Skip to content

[Feature] Make Projects the entrypoint of app deployment #558

Description

@aliilhami

This is a UX improvement request. Not a new feature.

Right now the templated app catalog apps are being deployed under Apps section in the menu. All other apps are tied to a project under the Projects menu.

As a regular end user, I would like to create a new project for an App too. Why would I need to manage apps on a separate entrypoint?

Normal UX should be:

  • Create a new project
  • Openship asks me to install a new App from the app catalog or do a Custom app
  • Projects created regardless I select a custom or a catalog app
  • All the services are being managed under Projects menu

Why I need this is there is a confusion right now. For example I have a server which has Uptime Kuma (custom service) and N8N (Catalog app). When I check the Home menu, I only see the Uptime Kuma under the projects tab, like there is no N8N deployment at all. After a short hearth attack, I realize there is a separate Apps section 😄

Image

Please fix this UX issue and group every deployment under Projects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions