[watchblob]

Overall, I like the idea a lot: it's Anki specifically for building your vocabulary. That said, I struggled a lot with the UX.

I think you need to make it more obvious that this is a preview and today you can only use words starting with S.

Changing the initial text in the search to 'Try searching for a word beginning with S...' would go a long way.

I'd also explain the product to people a bit more when on the landing page (without the copy above I would have been baffled) rather than launching them straight into it.

The login / sign up experience is a bit confusing. UX wise the view conflates sign up / login with information about the browser extensions. In my view, it's also a bit early to force people to use passkeys as the only way to login. Regardless, the whole button should be clickable rather than just the key.

The flying text is quite distracting.

On desktop, it's really not obvious that there is a button at the bottom right which has a lot of settings.

I also think there are very few people who would commit to spending $15.64 a month (1564 is Shakespeare's birthdate - nice) without some sort of free trial or at least having more of a go at using the app with more words than just daily one.

Sorry if that's harsh but that's my honest view. As I said, I like the idea overall. There is very little chance I'd spend $15.64 on this as it stands or if ever though.

[the_florist]

Thanks for the constructive criticism! There’s definitely room for improvement.

The design was intended to be minimalistic, but perhaps overly so. The preview could indeed be clarified: The letter corresponds to the day of the month, so the A headwords are unlocked on the 1st. Today’s the 19th, hence S.

The cards in the login/signup sheet are notifications, but I agree that the (non-dismissible) signup notification should be clickable. It’s not obvious that the padlock and key icons are buttons. As for passkeys, I do think they are ready for prime time, but password-less login will require user-friendly onboarding. The terse explanation on the Help page doesn’t cut it.

The five words sliding across the home page are currently hard-coded, but will soon cycle every weekday. You can turn off this upcoming “word-a-day” feature at https://flowery.app/settings.

I’m delighted that someone caught the Shakespeare reference! The product’s value should converge to its price as it evolves.

[watchblob]

Nice! Good luck anyway and congrats getting this out of the door. I know how difficult it can be to get to this stage. With some UX refinement then I think you'll have a nice proposition. As you said, pricing can evolve.

[watchblob]

I've just tried it on mobile. What's the reason for building a custom keyboard?

[the_florist]

I decided to roll my own virtual keyboard after a protracted battle with inconsistencies and quirks across mobile browsers. The glaring difference is that the native keyboard slides the viewport upward on iOS (pushing the fixed header off screen), whereas it shrinks it on Android (causing relayout that repositions any UI element fixed to the bottom).

Also, notice how the search box is anchored to (and animates with) the virtual keyboard. This effect cannot even be achieved with the experimental VirtualKeyboard API, which is not supported by WebKit anyway.