0 views collected around this technical thread.
This article explains how to enable and use iOS Picture-in-Picture for both system and custom video players, create a timer‑based PiP view, and integrate PiP into an English listening app, while comparing two implementation approaches and offering performance tips.
Chrome 111, released a month after Chrome 110, brings a refined download bubble UI, a numeric download count, smoother page transition support via the View Transitions API, automatic revocation of unused site permissions, and a new Document Picture-in-Picture API for richer web experiences.
This article explains how to use the new Picture-in-Picture Web API to enable floating video playback on web pages, covering setup of video and button elements, request handling, error management, event listeners, window‑size tracking, feature detection, and best‑practice UI considerations.
The article compares Android small‑window video playback techniques—SurfaceView, GLSurfaceView and TextureView—detailing their animation limitations, providing source‑code examples for embedded and floating implementations, and showing that TextureView combined with a singleton player offers the smoothest, most reliable small‑window experience.
The article compares Android’s SurfaceView, GLSurfaceView, and TextureView for picture‑in‑picture video playback, explaining each view’s rendering model, the hole‑punch limitations of SurfaceView, Android N’s synchronous updates, and TextureView’s full transformation support at higher power cost, to guide developers in choosing the optimal solution.
Android O (8.0) adds fluid‑experience features such as notification channels and dots, picture‑in‑picture, adaptive icons, autofill, downloadable fonts, pinned shortcuts, TextView auto‑sizing and media enhancements, while Vitals improve battery, security and stability, and it introduces background execution limits, stricter permissions, new WebView and UI APIs, unified margins, animation set improvements, and overlay‑window changes.