4 ms·

I will say that our marketing and sales teams probably did a poor job of communicating the capabilities of the app to our customers. I'm not even sure if most o

I will say that our marketing and sales teams probably did a poor job of communicating the capabilities of the app to our customers. I'm not even sure if most of them knew how it worked. I don't think our customers found the PWA features "organically", either. If they saw the install prompt, they most likely didn't understand it, ignored it, or both. I tried showing it to some at a conference, but like I said, they were uninterested in those features in comparison to the app itself.

mephitix 8y ago
I see. I am guessing for your app (record entry) it didn't matter that they were uninterested in those features. I'm working on an app that is highly reliant on push notifications (like chat). So if I made it a PWA, it would be DOA if my customers didn't hit 'install to homescreen'.
- untog 8y ago
  Not entirely- you can still receive notifications even if you're not installed to the home screen. The progressive path isn't great, but installing an app from an App Store is a huge jump for users to make, so neither is ideal really...
  - mephitix 8y ago
    On iOS you can't get notifications if you've closed out of Safari... it's not really usable. A simple scenario is - you're inviting someone to a chat room. You send them an invite and now you have to wait. Usually what people do is other things - like go to a different website, go to a different app, etc. In only the case where you're sitting on the same website will you get a notification. It doesn't work. It gets worse - let's say you installed the app to your homescreen. You run through that same scenario above - you navigate through your web app into /chatroom and click on an invite button there. Then you navigate away to another website/app. When you come back to the homescreen app, the entire site has reloaded and it will take you automatically to the main screen of your web app: / Note - these broken behaviors are only on iOS.
    - untog 8y ago
      Oh, yeah. I don't consider iOS a full PWA platform for exactly these reasons. Sad really.

mephitix 8y ago

I see. I am guessing for your app (record entry) it didn't matter that they were uninterested in those features. I'm working on an app that is highly reliant on push notifications (like chat). So if I made it a PWA, it would be DOA if my customers didn't hit 'install to homescreen'.

untog 8y ago
Not entirely- you can still receive notifications even if you're not installed to the home screen. The progressive path isn't great, but installing an app from an App Store is a huge jump for users to make, so neither is ideal really...
- mephitix 8y ago
  On iOS you can't get notifications if you've closed out of Safari... it's not really usable. A simple scenario is - you're inviting someone to a chat room. You send them an invite and now you have to wait. Usually what people do is other things - like go to a different website, go to a different app, etc. In only the case where you're sitting on the same website will you get a notification. It doesn't work. It gets worse - let's say you installed the app to your homescreen. You run through that same scenario above - you navigate through your web app into /chatroom and click on an invite button there. Then you navigate away to another website/app. When you come back to the homescreen app, the entire site has reloaded and it will take you automatically to the main screen of your web app: / Note - these broken behaviors are only on iOS.
  - untog 8y ago
    Oh, yeah. I don't consider iOS a full PWA platform for exactly these reasons. Sad really.