Your 'App' Could Have Been a Webpage (so I fixed it for you)

One dad saw a trip app, screamed “just make it a website,” and the comments cheered

TLDR: A fed-up parent rebuilt a Disneyland trip app as a plain webpage after deciding the app was unnecessary and stuffed with tracking and ads. The comments turned it into a full-on roast of modern app culture, with readers cheering the fix and arguing companies push apps to grab more attention.

A parent was told to download an app just to see a kids’ Disneyland trip schedule, and the internet responded with a giant, collective oh absolutely not. Instead of accepting one more phone-clogging download, he dug into how the app worked, pulled out the trip details, and rebuilt the whole thing as a simple password-protected webpage. The crowd’s reaction? Somewhere between standing ovation and full-blown anti-app rally. One commenter simply shouted “Preach!”, which honestly sums up the mood perfectly.

The strongest opinion in the thread was loud and clear: too many things are apps that should just be websites. People loved that this DIY fix cut out the extra junk, especially the app’s ads for other trips and the tracking tied to a Google account. The comment section turned into a support group for the app-fatigued, with users groaning that modern life keeps forcing them to install bloated little icons for things that could just be a page you open, print, search, or bookmark. One of the funniest reactions came from someone admitting they also have the dangerous urge to procrastinate by “fixing the world with code,” which is painfully relatable nerd chaos.

But there was also a mini-debate. Some users said this points to a bigger dream: making web versions of phone-only apps in general. Others dropped the hot take that websites can be awful too, and argued companies really want apps because they can spam people with notifications and keep grabbing attention. In other words: the article was about one trip app, but the comments made it a referendum on app culture itself.

Key Points

  • The article argues that the Travelbound app, used to share trip details, could have been implemented as a webpage instead of a mobile app.
  • The author intercepted the Android app's network traffic using an emulator, root tools, and HTTP Toolkit to inspect how it fetched data.
  • The app was found to request itinerary data from an API endpoint that incorporated the user's username and password into the URL.
  • The API response returned JSON containing itinerary entries, advertisement content, and file references used by the app.
  • The author built a password-protected HTML alternative with a Ruby script and Cron job that refreshed the JSON and omitted the app's advertisement section.

Hottest takes

"fixing the world with code in this way" — Hard_Space
"building web equivalents of apps that are only available on iOS/Android" — ed_mercer
"they want apps because they can spam you with notifications" — datakan
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.