This document contains information regarding the development process of Freazy, the Flutter-based mobile app for keeping up with everything in your freezers. Here you can find known issues, upcoming features or changes and a list of changes per (application) version.
If you have suggestions, or found a bug, I recommend going to the GitHub repository and creating an issue or bug report there. Alternatively, you can email me at [email protected].
Table of contents
Known issues
Here you can find known issues such as bugs or code problems with regard to the latest (released) version of Freazy. Some issues may be marked, this shows they have been fixed in code and a patch will be coming soon.
Bugs
- [x] Product titles are not wrapped onto multiple lines or cut off using ellipses (…). v1.1.0
- [x] Selecting a locale does not show a language it’s native implementation. v1.1.0
- E.g. if ‘English’ is selected, Dutch should still show as ‘Nederlands’.
- [ ] Product (fuzzy-) search works poorly, on word basis, not letters.
- E.g. ‘Pizza XXL’ doesn’t return when the search query is ‘XL’.
- [ ] Pressing the ‘text’ on a checkmark widget does not trigger the checkbox, this should be enabled to allow for easier usage.
- [x] Expired products should have ultimate priority in notifications. v1.1.0
- E.g. ”You have X expired products” should always have priority over “Your pizza will expire soon”.
- [x] Messages don't automatically dismiss. v1.1.0
- [ ] When clearing a field using the ‘X’, the form is still marked as ‘dirty’ and thus you cannot exit the add page without a confirmation dialogue.
- [ ] Autocomplete is broken, doesn't load
Code quality
- Messages need to be more compact and improved.
- E.g. the ‘onClick’ action takes up a lot of space compared to its usage.
- The text should have more space and less padding.
- A (small) icon should be added in front for extra clarity.
- E.g. a checkmark, cross, (I)
- Update the MessengerService to also allow for (generic) full-screen dialogues.
- These should only be used and implemented in places where the users’ interaction is required and not optional, and where it is important to block the active content.
- This dialogue should have
- Title: string
- Content: List<Widget>
- OnConfirm: VoidCallback
- OnCancel: VoidCallback
- OnConfirmColor: Color?
- OnCancelColor: Color?
- Implement in these pages:
- ‘Reset app’ confirmation
- ‘Leave with pending changes’ confirmation
- ‘Import database’t
- Translations/localization
- Snacks/toasts should be horizontally dismissible.
- E.g. remove message without any further state changes