The Entrepreneur Forum | Startups | Entrepreneurship | Starting a Business | Motivation | Success

Cross Platform Progressive Web Apps

Remove ads while supporting the Unscripted philosophy...become an INSIDER.

OhMyGuersh

New Contributor
Feb 23, 2017
19
17
22
New York, NY
Im exploring creating a Progressive Web App (PWA). The app will mostly be used on the web on a desktop, but I want to have the option to scale the app to mobile as well. Does anybody have any experience with managing a cross platform Progressive Web App (PWA)? If so, what are some of the issues that you have encountered?
 

Don't like ads? Remove them while supporting the forum. Subscribe.

kanunay

Contributor
I've Read UNSCRIPTED
Apr 20, 2018
44
62
112
45
United States
I have been exploring this as well. I currently have a web app that is optimized for mobile use.

My app depends heavily on access to a database, so the offline functionality of PWA isn't as interesting to me as the ability to have push notifications and for it to easily appear on the user's home screen without going through a bunch of steps.

I do remember an issue with iOS, I don't know if it's true anymore but at one time you still had to make the user go through a bunch of extra steps to get an icon on the home screen.
 

Akeem

Bronze Contributor
I've Read UNSCRIPTED
Speedway Pass
Feb 4, 2016
81
220
153
United Kingdom
PWAs are fabulous, however, a lot of people underestimate a basic mobile application.

I ran into a ton of problems when I tested my own idea as a PWA. Sure, you can get push notifications that can increase engagement and you get an icon on the homescreen, however, IMO the bad outweighs the good.

Personally, I went with an actual application (without prior mobile development experience at that point) and simply dragged a webView element (a web browser) into the app which redirected to my mobile site and published the application.

In many ways, I still regard it as a PWA simply because it's just a neater version of the "Add to homescreen", but without the problems.
 
OP
OP
O

OhMyGuersh

New Contributor
Feb 23, 2017
19
17
22
New York, NY
PWAs are fabulous, however, a lot of people underestimate a basic mobile application.

I ran into a ton of problems when I tested my own idea as a PWA. Sure, you can get push notifications that can increase engagement and you get an icon on the homescreen, however, IMO the bad outweighs the good.

Personally, I went with an actual application (without prior mobile development experience at that point) and simply dragged a webView element (a web browser) into the app which redirected to my mobile site and published the application.

In many ways, I still regard it as a PWA simply because it's just a neater version of the "Add to homescreen", but without the problems.
Thanks for your perspective Akeem. Can you elaborate on some of the problems that you ran into, as well as the "bad" about PWAs.

Also, correct me if I'm wrong, but it sounds like ultimately you chose to make a hybrid app instead of a PWA. If that is not a hybrid app, what is this approach called?
 
Last edited:

Akeem

Bronze Contributor
I've Read UNSCRIPTED
Speedway Pass
Feb 4, 2016
81
220
153
United Kingdom
Thanks for your perspective Akeem. Can you elaborate on some of the problems that you ran into, as well as the "bad" about PWAs.

Also, correct me if I'm wrong, but it sounds like ultimately you chose to make a hybrid app instead of a PWA. If that is not a hybrid app, what is this approach called?
  • Speed is a massive downside to PWAs when compared to alternatives such as a native or hybrid application.
  • PWAs make it more difficult to store internal files on a user's mobile device (away from service worker and cache stuff).
  • You can't use most device features through a PWA, meaning you're losing out on certain features.
  • PWAs generally tend to use more battery power than a native or hybrid app.
  • You're losing out on app store and playstore traffic.
  • If you're not connected to the internet, tough luck, PWAs can't function without an internet connection.
In regards to your second paragraph, yes, you're right. I went with the hybrid approach simply because PWAs wouldn't cut it for me. Personally, I find that most people see PWAs as the easy option to throw out an application, not realising that with a little bit more effort they can do much more with a very simple hybrid application. This does ofcourse depend on the purpose of the PWA, however, it's actually not difficult at all to release a hybrid app and you get the best of both worlds.

This is just my opinion.
 

Pawel Kata

