Why Linc

Front-end Delivery is the future

Yesterday Chris Evans (of Captain America fame) proved Marc Andreessen right. Way back in 2011 Marc first spoke publicly about a trend he saw that software is eating the world (https://a16z.com/2011/08/20/why-software-is-eating-the-world/). Eight years later, there is no sign of slowing down. On the contrary, it's escalating exponentially.

This shift in development, where progress is measured by how 'smart' everyday objects are and how quickly they update, means we all need to become really good at agile development of software products — able to create, release or even change direction entirely, as quickly as possible. But this style of product development can be alien to many people who are used to large software projects that often take months, if not years, to deliver. If they deliver at all.

Product Development is very different in that it is highly uncertain work. You don't know whether your product will be successful. To be good at it means you stop attempting to increase the quantity of features and start focusing on the quality of features. In short, it is about getting the right things done right. But to be able to do that you need feedback. And that feedback needs to be timely, accurate and appropriate.

The two questions that need to be continuously answered, are: "Is it working?" and "Is it valuable?". Questions like these have moved our industry from Continuous Integration to Continuous Delivery. CI was able to answer the question "Does it still work?" whereas CD allows us to start answering the question "Is it valuable?".

Linc was created out of our own frustration with projects that either did not have appropriate CI/CD pipelines, or had pipelines that would take weeks or even months of work to set-up and maintain.

So how does Linc help?

We really did not need another *aaS term, but Linc is basically Continuous Delivery as a Service for front-end applications. We enable you to iterate faster on these front-end applications, so you get better feedback faster, thus allowing you to deliver more valuable and timely products.

We mainly support modern web applications like those written in React, Angular or Vue for two reasons. Firstly, because focusing on a specific tech stack allows us to provide more specific tooling than a generic CI/CD solution (like BuildKite or Github Actions). Secondly, this is the area of your application that benefits the most from rapid iteration.

To achieve all of this, we focus on:

  • Testing — making sure everything works, at all times,
  • Collaborating — working with people in your team (even non-technical stakeholders), other organisations and your customers, and
  • Releasing — making it quicker and more reliable to get things into the hands of your customers.

Testing

  • Able to run unit tests on every build, and also run acceptance tests against your fully deployed application,
  • Every commit is deployed and available for manual QA with every backend, including production,
  • Future integrations with third party tooling such as Calibre, Browserstack, Percy and many more.

Collaborating

  • Able to run unit tests on every build, and also run acceptance tests against your fully deployed application,
  • Every commit is deployed and available for manual QA with every backend, including production,
  • Future integrations with third party tooling such as Calibre, Browserstack, Percy and many more.

Releasing

  • Automatically deploy every push/merge on your main branch so you can easily get feedback from your customers and users.

Interested?

We are currently rolling out and scaling up Linc as an invite-only private beta. Join our mailing list below to join the queue for an invitation.

Back to Article Feed