Been looking at designing a 1 page mobile app since they say that’s what you’re supposed to do.
All of the questions people asked weren’t answered. They just dead ended without responses.
Does anyone develop mobile-only here?
What is the problem with using “go to page” in a mobile app vs using URL parameters to show/hide elements and put everything on one page?
I don’t even think I can feasibly put everything on one page. The app has too many different things going on.
From my little experience, you see when your designing a mobile app the UX has to be exceptional, that way people using your app will have no issues using the app and the nav. will be smooth
Basically with URL par. to show an hide, your pages (tabs) loads faster giving the user that mobile app vibes as opposed to a traditional web page with takes approx. 4s to load…
this is just one amongst other reasons
One reason is performance, the other is, if you plan to port it to a native app, you can’t do that with multiple pages AFAIK.
If you are just planning to have a PWA (progressive web app) and don’t plan to port it to iOS/Android, you can absolutely use multiple pages.
you can use multiple pages but it can be limiting if you want to convert to a native app later
you’ll also notice that multi page apps lag between pages as the page and data has to be rendered/downloaded
single page apps usually take a longer time to initially load but are faster between “pages”/states
that’s because previously loaded pages data is still on the page (just hidden) so it doesn’t need to be downloaded again unless window is refreshed
sometimes I’ll build sections of a webapp like a single page app because I want to make it fast for the user to switch between “views”
most mobile apps I build are too heavy/complex to be native builds so I don’t worry about it and just build per page like I do web apps
Ok, thanks for the info/theory on this.
It’s a native app with no web app presence, no website. It’ll be wrapped using BDK since Bubble won’t let me try their Native App design tools. Sore subject.
So It’s confusing me. There is an index page of course. That is the whole app?
How do I do my splash screen and login/signup pages, then all the real pages inside the app?
Do I just not use the index page at all (leaving it blank) and make every single thing a group/child of index? So index is just an empty page with groups representing each page that are turned on/off?
I’m a little confused because index has a gradient background feature I need and am making use of. Regular groups do not. Or maybe they do and I’m confused?
Has anyone carried this through to a complete app and can let me know how to proceed with a fully wrapped, fully functional app with signup/login pages as well as a splash screen? Am I on the right track for best practices?
All has to be responsive of course.
Thanks!
This won’t work for converting to a native mobile apps. The editor won’t even let you do it without throwing errors:
The only way you could do it is if you use ‘go to page’ and want the other page to open in an external browser. A separate page won’t load inside the native app created through a different page.
it’s not so hard to convert a page into a reuseable element later on
but if I’m building for mobile native I’ll use reuseable elements as “pages” and not use separate pages
ok, this was a good discussion. Thank you. I’ll try to convert my index splash/login screen to a group.
Thanks!
