Platform-adapting flutter widgets.
Switch branches/tags
Nothing to show
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib [Docs] update changelog with version logs. add proper license. Dec 3, 2018
.gitignore First commit. Sep 21, 2018 [Docs] update changelog with version logs. add proper license. Dec 3, 2018
LICENSE [Docs] update changelog with version logs. add proper license. Dec 3, 2018 [Docs] add in new methods to readme. Dec 3, 2018
pubspec.lock [setup] fix compile. update dependencies. Nov 20, 2018
pubspec.yaml [Version] bump to 0.0.5 Dec 3, 2018


Platform Conforming Widgets for Flutter!

Flutter makes no attempt to provide familiar widgets for a specific platform (unlike React Native, ionic, and other cross platform tooling). This has enormous benefits to unified rendering on all platforms, maximum flexibility, and eliminating a whole class of bugs and testing done for each platform. While this is great, many scenarios we want our apps to look and feel like an Android or iOS app. Platty allows you to render iOS (Cupertino) and Android (Material) like widgets with minimal effort and maximum control in a unified API.

No more checking for platform inside render blocks to render a CupertinoButton or FlatButton, let platty do the logic for you! Want to use bottom tabs in your app that resolve to platform specific UI? No problem!


List of Widget Files:


Back Button


Navigation Bars







Getting Started

Use platty to unify render-specific APIs for you. The library utilizes the BuildContext theming APIs to propagate platform information into the Widgets.

By default, all widgets conform to the default TargetPlatform. It looks up the Theme.of(context).platform for its default. Also, all widgets provide a renderPlatform prop that allows you to choose which one to render (if you wish).

Replace MaterialApp and CupertinoApp with PlatformApp:

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  Widget build(BuildContext context) {
    return PlatformApp(
      title: 'Flutter Demo',
      // specify Android Material Theme data here. it's a lazy evaluated function, only rendering if platform is Android.
      androidTheme: () => ThemeData(
            primarySwatch: Colors.lightBlue,
      home: ExamplePage(),

PlatformApp unifies all of the same properties between MaterialApp and CupertinoApp to allow you to choose.

NOTE: Not specifying a renderPlatform will render a CupertinoApp on iOS, and might cause issues with widgets that expect a material app instance.

NOTE: There is not a CupertinoTheme just yet in Flutter. Check out this pull request . once that is in the main flutter releases, we can then create PTheme that merges MaterialTheme and CupertinoTheme instances. For now it is highly recommended to specify targetPlatform: in the constructor of PlatformApp.

Now you replace widgets that are included in this library with their "P" counterparts:

Button/CupertinoButton -> PButton

FlatButton/CupertinoButton -> PFlatButton

AppBar/CupertinoNavigationBar -> PNavigationBar

SliverAppBar/CupertinoSliverNavigationBar -> PSliverNavigationBar

Slider/CupertinoSlider -> PSlider

Switch/CupertinoSwitch -> PSwitch

BottomNavigationBar/CupertinoTabBar -> PTabBar

Scaffold/CupertinoScaffold -> PScaffold

CircularProgressIndicator/CupertinoActivityIndicator -> PActivityIndicator

BackButton/CupertinoNavigationBarBackButton -> PBackButton

AlertDialog/CupertinoAlertDialog -> PAlertDialog

Any widgets that have ios-only or android-only counterparts, they are prefixed to android/ios accordingly:

For example PButton, androidShape applies to RaisedButton.shape property. It does not exist on a CupertinoButton. However CupertinoButton has a borderRadius and pressedOpacity. Those two props become iosBorderRadius and iosPressedOpacity.


Specific Platform Instance

To have a specific P-Widget utilize a specific platform theme only, such as Material or Cupertino, you can wrap it in a PTheme instance:

  data: PThemeData(
    platform:,  // or iOS
    child: child,

Or, more simply, utilize helper method:


Also all P-widgets and methods allow you to override the PTheme with a renderPlatform parameter in their constructor or calling method.

Creating Your Own Platform-Adapting Widgets

We can extend upon the logic included in this library to build our own, powerful platform-adapting widgets. Included in the library is the PlatformAdaptingWidget base class, which inherits from StatelessWidget.

class SamplePlatformWidget extends PlatformAdaptingWidget {
  final Color color;

  SamplePlatformWidget({Key key, @required this.color, TargetPlatform renderPlatform}) // should allow consumers to choose TargetPlatform
      : super(key: key, renderPlatform: renderPlatform);

  /// Render a material widget here. Most Material widgets require a Material Theme instance above it.
  get renderMaterial => (BuildContext context) {
        return BackButton(
          color: color,

  /// Render a cupertino widget here.
  get renderCupertino => (BuildContext context) {
        return CupertinoNavigationBarBackButton(
          color: color,
  /// Render a fuchsia widget here. (defaults to material)
    get renderFuchsia => (BuildContext context) {
          return BackButton(
            color: color,

Platform-specific logic

This library comes with a few standard ways to implement behavior based on platform. You can utilize platformWrap, which allows you to specify a child, and on 1 or all platforms, wrap it with another widget:

      child: PButton(
        padding: EdgeInsets.all(0.0),
        child: Text(title),
        onPressed: () {
          Navigator.push(context, PlatformRoute.of(context, builder: page));
      renderCupertino: (context, child) => Padding(
            padding: EdgeInsets.only(bottom: 8.0),
            child: child,

You can specify any of renderCupertino, renderMaterial, or renderFuschia (or none). Any render methods not specified default to the child.

Also, platformSelect is a helper that enables returning different objects based on platform in a unified way. In our PlatformAdaptingWidget, we utilize it to return a different widget based on platform. You can use it to return any return type based on platform:

  children: [
      renderMaterial: (context) => Text("I am android"),
      renderCupertino: (context) => Text("I am iOS"),
      renderFuchsia: (context) => Text("I am FUCHSIA")) 

renderMaterial and renderCupertino are required. renderFuchsia defaults to material.

or you can return a non-widget too:

  children: [
      renderMaterial: (context) => "I am android"),
      renderCupertino: (context) => "I am iOS",
      renderFuchsia: (context) => "I am FUCHSIA"))