zhuyijun 5a1ba47561 1、新增直播播放 | 7 months ago | |
---|---|---|
android | 7 months ago | |
assets | 7 months ago | |
ios | 7 months ago | |
lib | 7 months ago | |
plugin | 7 months ago | |
test | 7 months ago | |
web | 7 months ago | |
windows | 7 months ago | |
.flutter-plugins-dependencies | 7 months ago | |
.gitignore | 7 months ago | |
.metadata | 7 months ago | |
README.md | 7 months ago | |
adaptive-overview.gif | 7 months ago | |
codelab_rebuild.yaml | 7 months ago | |
flutter.yaml | 7 months ago | |
key.jks | 7 months ago | |
pubspec.lock | 7 months ago | |
pubspec.yaml | 7 months ago |
Instead of transliterating widgets one by one between Cupertino and Material, Android and iOS apps often follow different information architecture patterns that require some design decisions.
This sample project shows a Flutter app that maximizes application code reuse while adhering to different design patterns on Android and iOS. On Android, it uses Material's lateral navigation based on a drawer and on iOS, it adheres to Apple Human Interface Guideline's flat navigation by using a bottom tab bar.
Visually, the app presents platform-agnostic content surrounded by platform-specific 'chrome'.
See https://youtu.be/svhbbFZg1IA for a longer non-gif format.
Defines the top level navigation structure of the app and shows the contents of the songs tab on launch.
Shows platform-agnostic cards that is tappable and that performs a hero transition on top of the platform native page transitions.
Both platforms also show a button in their app/nav bar to toggle the platform.
Shows platform-agnostic news boxes.
Shows a number of user preferences.
Shows a number of app settings via Material switches which auto adapt to the platform.