New Contributor
I've Read UNSCRIPTED
Jan 27, 2014
5
7
17
37
Latest iOS does not support PWA's properly, still, so if that's your market, you're better off making a mobile app. I'd like to suggest React Native as an easy way of making a mobile app for both Android and iOS. Also, with frameworks like react-native-web you'll also be able to have ~80% of your web app ready this way. The development is cheaper, than native apps, and the software works a lot smoother than PhoneGap/Ionic/Xamarin based products, which are basically websites packed in an app with a web browser without an address bar. Of course it's not rainbows and unicorns, but the amount of potential issues decreases daily and the technology is pretty mature at the moment. Uber Eats, Instagram, Wallmart, Soundcloud all use React Native and work great. That's just my 0.02$. First (hopefully) helpful post, too ;-)
 
OP
OP
O

OhMyGuersh

New Contributor
Feb 23, 2017
19
17
22
New York, NY
  • Speed is a massive downside to PWAs when compared to alternatives such as a native or hybrid application.
  • PWAs make it more difficult to store internal files on a user's mobile device (away from service worker and cache stuff).
  • You can't use most device features through a PWA, meaning you're losing out on certain features.
  • PWAs generally tend to use more battery power than a native or hybrid app.
  • You're losing out on app store and playstore traffic.
  • If you're not connected to the internet, tough luck, PWAs can't function without an internet connection.
In regards to your second paragraph, yes, you're right. I went with the hybrid approach simply because PWAs wouldn't cut it for me. Personally, I find that most people see PWAs as the easy option to throw out an application, not realising that with a little bit more effort they can do much more with a very simple hybrid application. This does ofcourse depend on the purpose of the PWA, however, it's actually not difficult at all to release a hybrid app and you get the best of both worlds.

This is just my opinion.
Thank you for your insight Akeem. It has been very helpful.
 

LexicMedia

New Contributor
Apr 8, 2019
10
2
8
Im exploring creating a Progressive Web App (PWA). The app will mostly be used on the web on a desktop, but I want to have the option to scale the app to mobile as well. Does anybody have any experience with managing a cross platform Progressive Web App (PWA)? If so, what are some of the issues that you have encountered?
Hello, let me try and explain you the scenarios based on our experiences with PWAs.
There will certainly always be the argument that a progressive web app is not native, and therefore not as performant and secure as a native app, and will never feel 100% like it to the user. And to be fair that’s probably right. But it’s also very probable that these differences will almost disappear, particularly for the normal user. And perhaps there are even users that prefer to see the same controls and to have the same look and feel when they access an application on their PC, iPhone, Android tablet, a Surface computer, on the TV and in the car.

From a development perspective, there are lots of arguments for a ‘one implementation serves them all’ solution. I won’t start with that again!

And another very interesting point is this: Since a PWA is basically a web app, the migration for many pages to a fully fledged device application is very close at hand! So even traditional online-only, browser-based pages could become offline applications on the home screen of your device.

So finally and most importantly is the fact, that the big tech giants are working on support: Google, Microsoft, Apple. In the world of the web and apps, it’s rarely a mistake to follow what they agree on. When Apple first introduced their iPhone 1 in 2007, they went with a concept very similar to PWAs. The only problem was, that there wasn’t the web technology like we have now. And Flash just didn’t meet their standards, or they couldn’t agree on a deal with Adobe. That’s why they went with native apps. So all in all, there is certainly a big future for progressive web apps.

In case if you have any requirements that we might can assist you, feel free to connect.
D M: preeti.saini63
 

LexicMedia

New Contributor
Apr 8, 2019
10
2
8
I have been exploring this as well. I currently have a web app that is optimized for mobile use.

My app depends heavily on access to a database, so the offline functionality of PWA isn't as interesting to me as the ability to have push notifications and for it to easily appear on the user's home screen without going through a bunch of steps.

I do remember an issue with iOS, I don't know if it's true anymore but at one time you still had to make the user go through a bunch of extra steps to get an icon on the home screen.
Hel
I have been exploring this as well. I currently have a web app that is optimized for mobile use.

My app depends heavily on access to a database, so the offline functionality of PWA isn't as interesting to me as the ability to have push notifications and for it to easily appear on the user's home screen without going through a bunch of steps.

