These are the subjective principles I will follow when designing this package, so we can discuss them in this issue

My main inspiration for designing this package will be firebase_ui_firestore

1. Customizability - The kit shouldn't force the user to use a specific UI design.
2. Ease of use - The kit should provide good looking interfaces by default with minimal modification.
3. Follow flutter design patterns - All stateful widgets SHOULD have their states exposed (for use with GlobalKey<TState>) AND have controllers (for use with model-view-controller cases like InheritedModel)
4. Correctly typed - Widgets should be generic, and not force the user to use Map<String, dynamic>
5. Tested - while testing UI is always hard, I will try my best to include as many meaningful tests as possible.
6. Responsive - the package should provide UI for all types of screens, ListViews for mobile, Tables for desktop, etc ...
7. Reactive - while the sdk currently uses Futures only, if this product discussion goes through meilisearch/product#143 , we might be getting a Stream-based API
8. Minimize 3rd party dependencies, but not completely ignore them - Packages like https://pub.dev/packages/flutter_typeahead , and https://pub.dev/packages/infinite_scroll_pagination can be used to not reinvent the wheel

cc @brunoocasali

What name to use for the new package on pub.dev? Since we already have meilisearch, I suggest naming it meilisearch_ui

Cc @brunoocasali

A central issue to track everything that should be added during/after the development of the repo:

• Correct Meilisearch + Flutter logo in the README
• Contributing guidelines
• Add useful information in the README:
  • How to install the library
  • How to use the library (basic concepts)
• Add dependabot