For a mobile app (on the app store) do you recommend creating separate pages for sign up/login or should it be on one page with the rest of the app workflows?

Hello, for a mobile app (on the app store) do you recommend creating separate pages for sign up/login or should it be on one single page with the rest of the app workflows to be more efficient and avoid lagging, etc?

I try and keep my pages to a minimum with apps - especially if the end goal is to convert to a wrapper or publish on the app store.

I’ve built using the following approach with success on mobile, and while I haven’t published to the app store using this approach yet, I’ve got an app I published that didn’t take this approach and load time isn’t great, so this is definitely optimal in my opinion:

I have a landing / login / sign up / onboarding flow all from one page, then a second page for primary functionality of the app, then an admin dashboard accessible for myself.

Essentially I look to build the whole app from three pages, meaning the only load time is really between sign up / login navigating to the primary functionality page.

Hope that helps.

Just to add to that, I’ve started using repeating groups and option sets for menu items on my apps which has reduced my workflows significantly and made design changes on the app really easy. If you want to see a video on this let me know and I’ll send one through.

1 Like

Hey @Bubbler777,

Here are some tips and tricks for optimizing your native apps.

While optional, following these suggestions can significantly improve the speed and performance of your Android and iOS apps, as well as reduce the chances of rejection by Apple or Google:

Hope you find this helpful!

Best regards,
Zeroqode Team.