6 ms·
Even though the average Android phone doesn’t compare performance wise to an iOS device and really sucks when it comes to running complicated web apps, it’s mo
by scarface74 7y ago
Even though the average Android phone doesn’t compare performance wise to an iOS device and really sucks when it comes to running complicated web apps, it’s mostly Android users here who claim that progressive web apps are the future and that Apple is holding them back.
- pjmlp 7y agoBecause Angular, React, Vue aren't needed for like 90% of those applications, server side rendering is more than enough. Specially when tons of "native" applications are actually Cordova and Ionic garbage that take longer to start than a HTTP server reply to the native browser. Native applications are great, when we are talking about stuff that actually makes use of the GPGPU or hardware sensors. Outside games, office and drawing applications, I don't have any applications installed that couldn't easily be done as mobile Web sites.
- scarface74 7y agoHow are you going to have a PWA that works offline with server side rendering? The latest “Apple wants to force everyone to develop apps instead of using the web so they can get their 30% cut of mostly free apps” controversy was about offline storage expiring after 7 days. Not to mention that the same people who are buying cheap Android phones probably have limited data plans and/or low bandwidth.
- pjmlp 7y agoBy having a server worker that caches the whole site, done. Apple's decision doesn't apply to PWAs as clarified on a later update. Plus updating the browser cache every couple of days isn't a big deal, native apps get store updates almost every day.
- scarface74 7y agoSo, no dynamic changes of the UI? We are talking about “web apps”.
- pjmlp 7y agoMany "web apps" are plain CRUD entry forms with fancy CSS animations.
- scarface74 7y agoI’ve done CRUD apps on mobile mostly for field services (technicians, deliveries, etc.) where it had to work offline. Even then you needed to navigate between screens, menus, navigate to different screens based on options chosen, client side validation, manage state on the client, etc. You still needed UI changes.
- pjmlp 7y agoStill possible with service workers without having the poor browser chew a SPA framework.
- scarface74 7y agoHow do service workers help if you can’t depend on having a network connection? Are you really saying that it would he more performant that you have to make a round trip just to perform validation? How slow would the hardware have to be for a network round trip to be faster?
- pjmlp 7y agoBy reading from the cache the necessary static HTML and CSS. Validations always need to be done on both sides, unless one does not value security. All of this is possible with vanilaJS, using builtin browser features, no need to kill the poor CPU with an additional bloated framework. I used to be big in native apps, until having seen too many examples of what used to be done in VB/Acess back in the day. So unless it is a game using OpenGL ES 3.0, Vulkan, Metal, something that requires AR/VR, real time audio, GPGPU for machine learning, or direct access to hardware sensors, it might be quite doable as PWA.
- nicoburns 7y agoThat's because it's not performance that's holding back PWAs. With a bit of work, perf was good enough for web apps on an iPhone 4S or earlier. iPhone 4s was released in 2011, so if low-end android devices are not hitting 2012/2013 iPhone performance levels, then they're also good enough for PWAs. It's the lack of platform APIs for things like offline storage and push notifications that are holding back web apps, not performance.
- scarface74 7y agoI bought my son a MotoG back in 2017. Because I kept reading that it was a good midrange Android phone. It was slow running “native” apps, web performance was even worse. He was more than happy to “upgrade” to my iPhone 6s (2015) in 2018. Performance was noticeable better. Also, it is still supported by the latest version of iOS. Of course by then the phone was three years old so I replaced the battery.
- Justice4Yall 7y agoios 14 won't support 6s most probably and soon your iphone 6s will go to trash. So your comment is lucky to have some truth for a couple of months while I look at my trashed iphone5 and iphone 6.
- scarface74 7y agoThe iPhone 6s would have gotten 5 years of os upgrades. But, just because Apple won’t support a device with latest version of iOS, doesn’t mean that it won’t provide security patches and bug fixes. For instance, Apple released bug fix patches for iOS 9 and iOS 10 supporting phones back to 2011 last year. https://appleinsider.com/articles/19/07/22/apple-issues-ios-936-and-ios-1034-updates-for-older-iphone-and-ipad-models https://appleinsider.com/articles/19/07/22/apple-issues-ios-... As far as going into the trash. I had an old iPad 1st generation (2010) that last saw an OS upgrade in 2011. I could still download the “last compatible version” of apps like Netflix, Hulu, Plex and Crackle and they still work. iCloud syncing also works with Apple’s iWork apps and the built in apps (except for Notes).
- arendtio 7y agoI run my own PWA on a 2012 Samsung Galaxy S3 and the only performance problems I have, are due to bad decisions as a developer (e.g. loading all elements of a list isn't such a great idea when the list grows over time and you use the app for 3 years (so far)). So if you are serious about building PWAs you shouldn't have performance issues. Yes, they are a bit slower than native apps, but with today's devices that shouldn't matter. The issue with Apple is, however, that they don't support all the APIs you need to create an awesome PWA (and decided recently to throw away the localStorage every 7 days unless the user wants to clutter his desktop with every PWA that needs to store data on the device for longer periods).
- scarface74 7y agoThat’s actually a good thing. If every website could store data indefinitely, it would be abused. By only allowing long term storage for websites that the user “installed” on their phone by adding it to the home screen expresses intentionality.