Skip to content

SYSTEM Cited by 1 source

Pinterest Android app

Definition

The Pinterest Android app is Pinterest's native Android client — the primary distribution channel for Pinterest's visual-discovery and recommendation product on Android devices. 2026-04-08 post disclosure: 60+ surfaces (feature screens) are built on top of a shared UI framework whose base class is BaseSurface, and all 60+ surfaces are continuously measured for User Perceived Latency via the Visually Complete detection built into BaseSurface (Source: sources/2026-04-08-pinterest-performance-for-everyone).

Role on the wiki

Stub — this page exists to anchor cross-references from Pinterest client-side engineering posts (2026-04-08 Performance for Everyone being the first ingested). Named Pinterest Android surfaces in the wiki so far:

  • Home Feed — named in the post as "one of our key user experiences' surfaces" with a Visually Complete definition "all the images rendered and videos playing." Wiki page systems/pinterest-home-feed covers the ads-surface and MOO-reranking axes; this Android app context adds the client-performance axis.
  • Search Result Feed — named alongside Home Feed as a key user experience surface.
  • Video Pin Closeup — named with Visually Complete definition "the full-screen video starts playing."
  • Search Auto Complete — named with Visually Complete definition "the search autocompleted suggestions' text rendered along with the avatar images."

Known architectural primitives

From the 2026-04-08 post only:

  • BaseSurface — Android UI base class every surface inherits from.
  • PerfImageView / PerfTextView / PerfVideoView — opt-in marker interfaces product engineers tag performance-critical views with.
  • 60+ surfaces — scale datum for how many features are built on BaseSurface.
  • Two engineer-weeks per surface — pre-platform instrumentation cost; now reduced to zero-per-surface (platform handles it).

Pinterest's iOS app and Web app are mentioned as having received the same base-class Visually Complete pattern, but are not canonicalised as wiki systems yet.

Caveats

  • Stub — this page is a minimal anchor for the 2026-04-08 Performance for Everyone ingest. Broader Android app architecture (module graph, dependency injection, app startup, RUM / APM integration, release cadence, A/B infrastructure on-device) is not on the wiki.
  • No absolute latency numbers disclosed for any Android surface; the 2026-04-08 post is about the measurement platform, not the performance numbers themselves.

Seen in

Last updated · 319 distilled / 1,201 read