You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the loading page with "cough..cough.." takes too much time: 70% of users have a waiting time of 6+s.
As a result, in the analytics, we see a lot of people backgrounding/refocusing the app, and some people drop even before reaching the home page.
Reason why it's so slow: the app needs to:
Get GPS location from device (should be quite fast, though not always)
Fetch reverse geolocation (aka get place name from GPS lat/lng)
Fetch AQI data from WAQI (whose servers are, I suppose, in China).
This issue tracks 2 action items:
Solved by refactor: Fetch API before fetching reverse #329 Make the technical side faster. For example, right now we do 1->2->3 sequentially, but we should do 1->{2,3}, because 2 and 3 could run parallelly.
Think of some ways to make the waiting experience more enjoyable?
The text was updated successfully, but these errors were encountered:
I was thinking of having an animation while loading which you can interact with using touch, tilt, etc...
I can write the code but don't want to do so until your 100% with what I'm writing 😄
I forked and cloned the repo and while running it, I was thinking what if during loading we had an cigarette and holding down on your screen smokes it. Once it's completely burns out it's replaced with an new one then it's interactive and interesting.
Or instead have an cigarette burn as an loading bar, your call 👍
Right now, the loading page with "cough..cough.." takes too much time: 70% of users have a waiting time of 6+s.
As a result, in the analytics, we see a lot of people backgrounding/refocusing the app, and some people drop even before reaching the home page.
Reason why it's so slow: the app needs to:
This issue tracks 2 action items:
1->2->3
sequentially, but we should do1->{2,3}
, because 2 and 3 could run parallelly.The text was updated successfully, but these errors were encountered: