Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to build an app in two years

Avatar for Roman Roman
July 15, 2018

How to build an app in two years

Two years ago I did the first commit for my app. I couldn’t be imaging back then how much time it takes until it’s not ashamed to present to an audience.
This talk is about my own path from the idea to implementation. It can be useful for those who is planning to build some app or thinking about a start-up.

Avatar for Roman

Roman

July 15, 2018

Other Decks in Technology

Transcript

  1. Roman Alekseev Software engineer and tech lead at trivago I

    like to make things simple and performant efficient. @jesprider
  2. We believe [TYPE OF USER] has a problem [DOING THING].

    We can help them with [OUR SOLUTION]. We'll know we're right if [CHANGE IN METRIC].
  3. We believe young people who want to travel across multiple

    cities can’t plan their trip in a single application. We can help them with an application, which allows them to plan their trip remotely real time at a single place. We'll know we're right if investors will start to fight for investing in the app the app will have >100 unique visitors a day.
  4. ❏ Adding things to your MVP while doing something else

    ❏ Implementing too generic/reusable solutions ❏ Pixel-perfect prototypes ❏ Refactorings ❏ Prioritization ❏ Focusing ❏ Implementing quick prototypes ❏ Testing your solutions ❏ Notes Avoid Do more MVP and Prototypes
  5. 1. Got all the cities with population > 15k (~22k)

    2. Crawled description from wikipedia (node-wikifetch) 3. Defined criteria for routes a. Number of cities b. Distance between cities c. Total distance d. Population 4. Generated routes using graphs a. Billions in first tests b. 40k after defined criterias Algorithm
  6. Summary Find a problem and define a solution. Discover competitors.

    Find a team. Choose a name. Define MVP and stick to it. Build a prototype. Test. Iterate more. Think of SEO.