Skip to content

Conversation

@diogogmatos
Copy link
Member

@diogogmatos diogogmatos commented Sep 8, 2025

Since the export const metadata feature of Next.js only works server-side, I have placed the metadata for each page in its own layout.tsx file. This way, the page.tsx file of each page is free to be used client-side and has the bonus of not getting cluttered with metadata stuff.

Added a install prompt with an "add to home screen" button that will:

  • If supported, directly open a system prompt to install the app
  • If not supported, show a step by step guide on how to install the app, that changes according to the operating system being used (iOS or Android)

Example on iOS:

IMG_7629 IMG_7630

Example on Android:

Screen_Recording_20250908_201928_Chrome.mp4

@diogogmatos diogogmatos self-assigned this Sep 8, 2025
@diogogmatos diogogmatos marked this pull request as ready for review September 8, 2025 19:21
@diogogmatos
Copy link
Member Author

It would be nice to merge this before monday 👀 @gxnca @nunom27 @enricoprazeres

@diogogmatos
Copy link
Member Author

Added the install button and updated the prompt logic to only be shown automatically at most 3 times, which basically means that:

  1. Prompt gets shown for the first time, User dismisses prompt (1x)
  2. 7 days later: Prompt gets shown again, User dismisses again (2x)
  3. 7 days later: Prompt gets shown for the final time, User dismisses (3x)
  4. Prompt never gets shown automatically again (only using the button now)

And all of this only if the user is always using the browser and not the app, on Android or iOS, to open the platform during the 3 consecutive weeks.

I think this is a good balance of giving a little motivation to the users to use the web app but also not annoying them forever if they insist in using it on the browser.

@joaodiaslobo
Copy link
Member

I think the the PWA prompt is a bit too intrusive. If I recall correctly, it would be the first time we do this in any of our apps, right?
I'm not too sure we should be immediately bombarding students with a pop-up like this.

Maybe let's just keep it as a button like we did with Calendarium? 🤔

@diogogmatos
Copy link
Member Author

@joaodiaslobo

I think the objective of the prompt is to let our users know of a feature they won't even know is there otherwise. Like Calendarium, the UX in Pombo benefits a lot from the extra vertical space the PWA provides when showing events and classes in the calendar, besides it's an overall better experience. I think this prompt would really benefit the adoption rates of this feature, since the concept of a PWA is not commonly known.

As for it being too intrusive, in my opinion it is almost as intrusive as a notification would be. As a user, I wouldn't mind being shown this one time, I think I would even think it's a cool thing we have that option.

I discussed this yesterday with @nunom27 and @gxnca and we had come to an agreement. But if you guys want to reconsider, it's okay. I've made my point.

Copy link
Member

@gxnca gxnca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@diogogmatos
Copy link
Member Author

🙏🏼 😭 portugal, lisboa, conseguimos.

@diogogmatos diogogmatos merged commit ead3d0c into main Sep 27, 2025
1 check passed
@diogogmatos diogogmatos deleted the dm/seo+pwa branch September 27, 2025 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants