review current design of Extensions workflow about podman-desktop

[vzhukovs]

One of the most potentially motivating things to the users will be an additional button near Install Custom... called Create Own or Develop an Extension, that will generate the skeleton of the empty extension or the simple one, like hello world. From what I see, we're missing such things. We have the ability to install an extension, but there is no information how to develop them on the UI. Could be useful I think.

[axel7083]

That's a lot of work, it is already such an impressive upgrade 👍 ! I have some comments, based mostly on how I feel with the implementation. (Nothing I listed is a necessity and falls under the need follow-up as it's still better than what we have so we can't hold for a while)

Navigation

IMO the Puzzle icon should be at the bottom as it is more a settings/configuration items rather than a resource or utility.

Extension List

The choice of the icons feel odds to me.

• Setting Gear for onBoarding
• Paper Edit for opening preferences

I would have something like a rocket or even a plane, to really show the action of on boarding

Rocket	Plane

I have some issue with the actions button, as the settings (gear) is disabled, I would not show it if the action is not available. Also to use the spaces available, I would have placed it at the top right of the card.

The different design buttons grouped all together feel very weird to me.

Extension	Resource

The open details icon also feel strange, as it should be on the right to keep the consistency with the resource page

Extension Details

I do not really like the extension details, as I have a feeling that the layout is not consistent with the application, having a scrolling container in the middle with some informations sticking on the right feel odds...

I am taking the JetBrain Plugin page as an example here

I am wondering if we should not move the version and author to the top, then they will still stick to the top, without having this weird (IMO) card on the right, which is not really bringing much information in reality.

Moreover, if we really want a dedicated places for more information, tabs could be a solution, as shown in the JetBrain example.

Custom Install

Maybe the placeholder's input should not be the place with all the details, and have some text above to give some details ?

Extension Catalog

The card layout feel too big, why so much unused spaces ?

Why do we use a header here Available extensions when we do not have one for the Installed one? I think we could remove it, as it does not bring a lot of information, since we already are in the Catalog tab, meaning that it is listing the available one