3 ms·
I paid for and use FlickType on the watch. It’s clever, but it always sucked it was a stand-alone app. It was a very limited and cumbersome workaround for an ob
by skygazer 5y ago
I paid for and use FlickType on the watch. It’s clever, but it always sucked it was a stand-alone app. It was a very limited and cumbersome workaround for an obviously missing OS feature. Copy and paste isn’t even a thing on the watch, so text was mostly trapped in the app. Everyone that used the app knew it would vastly better if a keyboard were supported natively by Apple across the whole OS. It was mostly a tantalizing proof of concept. I feel sorry for the Sherlocked developer, but this is a huge improvement.
I recall Apple had previously said they tested and abandoned an on-screen watch keyboard for the Series 0, as the screen was too small. And yesterday they said the screen was finally large enough for a keyboard. I think Flicktype proved it was viable on a smaller screen, and Apple is being crappy limiting availability to the new watch.
I don’t know if Apple legally or morally owes the developer anything. I doubt it, but I’m all for them sorting it out in court.
- skygazer 5y agoIt seems the letter from Apple that the dev posted on Twitter (which was cropped, excluding the date) was actually from 2019 and not sent recently -- it was his initial rejection before the app was finally approved. A bit misleading, whether intentional or not -- if it was intentional, it cleverly fanned the flames. Props to the dev for gorilla marketing skill. https://appleinsider.com/articles/21/09/15/apple-refutes-flicktype-developers-account-of-app-store-issues https://appleinsider.com/articles/21/09/15/apple-refutes-fli...