While gathering the initial requirements, we also took part in the process of choosing the right technology.
There were three different technologies on the table:
- Native Development
- Progressive Web App (PWA)
- Cross-platform App (React Native)
We went through all the proposals, starting from the main criteria: time to market.
"Guys, if you got 4-6 weeks, what’s doable?"
Why not Native Development?
Veygo believes that if you put a shorter deadline on delivery, you will have to shrink the functionalities to the absolute minimum, and that’s exactly what they wanted.
All they need the prototype for, is to check the assumptions, and the MVP concept was perfectly enough to do so. If the feedback doesn't fit the assumptions, they won’t be going further with the development.
However, native development didn’t appear to be the fastest, nor the cheapest way to build the MVP, especially if you want to launch the app on both iOS and Android platforms.
On top of that, they were ready to abandon the idea, if it didn’t meet the market fit, so native development seemed to be too much time and cost consuming for such an initiative.
Why not a Progressive Web App (PWA)?
As an alternative, they were considering using Progressive Web App (PWA) development.
“We need a simple advice, like: these things are really complicated, and these things are not, so that we can weight specific functionalities and prioritise"
And as we started talking about functionalities we found that one of the most important functionalities are push notifications.
Unfortunately, with PWA you cannot have the iOS push notifications. Even more, you cannot publish a PWA app on the AppStore.
The winner: Cross-platform approach with React Native
So, in summary, to:
- keep the short development time,
- get to market faster,
- get the most important functionalities working,
- be on both App Store and Google Play,
- and make a quality MVP that we can easily reuse in the final product,
React Native appeared to be an ultimate, and a perfect solution.