“It works better in the app” (shkspr.mobi)

Article summary

The article discusses the frustration of being told that something works better in an app, when in fact the app is often incomplete or lacking in functionality. The author cites an example of trying to add a calendar link to their Google Pixel phone, only to find that it couldn't be done through the app. The author argues that many companies prioritize app development over creating decent mobile websites, leading to a poor user experience. This phenomenon is not unique to Google, but rather a common issue across many companies.

Main themes

• app development priorities
• user experience
• native apps vs web apps
• privacy and security
• feature limitations
• company motivations

What commenters say

• Some commenters argue that the prioritization of new features and apps over maintenance and completion of existing ones is a major issue in the tech industry.
• Others suggest that companies deliberately limit the functionality of their web versions to encourage app downloads and increase engagement.
• A few commenters mention that some features, such as NFC reading, are only available in native apps and not in web apps.
• Some argue that the benefits of native apps, such as offline functionality and improved performance, outweigh the drawbacks of having to install and update them.
• Others counter that web apps can provide a similar experience without the need for installation and can be more private and secure.
• Some commenters express frustration with companies that require app installation for certain features or services, and argue that this can be a barrier to adoption.
• A few commenters suggest that the line between native apps and web apps is blurring, and that web apps are becoming increasingly capable of providing a similar experience to native apps.