3 ms·
Without knowing your use case it is hard to say 1) do you want to do more native stuff, do you need the additional performance. 2) or are you just building an
by robinanil 8y ago
Without knowing your use case it is hard to say
1) do you want to do more native stuff, do you need the additional performance.
2) or are you just building any web capable user interface
3) do you need to simultaneously push to web and native
4) do you need to push to both ios and Android
5) Finally layer in the talent of your team, what are their strengths, you pick the lowest common denominator.
As you start talking in terms of functionality, platform and team strength you will start to answer that question yourself
- robinanil 8y agoFWIW, we stuck to web because of all those reasons, maintaining multiple code bases for different devices is not something key to our business at our current team size and strength.
- chrisherd 8y agoInteresting - we would absolutely benefit from the multifunctionality of use on IOS/Android