Discuss: Preload building data in background about building-navigator HOT 9 CLOSED

Did you experience major performance issues? Or are there stutters in the browser? If nothing of this, why preloading?

from building-navigator.

On my smartphone it takes about 3 to 6 seconds from clicking a marker to the detailed results view. May we can improve it through preloading the details of the visible buildings.

from building-navigator.

Think about storing data using https://github.com/samyk/evercookie

from building-navigator.

Look for prefetching concepts and approaches. Try to preload building information when user on welcome screen. Load further information, when user moves the map or something.

from building-navigator.

Evercookies main point is to use all available browsers store (cookie, flash, html5 store, ...) and tries to avoids that users delete its content, which couldn't be our target.

from building-navigator.

After some thinking I decided to don't use preloading of data, because of to less positive effects to the end user. It does not really improve the speed of the app.

from building-navigator.

Evercookies main point is to use all available browsers store (cookie, flash, html5 store, ...) and tries to avoids that users delete its content, which couldn't be our target.

Why is that a problem here? We only store building information to speed up loading for users, nothing personal or sensitive.

from building-navigator.

First it has some caveats
Secondly i think its too intrusive:

If cookie data is removed from any of the storage mechanisms, evercookie aggressively re-creates it in each mechanism as long as one is still intact

from building-navigator.

Good points. I agree to leave that for now.

from building-navigator.