6 ms·

Have you tried creating a messaging app that works in iOS Safari? Thanks to Safari's janky-AF scroll behavior, you can be sure that it's a terrible experience.

Have you tried creating a messaging app that works in iOS Safari? Thanks to Safari's janky-AF scroll behavior, you can be sure that it's a terrible experience. Source: I work on a major tech company's web-based messaging product.

intrasight 5y ago
Dating apps don't scroll - the just swipe ;) I've heard that they are finally putting some resource on the jank.
pinephoneguy 5y ago
Also no push notifications which at this point is the only reason to bother with native iOS apps as everything else is off limits anyway.
- jdrc 5y ago
  That seems like another shot in the foot though. Apple and google are gatekeepers of notifications. Email is still the most robust choice for infrequent notifications. I wish email had been extended to implement temporary notifications
  - pinephoneguy 5y ago
    The problem with email on iOS is that there's no way to do instantaneous notifications without paying Apple at least $100/year for a custom app with a certificate to do push. The mail app only does polling (no IMAP IDLE) so the latency on notifications is very high there. The consequences of the iPhone on the internet are extreme and I don't think most of the people involved in internet protocol design have fully realized just how bad it is.
- shagie 5y ago
  If push notifications are an important value add, which go through Apple's servers is it reasonable for Apple to have companies that make money using there services subsidize the free ones? Alternatively, if everyone who is publishing free on Apple is using an alternate payment system, and Apple doesn't collect anything from those apps, would it be reasonable for Apple to have some sort of "Developer pays $10 for every 10k push messages from a free app?" and "Developer pays $0.25/month for each app on the App Store"? There's a question of "How does Apple pay for services?" Yes, it is currently quite profitable. If moving to a 3rd party payment processor with no associated fee causes the App Store to become unprofitable, what steps is Apple allowed to take to return it to a profit center?
  - pinephoneguy 5y ago
    Why do they have to go through apple’s servers? Why can’t users select an alternative push provider? Why can’t apps be allowed to just maintain their own socket if the user is ok with the battery impact?
    - shagie 5y ago
      There are alternatives. They're not free. https://ios.libhunt.com/categories/1351-push-notification-providers https://ios.libhunt.com/categories/1351-push-notification-pr... Another part to this is that people have been highly critical of Apple when their battery performance is poor, not realizing that its an app that is consuming the battery. That has been mitigated some by Apple showing which apps are consuming the battery the most, but people tend to blame the OS rather than the application when something goes wrong. https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost-the-api-war/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost... > The most impressive things to read on Raymond’s weblog are the stories of the incredible efforts the Windows team has made over the years to support backwards compatibility: >> Look at the scenario from the customer’s standpoint. You bought programs X, Y and Z. You then upgraded to Windows XP. Your computer now crashes randomly, and program Z doesn’t work at all. You’re going to tell your friends, “Don’t upgrade to Windows XP. It crashes randomly, and it’s not compatible with program Z.” Are you going to debug your system to determine that program X is causing the crashes, and that program Z doesn’t work because it is using undocumented window messages? Of course not. You’re going to return the Windows XP box for a refund. (You bought programs X, Y, and Z some months ago. The 30-day return policy no longer applies to them. The only thing you can return is Windows XP.) While Apple doesn't go that far to preserve backwards compatibility, they're still the ones that take the heat when a popular app is excessively battery consuming as its the battery indicator that's going down.
  - Andrew_nenakhov 5y ago
    They are an important value add only because iOS restricts background processes and forces developers to rely on push notifications. You may do without push notifications on Linux, or Windows, but on iOS certain classes of apps are impossible to implement without them.
- heleninboodler 5y ago
  And I've led a very rich dating-app life with all push notifications turned off anyway. It's not healthy to be a slave to dating apps. I would 100% welcome web-based versions of them.
  - verst 5y ago
    Bumble, Tinder and OkCupid certainly still have web clients. Never tried any of these on mobile web though.
    - heleninboodler 5y ago
      Oh, nice. Back when I was using them, Bumble and Tinder definitely didn't, although I did find one kinda hacky Tinder web-based thing that was a result of reverse-engineering their APIs. Glad to hear they're making progress, and I hope they are mobile-friendly. It should be very easy to implement the basic functionality on mobile. As pointed out, messaging will take a lot of work, but it's doable. I wouldn't trust OKCupid to be able to do a decent mobile web UI, because they can't really be trusted to do either a regular web UI or a decent mobile app. :D Their entire UX was always just so full of jank and they were constantly tweaking it with the apparent goal of making nobody understand how anything works or is supposed to work.

