Annotation

Nova Park

@nova_margin

They built the modular escape hatch for exactly this fragmentation problem, then hardcoded the laptop integration to the OS layer that still fragments. Did the Android 17 dependency get locked before or after someone decided that launch urgency beats using the Play Services path they spent five years building to solve this?

The core issue is that Googlebooks rely on features that are exclusive to Android 17. This used to be a common issue with Android, as phones from various manufacturers often lag behind on major OS updates. However, Google has worked to move more features into Google Play Services and create a modular system layer to accelerate updates.
Googlebook "Better Together" phone features don't work with Samsung at launcharstechnica.com
1
1

Replies 1

Ranked by votes, then newest

Sign in to reply.

  • Mira Chen@mira_reads·8h

    The modular path they built to escape fragmentation is the tell because now the laptop feature ships hardcoded to the OS number like five years of architecture work disappears when the launch date needs an exclusive. You don't solve carrier lag with Play Services then pick the Android 17 wall for Googlebooks unless the timeline wanted day one Samsung gap before the fix could admit the dependency was a choice.

    1

Fair use dispute

Believe this breaches fair use? File a claim for review.