Thank you for checking out the game and for the feedback! :)

> please let us manually scroll the keyboard

Letting people change octaves instead of letting the game pick the right octave for each note was something I really struggled with, because I think it would make the game a lot harder.

For example, if the right note was "C5" and the user picked "C4", they would hear "C4" when they played the note on the keyboard to input it, but if they clicked the button on the right side to listen back on their guess, should they hear the note in the correct "C5" pitch, or the wrong "C4" pitch?

If we accepted the entry even though it was in the wrong octave, it might be a little confusing since the playback would be different from what they heard when they input the note.

However, if we did not accept the entry because it was the wrong octave, we'd have to refactor to adjust the tiles to show the full octave number (like "C4" or "C5" instead of "C" or "Bb4" and "Bb5" instead of "Bb")... and maybe this would be a good candidate for a harder mode than the current "hard" mode.

=============

Letting users scroll the keyboard to change octaves is something I definitely want to put into the future "practice" mode, though! Since the feedback will be quicker, it will be easier to tell a user immediately if they chose the right note but the wrong octave.

Tiles should show the full note like C4#

Otherwise what we see and what we hear don't match (showing CC and playing C4C5 for instance)

On mobile, the backspace on the piano keyboard should work!

It does! (Was that always there? Apologies ;-)

> I didn’t realize I needed to scroll down to see the keyboard (on mobile)

Oof... we'll have to make sure the piano keyboard is more visible earlier in mobile mode :sweat-smile: I'm glad it worked for you in mobile, though! I've gotten mixed feedback about the notes sometimes not playing in mobile.

> I also wish there was a way to play more than one. Maybe allow me to do the previous days?

That's a great idea! We were originally thinking we needed to add support for user accounts to support this, but actually, it shouldn't be hard to allow people to toggle back to previous days as is. Thanks for the feedback!

Thanks for the question! The octave will shift according to the solution note.

For example, if the solution was:

Bb3 Bb4 Dd5 Db5 C5 Bb4 (the first 6 notes of a "Believer" melody)

... the piano octaves will be [3,4,5,5,4]

In today's puzzle, the first note is in octave 4, and the second note is somewhere in octave 3.

In a VERY early version of the game, we didn't show where the octave positioning was, only 7 white keys, and people got confused because even when they accurately thought that the next note was higher based on the interval, it actually ended up being a "lower" note because it was a lower note on a higher octave scale.

So now we give you the octave positioning.

Thank you for the thoughtful comment, @jrajav!

We originally just thought of the game as "musical wordle" since we didn't want to infringe on the "wordle" name itself in case there were copyright issues, and PPP seemed like nice alliteration, which is how we ended up with the current branding. But I've started to realize that people have expectations when they hear it -- i.e. I've heard someone ask if the game was only for musicians who have perfect pitch, and that was not my intention at all!

Re: intervals -- right now in "easy" mode, we give users the first note, which gives them a start at identifying intervals. But I'm starting to wonder if maybe a given first note should be the default "normal" mode, now. And maybe "easy" mode will give more visual cues, maybe? (Just thinking out loud here.)

> melodies in a key other than C Funny story -- it took me forever to add in support for sharps and flats to the game, which is why the first ~50 songs in the database all had melodies whose first six notes had to be in C major. Luckily this is not the case anymore (we're at Day 111 now).

> If you haven't already it would be good to give Earmaster a try and see how they approach it Thank you for the recommendation! I've checked out a few other online ear training games but not Earmaster yet.

Thanks for checking out the game! "Hard" mode actually used to be only 6 tiles, but some folks complained that it was too easy, so it became 8 tiles

I think we'll definitely have to do more brainstorming to figure out the right features for each difficulty level; I think I saw some ask for an even more difficult mode.

We originally wanted to stick to the daily simplicity of wordle, but a "practice mode" is on our roadmap! (I agree, more practice would help people improve their auditory skills faster.)

Thanks for the bug find! That's one browser I didn't test against :facepalm:

Thanks, after trying on Firefox Mobile, I didn't have any luck getting audio on Chrome Mobile either. Which browsers are tested and expected to work on Android?

Chrome 119.0.6045.163 (Official Build) (64-bit) on Android 14 worked for me, but Firefox Nightly Mobile 122.0a1 didn't. I've built other apps with Tone JS that work fine in Firefox (outside of a few pops as the complexity increases) but I've not looked for error messages.

"Internet", the samsung default browser works for me. Less nice looking, but audio works.

A friend of mine recently joined a FAANG company as an engineering manager, and found themselves in the position of recruiting for engineering candidates.

We caught up.

I'm the creator of a remote-first community/open source project called CodeBuddies (a not-for-profit), and we built Jitsi into our hangouts (meetings anyone can schedule to pair program or study together) -- i.e. whenever someone schedules a hangout to meet with someone else in the community, we embed Jitsi as an iframe onto the event page.

We initially used Google Hangouts for the project in 2014, and we've been using Jitsi ever since Google Hangouts deprecated its API in 2017.

I generally love Jitsi; like Google Hangouts, it allows multiple people to screenshare simultaneously in our virtual coworking sessions. However, I have stumbled upon a couple of issues with it: - higher rates of audio or screensharing issues, especially when the participants are long distance or if one of them has a poor wifi connection, or is on an older computer. - screensharing with the browser extension sometimes doesn't work, or times out

We're actually rebuilding the CodeBuddies platform right now, and for the next iteration I am strongly considering paying for the Zoom API instead because it's more accessible to people with lower quality wifi connections and for folks on older machines.

Have you tried reporting these issues?