Package selection guidance compiled from public package information, community data, and project usage.
wp_pivot_flutter is a Flutter package that implements a Windows Phone-style pivot tab bar, offering a sleek, swipeable interface for navigating between multiple tabs. Designed with a modern aesthetic inspired by Microsoft's Windows Phone UI, it provides smooth transitions and intuitive navigation. The package supports all major platforms including Android, iOS, Web, macOS, Windows, and Linux, making it ideal for cross-platform applications seeking a distinctive tab experience. It integrates seamlessly into Flutter apps with minimal setup and customizable styling options.
Use cases
Cross-platform mobile and desktop apps
Windows Phone-inspired UI design
Swipe-based tab navigation
Content organization in dashboards
Enhancing user engagement with visual feedback
Key features
Windows Phone-style pivot animation
Smooth horizontal swiping
Customizable tab indicators
Support for multiple platforms
Built-in transition animations
Easy integration with existing Flutter projects
Suitable for
Developers seeking unique UI components
Apps requiring intuitive tab navigation
Designers aiming for a retro-modern aesthetic
Projects targeting multiple operating systems
Teams wanting consistent UX across devices
Considerations
Limited to pivot-style tab layout
May require additional styling for complex use cases
Best suited for apps with 3-5 tabs
Not ideal for highly dynamic or nested navigation
Performance may vary on older devices
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
wp_pivot_flutter
A Flutter package inspired from Windows Phone Style Pivot Tabs
2026 Update: This project is evolving beyond the Pivot control into a systematic,
research-driven recreation of the Windows Phone UI in Flutter. The first published
Pivot study uses the WP8.1 emulator; Lumia 1020 validation remains pending. See
docs/ROADMAP.md for the vision and methodology,
and the research site at chinmaykabi.com/wp_pivot_flutter
for the study, project status, and source material.
Requirements
Version 2.3.0 requires Flutter 3.22.0+ and Dart 3.4.0+. See the
changelog for release details and pub.dev
for registry availability. A merged version is not automatically published.
The repository's example app uses Flutter 3.44+ for its current Android
toolchain; the package library itself retains the 3.22 minimum.
Full Pivot: native layout and motion
WpPivotView owns both the headers and page content. It follows measurements from
Microsoft's real Pivot control running on the WP8.1 emulator: cyclic headers,
drag tracking, release-time selection, and separate outgoing/incoming content
animations. See the evidence study for recordings,
methodology and known limits. Emulator evidence is not labeled as Lumia evidence.
An optional PivotController drives selection; dispose controllers you create.
onChanged reports committed selections. Pages keep their state while hidden.
Arrow keys navigate, headers support keyboard focus and semantic selection, and
the system reduced-animation setting removes the spatial transitions. wrap: false disables cycling at the ends. Give the view a bounded width and height.
Geometry scales from a 480-unit reference viewport. Header and title font families,
weights, colors, and PivotMotion parameters can be customized. The package bundles
unmodified Selawik 1.01 under the SIL Open Font License;
no proprietary Segoe font files are redistributed. Selawik is a fallback, not an
identical copy of Segoe WP. Source and hashes are in assets/fonts/SOURCE.json.
Migrating the example
Replace the WpPivot app bar plus external PageView with one WpPivotView, move
the page widgets into children, and remove the two-controller synchronization.
The full view reproduces native content phases that a stock PageView does not.
The existing WpPivot header-only API and PivotController remain available.
Current fidelity limits
The native font and rasterizer differ from Flutter's. Capture timing is too coarse
to establish physical display latency; flick parameters remain provisional beyond
the recorded inputs. The regression suite replays 21 native core, 21 confirmation
and nine header/title input traces, including successful flicks, cancellations,
reversal, wrapping and ignored gestures during transitions. Header and title swipes
share the content gesture surface. A separate release-web runtime probe measures
real engine frame timing, not physical display latency or Lumia performance.
Independent hardware validation and broader gesture sampling remain separate work.
Launcher UI primitives
The experimental wp_components.dart entrypoint now contains the reusable UI
layer needed to compose a Windows Phone-style launcher without putting launcher
policy into this package:
WpPhoneTheme, WpTile, and WpTileGrid provide the palette, touch tilt,
controlled edit affordances, and explicit four-column layout.
WpAppListView, WpAppListHeader, WpAppListRow, and WpAlphabetGrid
reproduce the measured list and jump-grid geometry while leaving app data,
sorting, and selection destinations with the caller.
WpSplitSurfaceView provides the two-surface commit/cancel drag between Start
and the app list.
WpStaggeredSceneTransition applies a caller-driven perspective entry/exit
to one item. The caller supplies scene ordering and transform origin and still
decides when navigation happens.
Run flutter run -t lib/launcher_components.dart from example/ for a complete
composition using placeholder content. The package deliberately does not request
the Android home role, enumerate installed packages, launch intents, persist pins,
order apps, or schedule live data.
At the 480 x 800 evidence viewport, held-out comparisons found zero edge error
for 11 tile surfaces, 10 app-list slots, and 28 alphabet cells. Four held-out
lateral commit/cancel replays in both directions ended on the correct page with
zero final/separation error; presentation-registered tracking p95 ranged from
3.4 to 22.5 px within the 36 px host-capture uncertainty bound. Raw host timing
error is retained separately because emulator timestamps do not identify guest
presentation. The staggered scene pose is evidence-informed and visually
inspected, but exact native timing and transformed polygons are not claimed.
See the component contract and
runtime report.
Legacy header-only example
Selection state is managed by a PivotController - pass your own to drive the
pivot from the outside, or let the widget create one internally.
Application Bar, Panorama, ToggleSwitch, Slider, ProgressBar, TiltEffect, and the launcher UI primitives are available through the separate
package:wp_pivot_flutter/wp_components.dart import. From example/, run
flutter run -d chrome -t lib/components.dart to try them together.
They are experimental. The three micro controls have repeated WP8.1 emulator
measurements and held-out comparisons; the earlier component batch remains pilot
evidence. See the component studies for evidence,
known differences, and the reusable capture/replay workflow. Emulator results do
not establish Lumia hardware fidelity. The existing Pivot API is unchanged.
Contributors ✨
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
Starware
wp_pivot_flutter is Starware.
This means you're free to use the project, as long as you star its GitHub repository.
Your appreciation makes us grow and glow up. ⭐