Skip to content
This repository has been archived by the owner on Jul 10, 2018. It is now read-only.

UCSF: zippify native app #51

Closed
Trott opened this issue Jun 22, 2013 · 2 comments
Closed

UCSF: zippify native app #51

Trott opened this issue Jun 22, 2013 · 2 comments
Milestone

Comments

@Trott
Copy link
Owner

Trott commented Jun 22, 2013

@Trott
Copy link
Owner Author

Trott commented Jun 26, 2013

Still need to review some of the links above, but in the existing setup, the main culprit seems to be external JS loaded on the initial page of an app. Thing to do is probably get minimal HTML loaded with a progress spinner and then append the JS scripts to the DOM after the load event has fired.

@Trott
Copy link
Owner Author

Trott commented Jun 27, 2013

Ooof, I think the only way around this, short of one huge honkin' single page app (which is an option), is to make sure that the main menu for each subapp loads without the need for any JS. Shuttle, Directory, and News are especially problematic right now. The thing they have in common is a need to load external JS, but even when I remove that need (for Shuttle, anyway), it's still kind of slow. Could try inlining everything. But probably best to serve up a menu and load any JS after deviceready and/or load fires. This will mean that the apps are not SPAs but instead a front menu page that links to places inside a SPA.

Or just go for one huge honkin' SPA, at least for PhoneGap.

@Trott Trott closed this as completed Jun 28, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant