logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·31.10.26
← Back to news

“It works better in the app”

Original article
shkspr.mobi|556 points|362 comments|by blenderob|Aug 28, 2026

“It works better in the app”

By Terence Eden | 📅 August 2026 | 👁️ ~28,729 Views

The Google Paradox

The "monkey-punchers" over at Google seem to have a chronic inability to actually finish a product. Whether it's a lingering, showstopping bug or a critical feature left on the cutting room floor, their software is perpetually riddled with jagged edges—despite being crafted by the supposed "greatest minds" of our era.

I recently found myself using a Google™ Pixel® device running Android© 17. I had a simple goal: click a calendar link and add it to my device.

The Struggle

Is this a monumental feat of software engineering? Absolutely not.

  • Seamless integration
  • One-click adding
  • Intuitive UX

I suspect even a mediocre Gemini model could vibe code a solution for this in a few months. Yet, the app failed me. The only way to succeed was to open calendar.google.com in a mobile browser, force desktop mode, and add the calendar there. Only then did it "magically" sync back to the app.


The Corporate "App" Trap

Why the push for native apps? It's rarely about the user. Many corporations are obsessed with securing a permanent spot on your home screen because they assume you're too incompetent to use a browser bookmark.

The real motivation is usually a metric: Corporate Bonus∝Engagement KPI↑\text{Corporate Bonus} \propto \text{Engagement KPI} \uparrowCorporate Bonus∝Engagement KPI↑

When "Quinn" in leadership needs to hit their OKRs to secure a year-end bonus, they push the app. I've lost count of how many times I've been told "it's easier if you use our app," only to be kicked back to the web the moment I try to do something the app's rigid constraints don't allow.

Native vs. Web: The Technical Debt

Having built software for everything from the Palm Pilot to BlackBerry and Symbian, I know the core issue: Apps are a nightmare to update.

"Every single new feature or page must be rigorously tested across thousands of different device configurations."

The only viable workaround is to have the app dynamically fetch functionality from a remote server. While apps once held a monopoly on certain hardware features and offline access, modern browsers have largely closed that gap.


Community Discourse

The post sparked several reactions from the tech community:

ContributorPerspective
Paul ArmstrongGoogle software exists in only two states: deprecated or not yet ready.
Tim W RESISTSPromotion at Google is based on the launch, not the landing.
Alex BuznikNoted the irony of the author's homepage looking like a mobile screen.
GregoryArgues that "it works better in the app" is just an excuse for a lazy mobile website.

Technical Footnote: The Share Logic

The site utilizes a specific JavaScript snippet for sharing:

{ 
  try { 
    await navigator.share({url:u}); 
  } catch { 
    // Fallback if the Web Share API fails
    alert('Copied URl to clipboard'); 
  } 
}

🗓️ Archive Statistics

The author's posting frequency is remarkably consistent:

  • 2026: Aug (44), July (17), June (17), May (19)...
  • 2025: Dec (15), Nov (17), Oct (16)...
  • 2024: Consistent ~30 posts/month.
  • 2023: Perfect 31-day streaks in several months.

Images from the discussion: