Use-case:

I want to switch regularly between a dark theme and a light one. Clearly, it's useful for day/night.
But I want to customize both of them, because I don't like the built-in default themes.

Problem:

Right now, Chordle has two "default" themes and one "custom". I can customize any of them, but all the customizations are
reset and forgotten at the moment I switch to any other theme. So I change back to my custom theme, and all the customizations are gone, which is really confusing and irritating.
So long term usage of any two themes is out of question right now. I have to settle for a single customized one and hope not to forget and switch to another, so my customization don't disappear without a warning.

Possible solutions:

1) Quick solution - remember custom only
Just remember the customizations in the custom theme. At least I could switch between "my theme" and one of the default ones.

2) Remember customizations for all themes
After I customize any theme, switch to another and back again, my customizations will be there.
Cons: No way back to default settings. Maybe a new button "restore defaults" would be needed? Or is there even a need to go back to defaults?

3) Two custom themes + remember them, keep forgetting defaults
Instead of a single custom theme, let's have two, custom light & custom dark. And remember all customizations in these, as in solutions #1 and #2. But keep the current behavior for default themes, resetting them after switch, so you can never lose the defaults.
Pros: Don't need a new reset button, easy way to reset to default.
Cons: Different behavior for two types of themes. Could be confusing. But with proper naming (custom light/dark), it could be understandable.

4) Overkill solution - theme editor
Enable creating unlimited number of custom themes. With custom names and colors. The two default ones would just be the two pre-installed. All those themes would of course be remembered between theme switches, and could be even exported and imported, so users can share themes amongst each other.
Pros: Total control! Sharing!
Cons: A lot of work for developers! :-) And maybe the user base is not large enough for sharing themes?

I hope this makes the cut, I'd really like to switch two customized themes :-)
I'd probably vote for solution #2, but all options would work, so, up to you, developers :-) Hope you have enough time for any of those O:-)

A second plea for this! While Chordle allows slashes in the chord line to represent beats, it doesn't convert them properly to chordpro, nor does it import them from Chordpro.

I use forward slashes for beats, and back slashes to indicate a quick chord change (ie half bar). For example:

C C G \ Em A D / / C
This is a song that I once wrote to someone I forgot

which in Chordpro should be:

[C]This is a [C]song that [G]I once[] [Em]wrote to [A]someone [D]I for[/]got [/] [C]

EDIT For some reason, the above formatting gets changed when I press the 'post' button, but I've left the example so you can get the idea...

First of all, let me praise you for the amazing job you've done in creating this fantastic piece of software.

After having used the app for over a year almost weekly, I do have a good idea of a few of the shortcomings.

1. It's not really a shortcoming, but a feature that will imidately broaden your user base/clients. iOS version of the app for iPad.
   80% of the musicians I interact with on a daily basis use an iPad with OnSong. Many of them are really frustated and willing to pay money to try something else.




2. Sync accross accounts. For example, let say you're playing in a band, and all the musicians have Chordle. You should be able to creat a set list and share it with them all. This way they can see the list and changes to the list and keys in real time.




3. Chord Degree Notation. Beeing able to, as a toggle, change from your preferred notation to a degree notation that shows the chords as degrees of the Key you're playing in, displayed as Roman numerals. For example, if your playing in C, C will be I (1), G will be V, F will be IV, Em will be iii (or IIIm).

The reasoning: When playing on a musical set up, often times you have to communicate chord changes with your musicians, but not everybody is playing on the same key, whether it is because they're using capo, transposing, using an instrument with a different tuning etc. Most experienced musicias will know this by heart, but some have never been exposed to this.

Another reason is that some songs require a key change mid song. And the current system struggles identifying keychanges.