Launching a webservice: defining your MVP

When you have an idea for a webservice it’s easy to get lost into coding a lot of neat little features. But do you need all of them straight away? More often than not these features will cost you a lot of time to develop, while they might not even be the features your customer want. Wikipedia says: A Minimum Viable Product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development.

The best boilerplate app is the one you code yourself

Boilerplate apps are great. They let you get your next project up and running quickly, and usually provide some form of structure you can follow. They can also, however, be a massive time-sink. We developers are curious by nature, and tend to have this thing where we want to know exactly how things run under the hood 🙈 In addition, boilerplates can be too minimalistic for your needs, or too much bloat.

I made a tool to track your whole site's Pagespeed

At the office we usually take some time to optimise our client’s websites for Google Pagespeed. We got quite proficient in this and no what the common pitfalls and best practices are. However, I noticed we usually only do this for the homepage 🤔. This makes sense, as that’s usually the main page, but what about all the other pages. For instance, the order process pages or your contact form. Those are just as, if not more, important to load up quickly.