Samsung wrapped Galaxy Unpacked in London today, and the foldable benchmark comparisons will be everywhere by tonight. Skip those. The Galaxy Z Fold 8, Z Fold 8 Ultra, Z Flip 8, Galaxy Glasses, and Watch 9 matter to developers for specific reasons — Android 17’s mandatory large-screen compliance is now live in a mass-market hardware push, a new wearable platform just got a hardware reveal date, and Wear OS 7 shipped with APIs the watch dev community has been requesting for years. Here’s what to act on, ordered by urgency.
Your Portrait Lock Is Gone. You Probably Haven’t Noticed Yet.
Android 17 (API Level 37) shipped on June 16. If your app targets API 37 and a user opens it on the Galaxy Z Fold 8 — or any Android 17 device with a smallest width above 600dp — the OS silently ignores android:screenOrientation, android:resizableActivity, android:minAspectRatio, and android:maxAspectRatio. Runtime calls to setRequestedOrientation() are also dropped.
The results aren’t subtle: stretched layouts, camera previews that rotate without accounting for it, animations that clip off-screen, UI components that were never tested outside a locked portrait viewport. Many apps have been using resizeableActivity="false" as a quiet fix for years. Those apps are broken on Galaxy Fold hardware right now — and their developers don’t know it because they’re not testing on foldables.
Google Play’s enforcement deadline for targeting API 37 is August 2027. That sounds distant until you realize users on Android 17 devices are hitting this today. The fix is not a one-line manifest change. It requires auditing your UI for adaptive behavior: proper WindowSizeClass usage, state preservation across rotation, and layout testing across folded, unfolded, and split-screen states. Games with android:appCategory set are exempt. Everything else is not.
Run your app on the Android 17 emulator this week — not when Play Store enforcement forces your hand. Open freeform windowing mode. Resize it. Watch what breaks.
Galaxy Glasses Is a New Platform With a Narrow Entry Window
The Galaxy Glasses announcement is what most developers will scroll past and regret in 18 months. The 2026 SKU is audio-only: no display, no onboard compute, processing offloaded to a paired phone. Priced at $379–$499, with Gentle Monster and Warby Parker frame options, arriving fall 2026. A display-equipped version is expected in 2027.
The development model is unlike anything currently in the Android toolkit. On a headset, you build a scene. On audio-only glasses, you build a prompt template. The entry points are the intent framework, notification summarization, the translation pipeline, and Gemini Live API for conversational context. The Jetpack XR SDK Developer Preview 4 introduces the Device Availability API — hooking into standard Android Lifecycle states so your app knows when glasses are being worn. The Jetpack Projected library bridges phone experiences to the glasses field of view.
One detail that changes the math: Galaxy Glasses work with both Android and iOS. That’s a larger addressable audience than any Wear OS device. The Android XR Developer Catalyst Program is accepting applications for pre-release hardware. Apps that ship at GA in fall 2026 get first-mover advantage in a category with no established ecosystem yet — unlike watches, where Wear OS and watchOS have years of momentum ahead of any new entrant.
App Bubbles Are a Multitasking Expectation Now, Not a Toggle
Android 17 introduces app bubbles as a platform-level multitasking feature. Any app can be long-pressed in the launcher to open as a floating, resizable window that minimizes to a bubble icon. On the Galaxy Z Fold 8’s inner display, this is genuinely useful — the real estate makes switching between floating apps feel closer to desktop than phone.
The issue for developers: users will attempt to bubble your app whether you tested that state or not. If your app doesn’t handle being resized mid-session, the experience degrades visibly. Android 17 also includes a foldable gaming mode that splits the inner display 50/50 — game on top, virtual gamepad on the bottom. Game developers who haven’t built for inner displays will be defaulted into this layout with no optimization. Drag-and-drop between apps is now expected behavior on large screens and is trivially discoverable on the Fold 8’s form factor.
Wear OS 7 Finally Has APIs Worth Building On
The Galaxy Watch 9 and Watch Ultra 2 debut Wear OS 7, which ships the largest set of useful developer tools the platform has seen in a single release. The Tiles API is replaced by Wear Widgets, now powered by Jetpack Glance with dynamic 2×1 and 2×2 card layouts. Live Updates replace the Ongoing Activities API for real-time data on the watch face. Compose for Wear OS 1.6 adds Navigation 3 integration and cleaner ambient mode handling via LocalAmbientModeManager.
The most forward-looking addition is the AppFunctions API, in Early Access, which lets watch apps respond to Gemini voice commands. On Watch 9, Gemini can trigger your workout tracker, timer, or task app without requiring UI navigation. It’s not production-ready yet, but early access registration is open now.
What to Do This Week
- Run your app on the Android 17 emulator in freeform windowing mode and identify what breaks
- Stop relying on
resizeableActivity="false"andscreenOrientationfor large-screen behavior — they don’t work on API 37 - Audit contact-access flows —
Intent.ACTION_PICKnow routes to the system Contact Picker on API 37 devices - Apply to the Android XR Developer Catalyst Program for Galaxy Glasses pre-release hardware access
- Register for Wear OS 7 AppFunctions Early Access if you build watch apps
- Test drag-and-drop handling if your app works with shareable content
