You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting by improving UI of how users browse and install is valuable since more plugins they use more signalK is valuable for them.
Why now ?
Starting by a section with little dependencies will help understand context of use for plugins and next improve the "manage plugins" section. So global experience is 10x better.
What solution looks like ?
The text was updated successfully, but these errors were encountered:
leonardgable
added a commit
to leonardgable/signalk-server
that referenced
this issue
Feb 12, 2024
User wants to browser and install plugins faster. User feedback
mentioned bad experience and confusin filters and search on the appstore
page.
A new AppStore and more modern page has been designed.
Easier and less confusing plugin/webapp search is made with a refactor
of the filters and the implementation of a new grid component.
This constitute a boiler plate for future development on the appstore.
The usage of ag-grid improves the user and developer experience to
develop new features on top. The library offers great built-in functionality such as cell renderers columns sorting,
filtering, quick search etc...
Fortawesome was installed using package json
as documented on fontawesome website.
Work in progress loose end further implementation are required.
Resolves: SignalK#1675
Is there a problem ?
Multiple feedback showing that UI issues exist on the Config section but also on the Appstore section. Discovering new tools is not as seamless as it should and sub-categories make things more complex : https://abdoug.notion.site/3a5d658b6a6a455194ba19aea93641df?v=75fca750dcdb470288effc0bd897f8a9&pvs=4
Problem worth solving ?
Starting by improving UI of how users browse and install is valuable since more plugins they use more signalK is valuable for them.
Why now ?
Starting by a section with little dependencies will help understand context of use for plugins and next improve the "manage plugins" section. So global experience is 10x better.
What solution looks like ?
The text was updated successfully, but these errors were encountered: