3 ms·
If going native makes sense, then going hybrid or responsive seldom does. That is, if the app isn't about content, like a catalog, or other content-centric purp
by Zigurd 12y ago
If going native makes sense, then going hybrid or responsive seldom does. That is, if the app isn't about content, like a catalog, or other content-centric purpose, then go native.
Or you can look at it from the other side: The more rich the interaction, and the more direct manipulation, the more reason to go native. If it's just a few buttons and text fields, you can choose whatever implementation is easiest for you.