Updated v1.0.0

[StelFoog]

The old v1.0.0 was planned and hasn't been updated in years (my bad 😓). It's time to plan a new v1.0.0 and bring the songbook out of "beta".

Although I have placed features into named categories such as "Required" that doesn't mean that it's the final place for that feature. This is just my own initial thoughts, they are likely to change and should be changed. Input is very appreciated.

When this ticket is fully planned out it should be closed and a new v1.0.0 milestone created.

Features

Required

• New design
  The old design works, but it's not great or maybe not even good. Apart from specific bad parts the design itself could use a new look. Notable bad parts are:
  • Filters they look awful and need to be entirely reworked
  • Lists good idea, but not a good execution
• Dark mode
• Use tailwind
• Have the search be fuzzy
• Update router (should maintain position of scroll), current one has been deprecated
• i18n support for the UI
• A "More" page, to learn more about the app and configure it to user preference
• QR codes
  • Generate QR codes for links
  • Scan QR code within app (needed mostly for PWA/native) to open list/song

Should have

• Gesture controls (useGesture?)
  • Pinch to increase font size of song lyrics
  • "Shortcuts" to navigation
• Improved SEO
  It should be easier to find the songs in our song book by searching google. Possibly using Next?
• Link to specific parts of song
• Ability to build for native iOS/android applications (or easily add in future)
  A good option would be tauri v2.
• Search by ID, should be possible in a small group to say the ID and for the rest to find the song

[StelFoog]

Maybe unlisted songs (not yet popular songs, not bad songs)? So that a new song can be added and only be listed when it has has had popularity at gasques or other events

[Cactooz]

Maybe unlisted songs (not yet popular songs, not bad songs)? So that a new song can be added and only be listed when it has had popularity at gasques or other events

Personally, since the songbook is digital and has a search function, I see no problem with having songs that are not as common. I would rather have multiple songs to choose from and others using our songbook, rather than only having the most common ones. For example, we would never had started singing some of the older songs if they were removed.

Though, it could be some form of filter, that you can click to see the "common" ones and then click the filter to see all songs or something along those lines. However, then we need to modify the songlist as well to have that data.

[Cactooz]

I would argue that the songbook should also mainly be in Swedish as the vast majority of the songs are Swedish to begin with. Then we can have a setting for you to switch it to English. At least to me, it looks quite weird that everything is in English and all songs and comments are in Swedish.

[Cactooz]

We could also have an about page/settings page, where there is some more information about the songbook. As we probably won't have that many settings other than dark mode and maybe language, they can incorporated together in one page.

[Cactooz]

Lists good idea, but not a good execution

In order for them to work well, I think we need to implement the QR code function as well, so you can easily share them at events.

[StelFoog]

I would argue that the songbook should also mainly be in Swedish as the vast majority of the songs are Swedish to begin with. Then we can have a setting for you to switch it to English. At least to me, it looks quite weird that everything is in English and all songs and comments are in Swedish.

I've added i18n support to the list of required features. Swedish should be default language, but system and user preference should be able to override it

We could also have an about page/settings page, where there is some more information about the songbook. As we probably won't have that many settings other than dark mode and maybe language, they can incorporated together in one page.

Very good idea, I've added a "More" page to the requirements. Though I think the name of such a page might need to be workshopped a bit.

In order for them to work well, I think we need to implement the QR code function as well, so you can easily share them at events.

Good point, I've moved it up!