Live data from Hacker News

Apple blocked the FlickType Watch keyboard then announced a clone of it

inputmag.com

261–270 of 309 posts

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#261

Very typical of Apple, using opaque approval procedures. They're acting like bullies because they didn't get what they wanted and because they have the money/power to do so. Apple wanted to buy FlickType but they didn't agree on the price or Eleftheriou didn't want to sell (I doubt it), and so from then onwards started the downhill ride. I fully support Eleftheriou on this just for the principle, but if I were in his…

The sad thing is that I've seen numerous comments here saying (of this and other situations), "Well, Apple offered him/them some money for it. They should have just taken the money", and that, to them, completely justifies it.

"A gift he couldn't refuse", indeed.

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#262

Very typical of Apple, using opaque approval procedures. They're acting like bullies because they didn't get what they wanted and because they have the money/power to do so. Apple wanted to buy FlickType but they didn't agree on the price or Eleftheriou didn't want to sell (I doubt it), and so from then onwards started the downhill ride. I fully support Eleftheriou on this just for the principle, but if I were in his…

The original issues with the app weren't opaque at all: Keyboard utilities can't have network access. Then he noted that it can operate without it, but the entitlement can't even exist for any users, even optionally. That is very clearcut. At least without the App Store reviewers crawling all over everything you do, putting an enormous level of scrutiny over everything you do. And the functionality has to justify it…

> Keyboard utilities can't have network access

This is 100% false. Both the apple keyboard and gboard from google require network access for gif, search support etc

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#263

Meh. The problem is FlickType requires network access during use. The App store licensing is ok with keyboards, it's not ok with keyboards that get network access. This, Apple perceives as a major privacy issue-- one for the possibility of keylogging, but also for the broader possibility of the always-on logging that the weather apps are infamous for. edit: Sorry, I didn't include the source, the Developer License Ag…

>FlickType requires network access during use. The App store licensing is ok with keyboards, it's not ok with keyboards that get network access

This is 100% false. Apples own keyboard as well as gboard from google both require network access to facilitate gif, search support etc

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#264

Has no one noticed that this app in question is still on the App Store? First result on google when you search for "Apple Watch keyboards". This makes me even more suspicious of the guy creating all this outrage. It's also not very well reviewed.

He didnt claim it was removed - i believe he was blocked from updating the app

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#265
post #161

What made me leave the iPhone ecosystem, many years ago, was when they pulled all the podcatchers off the app store because they were going to be adding podcast support to iTunes soon. Not only that but getting podcasts from iTunes at the time meant plugging your iPhone into your computer running iTunes, much less convenient than having your phone download things over WiFi. Especially since I was using Linux and didn…

When was this? Based on https://www.apple.com/newsroom/2005/06/28Apple-Takes-Podcast... , it looks like Apple added podcast support to iTunes in 2005. The iPhone wasn’t released until 2007 and the App Store didn’t exist until 2008.

https://en.m.wikipedia.org/wiki/Apple_Podcasts

The actual podcasts app was released in 2012

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#266

Earlier quoted context omitted.

Software is not different from hardware. Digital parts aren't magic, bring no magic rights, it's still just boring old parts someone invested in engineering into a product. Even in digital, beige box server, IaaS, PaaS, SaaS, FaaS, applications, devices, apps, screens... different waterlines, none of them magic. Which waterline do you have the right to "run whatever you want"? Which waterline is a business ok to say,…

I don't see this as a "features" problem. I think the correct way to approach this is in terms of "control". By designing their devices that way (non-unlockable bootloaders, signature verification on every app or executable with hardcoded public keys etc) companies have essentially introduced a new paradigm in which the legal owner of the device has less control over it than its manufacturer. That is the issue here.

Yeah. What people are complaining about is cryptography to prevent them from using their thing as they wish. Nobody is demanding API documentation from Sony, people are happy to reverse engineer that. But it doesn't matter because you can't give the machine valid code and have it execute, for no good reason other than that you don't know a magic number.

The problem is that building platforms is expensive and if people can use your thing for whatever they want, that thing that they want is often not giving you money. My conclusion is that there shouldn't even be game consoles. They're just a tax on everyone that wants to play games.

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#267
post #211

This is the key problem when a market-maker is also a market participant. When the same entity setting the market rules, deciding who is violating them, and collecting the market data is also an active competitor against everyone else in that market. It's not a fair playing field. Apple knows that, but pretends that it is. I say it's a problem, but I don't have a solution. It's hard to say "Apple can't make apps for…

A legal solution might be something like: Apple cannot prevent people from installing or updating apps from sources outside of their store.

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#269
post #264

Has no one noticed that this app in question is still on the App Store? First result on google when you search for "Apple Watch keyboards". This makes me even more suspicious of the guy creating all this outrage. It's also not very well reviewed.

He didnt claim it was removed - i believe he was blocked from updating the app

The article seems to make that claim:

"A separate version for the Apple Watch would remain [in the App Store], but then Apple pulled that one as well, telling Eleftheriou that keyboards aren’t allowed on the Apple Watch."

Re: Apple blocked the FlickType Watch keyboard then announced a clone of it

#270
post #264

Earlier quoted context omitted.

He didnt claim it was removed - i believe he was blocked from updating the app

The article seems to make that claim: "A separate version for the Apple Watch would remain [in the App Store], but then Apple pulled that one as well, telling Eleftheriou that keyboards aren’t allowed on the Apple Watch."

Im not familiar with all the history nor what they mean there, but this is a better source and i think explains the story better. I havent seen the dev make that claim at least.

https://arstechnica.com/tech-policy/2021/08/iphone-keyboard-...

Post reply on HN