[GH-ISSUE #1314] iOS: Support for Display names #931

Open
opened 2026-05-07 00:28:53 +02:00 by BreizhHardware · 5 comments

Originally created by @patricksthannon on GitHub (Apr 11, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1314

💡 Idea
Using the Ntfy IOS app, I noticed that there isn't an implementation of display names like the web app and thought it would be a wonderful addition to those who have longer server names, that end up clogging the screen. For now I'll add more descriptive titles on all of my subscription notification messages.

display name settings on the ntfy web app

💻 Target components
Where should this feature/enhancement be added?
IOS app

Originally created by @patricksthannon on GitHub (Apr 11, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1314 <!-- Before you submit, consider asking on Discord/Matrix instead. You'll usually get an answer sooner, and there are more people there to help! - Discord: https://discord.gg/cT7ECsZj9w - Matrix: https://matrix.to/#/#ntfy:matrix.org / https://matrix.to/#/#ntfy-space:matrix.org --> :bulb: **Idea** Using the Ntfy IOS app, I noticed that there isn't an implementation of display names like the web app and thought it would be a wonderful addition to those who have longer server names, that end up clogging the screen. For now I'll add more descriptive titles on all of my subscription notification messages. <img width="431" alt="display name settings on the ntfy web app" src="https://github.com/user-attachments/assets/cb42247e-8a46-45c9-9205-9bc456ca3883" /> :computer: **Target components** Where should this feature/enhancement be added? IOS app
Author
Owner

@FallenGodyyc commented on GitHub (Sep 26, 2025):

will this be implemented?

<!-- gh-comment-id:3337660254 --> @FallenGodyyc commented on GitHub (Sep 26, 2025): will this be implemented?
Author
Owner

@lennon101 commented on GitHub (Jan 14, 2026):

I'm self hosting my ntfy instance and what I see in the iOS app is the full url/topic name in the display name for each topic. Anyway to change this? 🤔

Image
<!-- gh-comment-id:3747116717 --> @lennon101 commented on GitHub (Jan 14, 2026): I'm self hosting my ntfy instance and what I see in the iOS app is the full url/topic name in the display name for each topic. Anyway to change this? 🤔 <img height="600" alt="Image" src="https://github.com/user-attachments/assets/b067591c-1265-4220-9242-11a032d573dc" />
Author
Owner

@AnimaI commented on GitHub (Mar 6, 2026):

Hi @binwiederhier

I wanted to share some thoughts on this feature request and ask for your perspective.

The subscription list on iOS shows the full server URL as the title for each entry (e.g. https://ntfy.myserver.com/alerts). When using a self-hosted server with multiple topics, all entries look similar and are hard to tell apart at a glance.

What I am looking for is a simple "Display name" field per subscription. The user sets it once when subscribing or in the subscription settings. After that, the list shows the custom name instead of the URL. The Android app has exactly this under subscription settings.

I looked at the source code and the change seems manageable. Here is what I had in mind:

Subscription.swift — return custom name if set, otherwise fall back to the current behavior:

func displayName() -> String {
    if let name = customDisplayName, !name.isEmpty {
        return name
    }
    return topicShortUrl(baseUrl: baseUrl ?? "?", topic: topic ?? "?")
}

ntfy.xcdatamodeld — add one optional attribute to the Subscription entity:

<attribute name="customDisplayName" optional="YES" attributeType="String"/>

SubscriptionAddView.swift — add a text field for the display name.

That looks like roughly 40 lines across three files. I am happy to contribute a PR if that helps move things forward.

Two questions: Does this approach work for you architecturally? And do you have a rough sense of when something like this could land?

Thanks for maintaining ntfy!

<!-- gh-comment-id:4008607010 --> @AnimaI commented on GitHub (Mar 6, 2026): Hi @binwiederhier I wanted to share some thoughts on this feature request and ask for your perspective. The subscription list on iOS shows the full server URL as the title for each entry (e.g. `https://ntfy.myserver.com/alerts`). When using a self-hosted server with multiple topics, all entries look similar and are hard to tell apart at a glance. What I am looking for is a simple "Display name" field per subscription. The user sets it once when subscribing or in the subscription settings. After that, the list shows the custom name instead of the URL. The Android app has exactly this under subscription settings. I looked at the source code and the change seems manageable. Here is what I had in mind: **`Subscription.swift`** — return custom name if set, otherwise fall back to the current behavior: ```swift func displayName() -> String { if let name = customDisplayName, !name.isEmpty { return name } return topicShortUrl(baseUrl: baseUrl ?? "?", topic: topic ?? "?") } ``` **`ntfy.xcdatamodeld`** — add one optional attribute to the Subscription entity: ```xml <attribute name="customDisplayName" optional="YES" attributeType="String"/> ``` **`SubscriptionAddView.swift`** — add a text field for the display name. That looks like roughly 40 lines across three files. I am happy to contribute a PR if that helps move things forward. Two questions: Does this approach work for you architecturally? And do you have a rough sense of when something like this could land? Thanks for maintaining ntfy!
Author
Owner

@lennon101 commented on GitHub (Mar 13, 2026):

@AnimaI nice work! did you end up submitting a PR?

<!-- gh-comment-id:4053024885 --> @lennon101 commented on GitHub (Mar 13, 2026): @AnimaI nice work! did you end up submitting a PR?
Author
Owner

@AnimaI commented on GitHub (Mar 13, 2026):

PR submitted: https://github.com/binwiederhier/ntfy-ios/pull/29

<!-- gh-comment-id:4054915142 --> @AnimaI commented on GitHub (Mar 13, 2026): PR submitted: https://github.com/binwiederhier/ntfy-ios/pull/29
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#931
No description provided.