I asked us to only put apps with UIs in My Apps, can be front-end and backend containers that have UIs to interact with, put databases, apis, anything that doesn't have an AI in the websites category but rename to services.
Steps to Reproduce
N/A
Expected Behavior
Just like I said
Actual Behavior
N/A
Archipelago Version
N/A
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
### Description
I asked us to only put apps with UIs in My Apps, can be front-end and backend containers that have UIs to interact with, put databases, apis, anything that doesn't have an AI in the websites category but rename to services.
### Steps to Reproduce
N/A
### Expected Behavior
Just like I said
### Actual Behavior
N/A
### Archipelago Version
N/A
### Hardware
x86_64 (Intel/AMD)
### Relevant Logs
_No response_
### Screenshots
_No response_
Done — fixed in commit c10f2ac2 (local main; ships with the next push/release).
The categorisation logic was already correct (built under #45): a package lands in My Apps only when its manifest declares a UI (interfaces.main.ui) or it is a curated app; databases, APIs and other headless backends fall through to the other tab. What was left was the label — the tab was still called "Websites" while the code had half-migrated to services.
This finishes the rename:
Tab label is now "Services" in Apps, Marketplace, Discover and the mobile nav.
services is the canonical tab state + query param (?tab=services).
Old ?tab=websites bookmarks still resolve (back-compat acceptor kept).
appsConfig.test.ts: 8/8 pass.
So headless services (databases/APIs/no-UI containers) sit under Services, and only interactive UI apps stay in My Apps — as requested.
**Done — fixed in commit `c10f2ac2`** (local main; ships with the next push/release).
The categorisation logic was already correct (built under #45): a package lands in **My Apps** only when its manifest declares a UI (`interfaces.main.ui`) or it is a curated app; databases, APIs and other headless backends fall through to the other tab. What was left was the label — the tab was still called **"Websites"** while the code had half-migrated to `services`.
This finishes the rename:
- Tab label is now **"Services"** in Apps, Marketplace, Discover and the mobile nav.
- `services` is the canonical tab state + query param (`?tab=services`).
- Old `?tab=websites` bookmarks still resolve (back-compat acceptor kept).
- `appsConfig.test.ts`: 8/8 pass.
So headless services (databases/APIs/no-UI containers) sit under **Services**, and only interactive UI apps stay in **My Apps** — as requested.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
I asked us to only put apps with UIs in My Apps, can be front-end and backend containers that have UIs to interact with, put databases, apis, anything that doesn't have an AI in the websites category but rename to services.
Steps to Reproduce
N/A
Expected Behavior
Just like I said
Actual Behavior
N/A
Archipelago Version
N/A
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
Done — fixed in commit
c10f2ac2(local main; ships with the next push/release).The categorisation logic was already correct (built under #45): a package lands in My Apps only when its manifest declares a UI (
interfaces.main.ui) or it is a curated app; databases, APIs and other headless backends fall through to the other tab. What was left was the label — the tab was still called "Websites" while the code had half-migrated toservices.This finishes the rename:
servicesis the canonical tab state + query param (?tab=services).?tab=websitesbookmarks still resolve (back-compat acceptor kept).appsConfig.test.ts: 8/8 pass.So headless services (databases/APIs/no-UI containers) sit under Services, and only interactive UI apps stay in My Apps — as requested.