How to Build a Billion Dollar App
Sunday, September 25th, 2016 | Books
In How to Build a Billion Dollar App George Berkowski takes you through the stages of coming up with a mobile app from concept to being a billion pound company. It is based on his story co-founding taxi app Hailo.
As you might expect it is a pretty whistle-stop tour of each stage of the business. However, it provides a good overview with various comments and advice that Berkowski brings from his experience at Hailo. He stresses the importance of getting the product right for the market and how you should be measuring growth, two of the keys to getting a successful product out there.
While it is a good overview, I am not sure how much I am going to take away from it. Compared to something like The Hard Thing About Hard Things which offers plenty of specific and useful advice, this is more of a general guide to the journey. The one thing I did really like was a list of concepts that have universal appeal to humans. This is great for brainstorming ideas from.
I also found it interesting that he recommended having one Scrum Master for around 12-15 engineers. I have worked at a number of companies that do agile and a typical setup in the UK would be one Scrum Master to around 3-5 engineers, a considerably different ratio.
In How to Build a Billion Dollar App George Berkowski takes you through the stages of coming up with a mobile app from concept to being a billion pound company. It is based on his story co-founding taxi app Hailo.
As you might expect it is a pretty whistle-stop tour of each stage of the business. However, it provides a good overview with various comments and advice that Berkowski brings from his experience at Hailo. He stresses the importance of getting the product right for the market and how you should be measuring growth, two of the keys to getting a successful product out there.
While it is a good overview, I am not sure how much I am going to take away from it. Compared to something like The Hard Thing About Hard Things which offers plenty of specific and useful advice, this is more of a general guide to the journey. The one thing I did really like was a list of concepts that have universal appeal to humans. This is great for brainstorming ideas from.
I also found it interesting that he recommended having one Scrum Master for around 12-15 engineers. I have worked at a number of companies that do agile and a typical setup in the UK would be one Scrum Master to around 3-5 engineers, a considerably different ratio.