🚀 Feature: App descriptions, categorization, and visibility control for 'My Apps' page #53

New Issue

OVERLORD · 2025-10-06T23:59:28+03:00

OVERLORD commented

2025-10-06 23:59:28 +03:00

Originally created by @secondtruth on GitHub.

Feature description

My suggestion is enhancing the OIDC client creation page to include additional fields for description, categorization, and visibility control.

Details

The following fields should be added to the OIDC client creation form in the admin UI:

Description: A text input or textarea to add a brief description of the application, providing context for the end user about what it is/does.
Category: A field to assign the application to a category. The input should function as a combo box, allowing users to type a new category name or select from a list of existing categories. This feature would support the grouping of applications on the 'My Apps' page, for example, by function or department (e.g., "Development Tools," "Media Services").
Hide on My Apps page: A checkbox that, when enabled, prevents the application from being displayed on the 'My Apps' page. This is useful for backend services or other applications that users do not need to interact with directly from the user portal.

Pitch

The primary goal of this feature is to improve the usability and organization of the 'My Apps' page, especially in environments with a large number of available services.

Originally created by @secondtruth on GitHub. ### Feature description My suggestion is enhancing the OIDC client creation page to include additional fields for description, categorization, and visibility control. ### Details The following fields should be added to the OIDC client creation form in the admin UI: - **Description:** A text input or textarea to add a brief description of the application, providing context for the end user about what it is/does. - **Category:** A field to assign the application to a category. The input should function as a combo box, allowing users to type a new category name or select from a list of existing categories. This feature would support the grouping of applications on the 'My Apps' page, for example, by function or department (e.g., "Development Tools," "Media Services"). - **Hide on My Apps page:** A checkbox that, when enabled, prevents the application from being displayed on the 'My Apps' page. This is useful for backend services or other applications that users do not need to interact with directly from the user portal. ### Pitch The primary goal of this feature is to improve the usability and organization of the 'My Apps' page, especially in environments with a large number of available services.

OVERLORD closed this issue

2025-10-06 23:59:29 +03:00

OVERLORD commented

2025-10-06 23:59:30 +03:00

@secondtruth commented on GitHub:

What do you feel is one of the most important aspects of this?

For me, the most important aspect is: Hide on My Apps page.

@secondtruth commented on GitHub: > What do you feel is one of the most important aspects of this? For me, the most important aspect is: Hide on My Apps page.

OVERLORD commented

2025-10-06 23:59:30 +03:00

@secondtruth commented on GitHub:

Hi @kmendell,

I've thought about this again. I realized that the categorization feature would also be very valuable in my use cases.

That said, I fully understand your concern about UI bloat and the project's principle of simplicity. To reconcile both perspectives, I’d like to suggest adding an "Advanced Mode" (or "Expert Mode") toggle in the application configuration.

By default, Pocket ID would remain clean and minimal, showing only the core features. When "Advanced Mode" is enabled, additional options (such as the suggested ones) would appear.

This way, the default experience stays streamlined while still allowing power users to unlock more functionality if they need it.

Would this still be a middle ground that aligns with Pocket ID's philosophy?

@secondtruth commented on GitHub: Hi @kmendell, I've thought about this again. I realized that the categorization feature would also be very valuable in my use cases. That said, I fully understand your concern about UI bloat and the project's principle of simplicity. To reconcile both perspectives, I’d like to suggest adding an "Advanced Mode" (or "Expert Mode") toggle in the application configuration. By default, Pocket ID would remain clean and minimal, showing only the core features. When "Advanced Mode" is enabled, additional options (such as the suggested ones) would appear. This way, the default experience stays streamlined while still allowing power users to unlock more functionality if they need it. Would this still be a middle ground that aligns with Pocket ID's philosophy?

OVERLORD commented

2025-10-06 23:59:31 +03:00

@kmendell commented on GitHub:

As the goal of pocket id is meant to be simple and not a bloated UI, certain decisions have o be taken into account, and adding so many UI elements for customization of a client goes againts that principle. Though im sure we can find some common ground and make it semi customizable.

What do you feel is one of the most important aspects of this?

@kmendell commented on GitHub: As the goal of pocket id is meant to be simple and not a bloated UI, certain decisions have o be taken into account, and adding so many UI elements for customization of a client goes againts that principle. Though im sure we can find some common ground and make it semi customizable. What do you feel is one of the most important aspects of this?

OVERLORD commented

2025-10-06 23:59:32 +03:00

@kmendell commented on GitHub:

Closing this issue as it is a duplicate of https://github.com/pocket-id/pocket-id/issues/843. Well track that progress there.

@kmendell commented on GitHub: Closing this issue as it is a duplicate of https://github.com/pocket-id/pocket-id/issues/843. Well track that progress there.

OVERLORD referenced this issue

2025-10-07 00:25:23 +03:00

[PR #53] [MERGED] feat: custom claims #958

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/pocket-id#53