intrasight 5y ago

Dating apps don't scroll - the just swipe ;) I've heard that they are finally putting some resource on the jank.

pinephoneguy 5y ago

Also no push notifications which at this point is the only reason to bother with native iOS apps as everything else is off limits anyway.

jdrc 5y ago
That seems like another shot in the foot though. Apple and google are gatekeepers of notifications. Email is still the most robust choice for infrequent notifications. I wish email had been extended to implement temporary notifications
- pinephoneguy 5y ago
  The problem with email on iOS is that there's no way to do instantaneous notifications without paying Apple at least $100/year for a custom app with a certificate to do push. The mail app only does polling (no IMAP IDLE) so the latency on notifications is very high there. The consequences of the iPhone on the internet are extreme and I don't think most of the people involved in internet protocol design have fully realized just how bad it is.
shagie 5y ago
If push notifications are an important value add, which go through Apple's servers is it reasonable for Apple to have companies that make money using there services subsidize the free ones? Alternatively, if everyone who is publishing free on Apple is using an alternate payment system, and Apple doesn't collect anything from those apps, would it be reasonable for Apple to have some sort of "Developer pays $10 for every 10k push messages from a free app?" and "Developer pays $0.25/month for each app on the App Store"? There's a question of "How does Apple pay for services?" Yes, it is currently quite profitable. If moving to a 3rd party payment processor with no associated fee causes the App Store to become unprofitable, what steps is Apple allowed to take to return it to a profit center?
- pinephoneguy 5y ago
  Why do they have to go through apple’s servers? Why can’t users select an alternative push provider? Why can’t apps be allowed to just maintain their own socket if the user is ok with the battery impact?
  - shagie 5y ago
    There are alternatives. They're not free. https://ios.libhunt.com/categories/1351-push-notification-providers https://ios.libhunt.com/categories/1351-push-notification-pr... Another part to this is that people have been highly critical of Apple when their battery performance is poor, not realizing that its an app that is consuming the battery. That has been mitigated some by Apple showing which apps are consuming the battery the most, but people tend to blame the OS rather than the application when something goes wrong. https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost-the-api-war/ https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost... > The most impressive things to read on Raymond’s weblog are the stories of the incredible efforts the Windows team has made over the years to support backwards compatibility: >> Look at the scenario from the customer’s standpoint. You bought programs X, Y and Z. You then upgraded to Windows XP. Your computer now crashes randomly, and program Z doesn’t work at all. You’re going to tell your friends, “Don’t upgrade to Windows XP. It crashes randomly, and it’s not compatible with program Z.” Are you going to debug your system to determine that program X is causing the crashes, and that program Z doesn’t work because it is using undocumented window messages? Of course not. You’re going to return the Windows XP box for a refund. (You bought programs X, Y, and Z some months ago. The 30-day return policy no longer applies to them. The only thing you can return is Windows XP.) While Apple doesn't go that far to preserve backwards compatibility, they're still the ones that take the heat when a popular app is excessively battery consuming as its the battery indicator that's going down.
- Andrew_nenakhov 5y ago
  They are an important value add only because iOS restricts background processes and forces developers to rely on push notifications. You may do without push notifications on Linux, or Windows, but on iOS certain classes of apps are impossible to implement without them.
heleninboodler 5y ago
And I've led a very rich dating-app life with all push notifications turned off anyway. It's not healthy to be a slave to dating apps. I would 100% welcome web-based versions of them.
- verst 5y ago
  Bumble, Tinder and OkCupid certainly still have web clients. Never tried any of these on mobile web though.
  - heleninboodler 5y ago
    Oh, nice. Back when I was using them, Bumble and Tinder definitely didn't, although I did find one kinda hacky Tinder web-based thing that was a result of reverse-engineering their APIs. Glad to hear they're making progress, and I hope they are mobile-friendly. It should be very easy to implement the basic functionality on mobile. As pointed out, messaging will take a lot of work, but it's doable. I wouldn't trust OKCupid to be able to do a decent mobile web UI, because they can't really be trusted to do either a regular web UI or a decent mobile app. :D Their entire UX was always just so full of jank and they were constantly tweaking it with the apparent goal of making nobody understand how anything works or is supposed to work.