I really like Qin 1s phone and it's operating system. Only drawback is the browser is Chrome 33 and 256MB RAM. To put in perspective, it can't handle sites like Instagram & prompts "go to memory saver mode or quit browser" In other words, many webpage consume too much memory.
-
Show this thread
-
btw: memory saver mode = no image soooooo you can see, many of web activities we do become inaccessible.
1 reply 0 retweets 6 likesShow this thread -
Here is face book in saver mode. No emoji, no menu icons. It’s not the issue only for low power phone user. Blocking image is a efficient data saver for those in regions where mobile data is expensive.pic.twitter.com/Zmj8zvxYbV
3 replies 4 retweets 14 likesShow this thread -
Replying to @kosamari
Graphics stack is always #1 memory user (cull your layers, yo!)...but you know what #2 is? JS heap. Every time.
1 reply 0 retweets 1 like -
Replying to @slightlylate
I don't think majority of web developers even know about composited layers (I didn't...until like 3 years ago, and only learned it because of proximity to browser engineers like you :D ) JS heap is yeah easier to get it would be issue.
1 reply 0 retweets 1 like
JS heap bloat is exacerbated by extraneous DOM creation...it's amazing how inefficient modern frontend development has become. Truly a thing of wonder.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.