Thoughts for building a mobile app that has some UI and flow differences than the browser version
We are going to generate an android mobile app using Quasar/Cordova, the mobile app would have some differences than the browser version, and here are some of them:
- Some components would have a different UI
- Different design for the login page
- Different flow after a user logs-in
- We would have a bottom bar (contains some navigation icons)
- Some routes would be visible for mobile app only
- Navigation experience could be different for the mobile app
My concerns are:
- Is this even a valid approach and doable using the platform detectors, or it’s preferred to go with a separate project to serve the mobile app?
- Let’s assume we would have many components/pages that are specific for the mobile app only, will this affect the performance in general?
- In a such a case, should we utilize the current logic and use it for mobile app & browser version? or we should separate them? (for example user different methods, stores, computed functions for the mobile app only)?
- How to organize such a thing, and what should take it into consecration?
I need some thoughts & insights from your experience, so we can do it right.
dobbel last edited by dobbel
Is this even a valid approach and doable using the platform detectors, or it’s preferred to go with a separate project to serve the mobile app?
Yes it’s very doable with platform/mode detectors in a single project.
Here’s a repo/project/product(enFocus) that has a different ui/flow based on if you are on mobile or electron.
It is using different techniques to archive this( for example using functional components and different routes depending on what mode quasar is running).