I do remember an issue with iOS, I don't know if it's true anymore but at one time you still had to make the user go through a bunch of extra steps to get an icon on the home screen.

Hello Kanunay, as you mentioned that your App depends heavily on the database i would suggest you to opt for Cross Platform App Development or maybe Native Development as the app will need to access the database everytime for its functioning. React Native could be a very good example here as this is a latest platform having cost effectiveness of Cross Platform and User responsiveness of a Native Platform.

[removed by moderator]
 

astr0

Grinding
FASTLANE INSIDER
Read Millionaire Fastlane
I've Read UNSCRIPTED
Speedway Pass
Dec 3, 2017
328
459
232
32
Lviv, Ukraine
Latest iOS does not support PWA's properly, still, so if that's your market, you're better off making a mobile app. I'd like to suggest React Native as an easy way of making a mobile app for both Android and iOS. Also, with frameworks like
react-native-web you'll also be able to have ~80% of your web app ready this way. The development is cheaper, than native apps, and the software works a lot smoother than PhoneGap/Ionic/Xamarin based products, which are basically websites packed in an app with a web browser without an address bar. Of course it's not rainbows and unicorns, but the amount of potential issues decreases daily and the technology is pretty mature at the moment. Uber Eats, Instagram, Wallmart, Soundcloud all use React Native and work great. That's just my 0.02$. First (hopefully) helpful post, too ;-)
+1 for React Native, almost everything except rendering components can be shared with WebApp, and it's almost like a native app on the look&feel and performance(native rendering, just JS runtime instead of Java/machine code).

I wouldn't put Xamarin with PhoneGap and Ionic if you're not planning to put the whole Web app inside a WebView. It's AOT-compiled on iOs and MSIL with mono runtime on Android. Haven't worked with it for a few years though, maybe something had changed that I'm not aware of. But you won't get shared code with WebApp, cause it's C#/.Net.
 

Anand Mahajan

New Contributor
Feb 14, 2019
4
1
3
Pune
There are definitely pros and cons of both WPS and native apps. But WPS is the next level of mobile apps when it comes to publishers. Readers want their apps to load fast and WPS has solved that prob irrespective of shaky networks.
 

Don't like ads? Remove them while supporting the forum. Subscribe.

404profound

Platinum Contributor
I've Read UNSCRIPTED
Speedway Pass
Aug 27, 2017
1,344
2,779
662
Desert of Desertion
Currently building a PWA on the Node/MongoDB/Express/Vue-Nuxt stack. Contrary to common preachings I'm doing web-first before doing mobile. Easier to maintain control without worrying about app store bullshit requirements. My API is decoupled from the front end so it will serve the mobile UI as well once it's ready.
 

astr0

Grinding
FASTLANE INSIDER
Read Millionaire Fastlane
I've Read UNSCRIPTED
Speedway Pass
Dec 3, 2017
328
459
232
32
Lviv, Ukraine
Contrary to common preachings I'm doing web-first before doing mobile. Easier to maintain control without worrying about app store bullshit requirements.
Smart approach. It's also easier to develop/debug/test/iterate with web UI first.

Why Vue and not React?
 

404profound

Platinum Contributor
I've Read UNSCRIPTED
Speedway Pass
Aug 27, 2017
1,344
2,779
662
Desert of Desertion
Hello, let me try and explain you the scenarios based on our experiences with PWAs.
There will certainly always be the argument that a progressive web app is not native, and therefore not as performant and secure as a native app, and will never feel 100% like it to the user. And to be fair that’s probably right. But it’s also very probable that these differences will almost disappear, particularly for the normal user. And perhaps there are even users that prefer to see the same controls and to have the same look and feel when they access an application on their PC, iPhone, Android tablet, a Surface computer, on the TV and in the car.

From a development perspective, there are lots of arguments for a ‘one implementation serves them all’ solution. I won’t start with that again!

And another very interesting point is this: Since a PWA is basically a web app, the migration for many pages to a fully fledged device application is very close at hand! So even traditional online-only, browser-based pages could become offline applications on the home screen of your device.

