Eric5020946
Posts: 0
Joined: Tue Sep 18, 2012 4:31 pm

single page layout as default (native apps)

I suggest to change default layout to single page layout

Why? Only single page layout gives us page transitions similar to iOS experience (slide should be default as well) - as you probably know, lack of iOS type of styling and behavior will get your app rejected in App Store

In order to make this experience happen, pages shouldn't triger any REST calls until page is loaded, when page loads - mostl likely empty, call is made and with some small delay page is populated based on REST output. Only this will allow pages to transition smootlhy - in every other case, transitions are pointless and won't work (for native apps)

what to do?

  • test that single page layout triggers REST calls properly each tine page is visited, need ot resolve cache issues

  • determine which event fires right after page is loaded - sorts like web behavior, you see page, DOM is created and then ajax fires to populate empty DOM element

    without providing this ability and iOS experience using native app just simply sucks :) - assuming it will not get rejected :)

maxkatz
Posts: 0
Joined: Fri Aug 13, 2010 3:24 pm

single page layout as default (native apps)

Thank you for the idea... I think having it as an option is a pretty good solution. We want to leave it up to the developer to decide what's the best approach for his/her app.

Eric5020946
Posts: 0
Joined: Tue Sep 18, 2012 4:31 pm

single page layout as default (native apps)

web app vs native apps development is much different, perhaps it would be a good idea to ask user what kind of app they want to develop and preset editor with default settings proper for each development

something to think about for the future :)

maxkatz
Posts: 0
Joined: Fri Aug 13, 2010 3:24 pm

single page layout as default (native apps)

We had such option before - it confused users even more. They would create a pure mobile web app and then try to add native components.

Return to “Issues”