|
|
|
|
|
by akennberg
5021 days ago
|
|
I used to work on mobile products at Google using both, HTML5 for mobile and native. When betting on HTML5 you get the benefit of quick updates across multiple platforms and smaller team size. However, most of your time is allocated towards finding work arounds for strange browser bugs. Mostly glitches in the UI. With native, things work the right way most of the time, so you can quickly create exciting new features, which excites the team. The down side of native, is that you'll be implementing that exciting new features N number of times for each platform. Now that I am doing a lean startup, the reality is that the first app will be re-written completely. My bet is to focus short-term on one platform and write using native code for speed and lack of bugs (higher moral). For longer-term multi-platform play and if you plan to stay small and lean, I would recommend HTML5 or a hybrid. |
|