Camera
Capture, camera errors, blurry photos, and device-specific behavior.
Android Design: Design on Android means photos, camera reliability, Google Photos edits, screen recording, widgets, and the surfaces that change across Pixel and Samsung.
Android already has a lot built. The Design page should organize the useful work, not invent a second backlog.
Design pages should organize real creative tasks into a small set of surfaces. The article shelf below uses built pages first; the next-needed list stays intentionally short.
Capture, camera errors, blurry photos, and device-specific behavior.
Google Photos edits, backups, sync, album sharing, and storage cleanup.
Screenshots, screen recording, widgets, and visual surfaces.
Sharing, backup, export, and cross-device movement.
These links already exist in the article table and belong on the Design page now. That keeps the page useful without flooding taxonomy.
Already exists in the article library. This page places it before adding anything new.
Already exists in the article library. This page places it before adding anything new.
Already exists in the article library. This page places it before adding anything new.
Already exists in the article library. This page places it before adding anything new.
Already exists in the article library. This page places it before adding anything new.
Already exists in the article library. This page places it before adding anything new.
Pixel and Samsung labels differ, so organize by task instead of menu name.
The strongest existing cluster is Google Photos; make it the backbone.
Screenshots and recordings become support evidence, not just media.
Edits and backups should not silently eat the phone.
The purpose is curation: place strong existing articles, add a few gaps, and keep the next sections from becoming oversized backlogs.