mirror of
https://github.com/breezy-weather/breezy-weather.git
synced 2025-12-07 13:50:05 +00:00
Design principles for new features
This commit is contained in:
parent
4093228275
commit
bbbb88810c
1 changed files with 3 additions and 1 deletions
|
|
@ -20,7 +20,7 @@ Breezy Weather wants to be:
|
|||
- mainly target small displays, so we don’t want to fit too many things, as we also want to let the design breathe a bit
|
||||
|
||||
|
||||
### New preference
|
||||
### New features
|
||||
|
||||
Probably, the most requested thing. “If you don’t want to make that feature for everyone, you can still make it a preference”.
|
||||
|
||||
|
|
@ -34,6 +34,8 @@ Additionally, any added preferences means implementing it, make the code execute
|
|||
|
||||
So, the idea is to make a fair use of preferences, so if it covers too narrow of a case, it won’t be implemented.
|
||||
|
||||
You can read [Niagara’s design principles](https://help.niagaralauncher.app/article/8-niagaras-design-principles) for a similar take on the matter (although due to the nature of this weather app, the “universal” criteria doesn’t always apply to us).
|
||||
|
||||
|
||||
### New weather sources
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue