4 ms·
My tool is used by 1 million people a day https://www.photopea.com https://www.photopea.com This is the reason I never made a mobile version and all mobile use
by IvanK_net 18d ago
My tool is used by 1 million people a day https://www.photopea.com https://www.photopea.com
This is the reason I never made a mobile version and all mobile users use it in a browser.
The biggest problem (bug) with this approach is that iOS limits the RAM usage to 2 GB per website. I have to tell many of my users to ditch their $1000 iPads and get a used $150 Macbook for better experience.
I think Apple does it on purpose https://bugs.webkit.org/show_bug.cgi?id=268816 https://bugs.webkit.org/show_bug.cgi?id=268816
- focusedone 18d agoIf you are the photopea developer, you are a true hero. Thank you for your work!
- IvanK_net 18d agoThank you! :)
- egeozcan 18d agoI created a much more basic version of photopea (https://egeozcan.github.io/ketchup/ https://egeozcan.github.io/ketchup/) because I didn't even know it existed. This is very cool and fast!
- IshKebab 18d agoIn fairness is that really a bug? All apps are deliberately limited to a couple of GB on Android (depending on how much total RAM you have). It would be pretty annoying if a random website can just DoS your phone by using all your RAM.
- daveoc64 18d agoSeems like the solution to the DoS concern is to just limit the site to whatever amount of RAM is currently available on the device - that's what every other browser/OS combination other than iOS seems to do without issue.
- IvanK_net 17d agoWhen I run my website in Chrome on Android (with 8 GB of RAM), my website can get 6.5 GB of RAM. When I run my website in any browser on iOS (iPad with 16 GB of RAM), my website can get 1.88 GB of RAM. This much RAM might be needed only for a few seconds (computing a visual effect). A user is "focused" at just one app at a time. If a user uses my tool for hours, I think it makes sense to give them all the resources (CPU, GPU, RAM, ...)
- oblio 18d agohttps://bugs.webkit.org/show_bug.cgi?id=268816#c19 https://bugs.webkit.org/show_bug.cgi?id=268816#c19 > This issue is considered resolved. Per the above discussion, there are multiple restrictions at multiple levels that affect different scenarios, so it is not surprising that you are still seeing similar issues. > Please file a new bug with your use case. Providing a deeper explanation for the need than a synthetic test case would help us prioritize it higher. This is just shameful. 2 and a half years later, just resolving it like it's been 2 days.
- mattz56 17d ago[dead]