홈 화면에 추가 (iOS, iPadOS)

:discourse2: 요약 **홈 화면에 추가 (iOS, iPadOS)**는 iOS 기기 사용자에게 팝업을 표시합니다. 이 팝업은 닫을 수 있으며, PWA를 통해 Discourse 포럼을 보고 있는 경우 표시되지 않습니다.
:hammer_and_wrench: 저장소 GitHub - discourse/discourse-apple-add-to-homescreen · GitHub
:open_book: Discourse 테마를 처음 사용하시나요? Discourse 테마 사용 입문가이드

이 테마 컴포넌트를 설치하세요

기능

이 컴포넌트는 iOS 기기 사용자에게 팝업을 추가합니다. 이 팝업은 닫을 수 있으며, PWA를 통해 Discourse 포럼을 보고 있는 경우 표시되지 않습니다.

iPhone

iPad

설정

이름 설명
팝업 타이머 팝업이 표시되기까지 얼마나 오래 기다릴까요? (밀리초 단위)
번역 기본값
pwa_text %{siteTitle}을(를) iOS 기기에 설치하세요. 공유를 누른 다음 홈 화면에 추가를 선택하세요.

이 테마에는 표시될 텍스트와 팝업이 표시되기까지 기다릴 시간을 결정하는 타이머를 위한 두 가지 설정이 포함되어 있습니다. 이 설정들은 기본적으로 설정된 값이 제공됩니다.

이 팝업은 PWA를 사용하지 않고 iPhone 또는 iPad에서 Discourse 포럼을 보고 있는 iOS 사용자에게만 표시됩니다. 사용자가 x 아이콘을 클릭하면 다시 표시되지 않습니다.

표시되는 텍스트 편집

이 영역을 편집할 때 다음 사항을 유의해야 합니다:

이 텍스트를 편집하고 siteTitle이 여기에 유지되기를 원한다면, 원하는 위치에 %{siteTitle}을(를) 유지하세요.


:discourse2: 우리가 호스팅하고 있나요? 테마 컴포넌트는 Standard, Business, Enterprise 플랜에서 사용할 수 있습니다.

27개의 좋아요

Fantastic idea! Thank you! The issue always has been and will be discoverability with this feature.

8개의 좋아요

In core for Android we use a trust level >= 1 check for showing the pop-up, which acts like a timer but is better IMO:

https://github.com/discourse/discourse/blob/main/app/assets/javascripts/discourse/app/components/pwa-install-banner.js#L41-L46

I wonder if this component should use the same :thinking:

Also, I’d love to merge both Android and iOS PWA install banners into a single component in core!

12개의 좋아요

I suggest that the default text should mention push notifications, and avoid mentioning “device.”

Perhaps something like:

“Add %{siteTitle} to your Home Screen to sign up for push notifications! Tap share and then Add to Home Screen.”

It’d be especially helpful if the Discourse team did some A/B testing around this, to find language most likely to get users to sign up for push.

Here are questions I have:

  • Is it better to say “Add” or “Install”?
  • Is it better to mention push notifications here, or to delay mentioning them?
  • If we do mention installation, should we say that this is an “app” being installed? A “web app”?
  • iPad has more room. Is it better to use more words?
6개의 좋아요

On iPad, this banner is not great. The banner appears at the bottom of the screen, but the share button is at the top. I see there’s a little up arrow :up_arrow:, as if to indicate “hey, the button’s up in the header” but I doubt that will be enough. (Have y’all done user testing on this? Have you seen it work for non-expert iPad users?)

It also doesn’t help that we’re asking the user to “tap share,” but the button isn’t visibly called “share.” It’s a little box with an arrow.

image

Years ago, I used to use https://github.com/cubiq/add-to-homescreen which would draw a pop-up like this:

I’d love it if Discourse did something more like this.

Now, the flyout is kinda fragile (what if the button moves?), but I think it’s also OK if the button isn’t exactly where the flyout points, as long as it’s in roughly the right place.

Historically, it was also perilous that the button might look different from one version of iOS to the next. But the share button hasn’t changed shape since iOS 7, and there’s no particular reason to think it will change in iOS 17, so I think an approach like this would work on iPad, with a little flyout pointing toward where the Share button probably is in the header bar.

3개의 좋아요

This is good feedback Dan.

I could see the benefit of showing this flyout at the top of the page when an ipad is being used.

To be quit frank, the reason we didn’t include that icon in this version of the component is that this icon is only available in Font-Awesome 6, and Discourse does not currently support that version yet.

2개의 좋아요

This sort of desire is exactly why I set this text to be editable by an admin. Each person may have a different take on what this popup should say, so feel free to edit to your liking.

1개의 좋아요

I don’t think I have the power to A/B test it on my forum. Is that something y’all could A/B test?

Does it let the user know why they might want to do that?

1개의 좋아요

Im not sure I follow your question. I would venture if they are on the forum already, the reason behind installing it on their iOS device would be self evident.

My point is that Apple users are only familiar with installing apps via the App Store. Very few will understand what a pwa is. Fewer still will know the potential benefit of installation.

Putting browser notifications behind A2HS is a great move on apples part. It completely solves the early issues with notifications on desktop.

How do we let users know what’s in it for them beyond another icon on their Home Screen?

3개의 좋아요

I completely (but I hope politely) disagree. I run a Discourse forum and have it and others added to the Home Screen. I only thought about doing that after discussions here, and haven’t seen any benefits (the notifications don’t work) so have continued to use the Hub app.

2개의 좋아요

I think we might just be both making assumptions here without gathering feedback from admins who have installed this.

That being said, the text is 100% customizable, so if an admin feels the need to further clarify, they can do so quite easily.

My feedback has been specifically from clients, after mentioning that the PWA was a necessary step to enable notifications.

It’s going to vary between communities, but in the era of ‘ask app not to track’ users aren’t as likely to blindly follow instructions without some perceived benefit. Telling a user how to install the PWA without explaining why definitely buries the lede.

I had this issue with a couple of my self-hosted instances and modifying the push notification time window mins to 0 fixed it for me and most of my users. As a side-effect it also makes the behavior closer to how the Hub app notifications work for timing.

3개의 좋아요

I had to add this plugin manually.

I had a blank repository when clicking with the installer.

Sorry about that, it should be fixed now.

1개의 좋아요

Nice component! I like how it’s implemented close to where the share buttons are. Agree that we should integrate this into core and the android banner.

I have an old unimplemented mockup from a while ago that might address some thoughts mentioned here:

The idea with the text here :point_up: was to have some sort of clear “what’s in it for me” — and literally show the site logo in an app-like way to make it a little clearer what this is all about.

That was mocked up for Android, which makes things easier because you can include a button that directly adds the PWA to your device.

Unfortunately iOS still requires you to go through their share sheet to get to this action… but I think we can have a button that triggers the share options? (we already do this for clicking the share icon on posts in iOS…)

4개의 좋아요

Not on iOS. You can open a share sheet with navigator.share(), but it doesn’t have the “Add to Home Screen” button on it. To A2HS, the user has to manually click the little share button; hence the need for something like this.

1개의 좋아요

Turns out I was just still on an old iOS version (pre-16.4): Live notifications: "Notifications are not supported on this browser. Sorry."