cupertino_plus

⚠️ experimental and work in progress ⚠️

note: the pub listing for this package only exists to reserve the name for the package.
using this package as a dependency in its current state is redundant and not recommended.

a collection of pixel-perfect ios-styled components and properties for flutter, following the official guidelines.

by jeroen meijer and reuben turner.

about the cupertino_plus project

last updated: 2021-09-28

reasoning

cupertino_plus is a flutter project that spawned out of a desire to create a set of pixel-perfect ios-styled components and properties for flutter.

while support for widgets following material design is absolutely stellar and offers a lot of flexibility, we feel like the current ios component support in flutter is severely lacking in some parts, ranging from components and scaffolding that have been available since ios 13 (which is 2 versions behind at the time of writing) that still have not been added, existing components being out of date, and navigation paradigms that are either completely unavailable or are implemented in a package (on pub.dev) with poor code quality or support.

goals

our goals are therefore to start creating ios components and features that are indestinguishable from their native counterparts, allowing all flutter devs, both new and old, to be able to create flutter applications that look and feel like native ios apps.

there are some examples of ios-styled flutter apps, such as the official veggie seasons sample app. however, the components used are prodominantly custom to the project, and are not available in the official flutter sdk. additionally, most of the components are not pixel-perfect, and feel (sometimes heavily) outdated.

we want to help out in creating a better ios-feeling experience for flutter developers. we love dart, we love flutter, we love ios, and we would especially love to be able to combine the best of all these in a way that is easy to use, and that is not only pixel-perfect, but also maintainable, and well tested.

but why not just contribute to the official flutter sdk?

that is definitely our end goal, but we feel that the current flutter sdk is not the best place to start.

at this point, we only have some ideas, ambitions and short-term plans, and this whole project spawned out of the fact that we were simply missing some components. we need time to gather our thoughts and get a plan in place, and we need to get the community involved.

first and foremost, we would like to get our goals aligned, gather data and feedback, get a group of people together, and start working on the project.

roadmap

our current roadmap is extremely rough and we are working on it — the project only just started, after all.

in the meantime, please have a look at the project board and issue #1 for more details.

how can i contribute?

first off, thank you so much for asking! ❤️

since we are still working out the details, we would like to ask you to hold off on contributing to the project until we have a more solid roadmap. please check back here in the future. your patience and excitement is appreciated!