So finally and most importantly is the fact, that the big tech giants are working on support: Google, Microsoft, Apple. In the world of the web and apps, it’s rarely a mistake to follow what they agree on. When Apple first introduced their iPhone 1 in 2007, they went with a concept very similar to PWAs. The only problem was, that there wasn’t the web technology like we have now. And Flash just didn’t meet their standards, or they couldn’t agree on a deal with Adobe. That’s why they went with native apps. So all in all, there is certainly a big future for progressive web apps.

In case if you have any requirements that we might can assist you, feel free to connect.
D M: preeti.saini63
@MJ DeMarco
 

404profound

Platinum Contributor
I've Read UNSCRIPTED
Speedway Pass
Aug 27, 2017
1,344
2,779
662
Desert of Desertion
Smart approach. It's also easier to develop/debug/test/iterate with web UI first.

Why Vue and not React?
Vue vs React is mostly a matter of preference. They both mount a virtual dom and use flux reactive state. The main difference is in component patterns and syntax. React is JSX and strongly modularized. Vue is more traditional ES6/HTML and I have CSS preprocessing (SCSS). I've tried learning all three (Angular/React/Vue) and Vue won because it's easiest to work with and diagnose errors. Their performance benchmarks are also nearly identical.
 

astr0

Grinding
FASTLANE INSIDER
Read Millionaire Fastlane
I've Read UNSCRIPTED
Speedway Pass
Dec 3, 2017
328
459
232
32
Lviv, Ukraine
Yeah, totally a matter of preference.

I don't know much about Angular cause I don't like their architecture/design decisions at all. Though it's very popular and my wife coded in Angular for years :rofl:.

React won my value competition mostly because it's more popular and it's easier to find good devs with experience in React than Vue here. Modularity is also great for code reuse, even between projects. Oh, and it's very easy to configure SCSS too.

Thanks for a quick answer!
 

404profound

Platinum Contributor
I've Read UNSCRIPTED
Speedway Pass
Aug 27, 2017
1,344
2,779
662
Desert of Desertion
Yeah, totally a matter of preference.

I don't know much about Angular cause I don't like their architecture/design decisions at all. Though it's very popular and my wife coded in Angular for years :rofl:.

React won my value competition mostly because it's more popular and it's easier to find good devs with experience in React than Vue here. Modularity is also great for code reuse, even between projects. Oh, and it's very easy to configure SCSS too.

Thanks for a quick answer!
Sure thing!
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Sponsored Offers

  • Sticky
MARKETPLACE How To Create A 100K-1M+ Sales Funnel
I think it's like a landing page, anyway it looks good, I've bookmarked it for future reference...
  • Sticky
MARKETPLACE Fox's Web Design Guide: Earn $100K this year (Yes, 2020!) and Go Fastlane
Just had a personal highlight of the program so far - @GuitarManDan gave a one hour Zoom talk on...
  • Sticky
MARKETPLACE KAK’s “Kill Bigger” Incubation Program- With DAILY personal attention.
I joined @Kak's business incubator in the first week of May. During our daily chats we uncovered...
  • Sticky
MARKETPLACE Lex DeVille's - Advanced Freelance Udemy Courses!
This is your May reminder that you can do this. I'll keep it short. These are the May promos...
  • Sticky
MARKETPLACE Grow Your Business With a Book (An Unorthodox Marketing Strategy That Built One of the Largest...
Thanks! This is a cool idea, actually. I would like to use your experience as I heard that these...
  • Sticky
FEATURED! Introducing... WEALTH EXPO$ED, A Short Story By MJ DeMarco
would this be available in paper version? I know it's short, but most of my family is...
  • Sticky
MARKETPLACE You Are One Call Away From Living Your Dream Life - LightHouse’s Accountability Program ⚡
Here is where you eliminate uncertainty from the future! I wanted to post this image as I...


Visit A Forum Sponsor
sponsor

New Topics

Fastlane Insiders

View the forum AD FREE.
Private, unindexed content
Detailed process/execution threads
Monthly conference calls with doers
Ideas needing execution, more!

Join Fastlane Insiders.

Top Bottom
AdBlock Detected - Please Disable

Yes, ads can be annoying. But please...

...to support the Unscripted/Fastlane mission (and to respect the immense amount of time needed to manage this forum) please DISABLE your ad-block. Thank you.

I've Disabled AdBlock