Mobile apps are the worst offenders in this area. So little native compatibility with password managers and when you do it through the keyboard it doesn't always work.

I remember reading that Amazon chose "Alexa" as their wake-up word because it tested well in different activation tests and they already owned trademarks for the word.

On the other hand, Google went with a brand focused wake-up word that doesn't work that well for this type of interaction.

Of course, because of this, many TV shows activate Google Assistant when somebody says "Ok, {{word that vaguely resembles the phonetics of the word "google"}}"

How did they manage to oversee this issue?

True. But I also get the sense that they did this because the "more" tab feels like a bucket for "what's left and didn't fit anywhere else" and not a primary navigation mechanism. I think the goal here is to have the same functionality as the hamburger menu while keeping all the navigation contained in the bottom area.

Why?

Nice Article! And Craft is amazing!! Love it everyday more.

The introduction of downvotes was the single most stupid decision in the history of stupid decisions. Just wait and see how this comment gets downvoted.

Every decision is being critiqued by the PM before it's even a flushed out idea to the point of frustration.

That sounds like a very bad reason to quit and be frustrated. Designers have to be good at dealling with push back, evangelizing their ideas and convincing stakeholders.

I was excited to try it, but the App Store reviews don't look too good.

Hey Pete. I saw this last week, but I didn't even bother to explore it when I saw there was no documentation. The features are also pretty vague.

I have been looking for something like this, but it's pretty hard to evaluate your product from the existing landing page. For example, right away I wanted to know if this has webhooks for subscription and cancellation events, but there's nothing in the landing page mentioning that.

Another reason why I'm looking for a product like this is that I don't want to mess with setting up a backend to handle payment changes, cancellations, payment method changes, etc. It's not clear if you provide these either. Otherwise, this is pretty similar to Stripe Checkout (not necessarily a bad thing). It would be nice to understand how is different.

I don't know if the vagueness is intentional or not, but I would consider making things more clear, as well as providing links to documentation.

I have an API product and currently using Chargebee, but I would love something simpler. Maybe I'm not the right audience for this product but I thought I would share these thoughts.

This is weird.