Changes between Initial Version and Version 1 of Ticket #61040, comment 23
- Timestamp:
- 05/02/2024 08:19:25 AM (8 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #61040, comment 23
initial v1 11 11 So, if the objective is to redesign for the most user-friendly experience (ignoring technical limitations at this stage), in my opinion, for a plugin with no dependencies, on the ADD page, there should be a two-step process: Install and Open. Opening technically activates and runs the plugin, including any onboarding. For plugins with dependencies, the flow should be Install, notify users of dependencies, and give them an opportunity to install. When all dependencies are met, the plugin should Open, running a plugin configured within the dependency setup to be the master, with whatever onboarding is defined in the master plugin. 12 12 13 Now, my second point: This is just my opinion on what users want. In a commercial world, we would gather user requirements through various methods beyond those that participate in trac kdiscussions. (But I do assume App Stores have rather worked out the simple use case.)13 Now, my second point: This is just my opinion on what users want. In a commercial world, we would gather user requirements through various methods beyond those that participate in trac discussions. (But I do assume App Stores have rather worked out the simple use case.)