Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple rejected my dictation app for using the accessibility API

mitmllc.com

Post reply on HN
Print view View original

141–150 of 200 posts

Re: Apple rejected my dictation app for using the accessibility API

#141

Post by RZelaya »

longnguyen wrote: post #140

If you emulate command+V, make sure to check the keyboard layout. You may need to translate the keycode V for the current keyboard layout like DVORAK etc

Good catch. Easy edge case to miss if you only test on QWERTY. I'll double-check the implementation, thanks for the heads up.

update: You're right, this is a real bug. The Direct version's auto-paste hardcodes the QWERTY keycode for V instead of translating for the active layout, so Dvorak / Colemak / AZERTY users would all hit it. The MAS version is unaffected (clipboard-only; the user presses their own Cmd+V, which is layout-correct). Fix is going into the next release. Thanks for the careful read.

Re: Apple rejected my dictation app for using the accessibility API

#142

Post by exitb »

marvin-hansen wrote: post #118

I actually had the almost same situation by building an offline voice dictation app for macOS and iOS, and in macOS I was confronted with the exact same situation. However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and…

Isn’t that just deliberate on their part? As in, they genuinely don’t want developers to use these APIs and just allow them for accessibility use cases.

Re: Apple rejected my dictation app for using the accessibility API

#143

Post by gumby271 »

cmsj wrote: post #91
robgough wrote: post #38

I recently built a similar app, and so hit the same limitations – I wasn't too upset on Mac, happy to distribute without the App Store (though it's a shame). Where I was more frustrated was how much this limited the potential usability of the iPhone app. Because of app store restrictions it is a far worse app ... though like in your example, still useful to a degree. I can only hope they use the new CEO as an opportu…

I really do understand the desires people have for iOS to be a more open platform, but I'm just gonna say very clearly: I do not want third party apps being able to do what OP's app does. My iPhone is the one computing platform I have where I get the assurance that no third party app can be spying on anything else I do on the device.

Two things can be true, you can choose to install software from a curated store, policed by an entity you trust to do that. I can install whatever trash I want from the internet and risk my own security doing so. These two things aren't in conflict and could be enabled with a change in policy from Apple.

Worried about grandma installing shady apps? Enable parental controls on her phone.

Re: Apple rejected my dictation app for using the accessibility API

#144

Post by Wowfunhappy »

marvin-hansen wrote: post #118

I actually had the almost same situation by building an offline voice dictation app for macOS and iOS, and in macOS I was confronted with the exact same situation. However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and…

> However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and and move the cursor...

I want apps to be able to do that!

Re: Apple rejected my dictation app for using the accessibility API

#145

Post by longnguyen »

RZelaya wrote: post #141
longnguyen wrote: post #140

If you emulate command+V, make sure to check the keyboard layout. You may need to translate the keycode V for the current keyboard layout like DVORAK etc

Good catch. Easy edge case to miss if you only test on QWERTY. I'll double-check the implementation, thanks for the heads up. update: You're right, this is a real bug. The Direct version's auto-paste hardcodes the QWERTY keycode for V instead of translating for the active layout, so Dvorak / Colemak / AZERTY users would all hit it. The MAS version is unaffected (clipboard-only; the user presses their own Cmd+V, which…

Good luck. I’ve been building a native AI client[0] for the past 3 years and I didn’t catch this edge case until some of my users asked for it.

[0]: https://boltai.com

Re: Apple rejected my dictation app for using the accessibility API

#146

Post by gumby271 »

Gormo wrote: post #123
dmcgill50 wrote: post #27

In Apple’s defense, your company name is MITM. Man In The Middle certainly falls on one side of the perception line, don’t you think?

Of course, one might construe Apple as an MITM in the relationship between the user an and the software vendor.

In fact, Apple would construe themselves as a MITM, pretty explicitly.

Re: Apple rejected my dictation app for using the accessibility API

#147

Post by julianlam »

atroon wrote: post #111

I don't mean to offend, but entrusting every input to a company literally called MITM LLC has a level of absurdity that either greatly entertains or else greatly frightens me.

Model-in-the-middle LLC

Checks out, what's the problem? /s

Re: Apple rejected my dictation app for using the accessibility API

#148

Post by phainopepla2 »

Wowfunhappy wrote: post #144
marvin-hansen wrote: post #118

I actually had the almost same situation by building an offline voice dictation app for macOS and iOS, and in macOS I was confronted with the exact same situation. However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and…

> However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and and move the cursor... I want apps to be able to do that!

Then they should use an appropriately scoped API, as OP suggested.

Re: Apple rejected my dictation app for using the accessibility API

#149

Post by ChrisClark »

chris_wot wrote: post #105
squigz wrote: post #102

Earlier quoted context omitted.

This comment is a little light on the reasoning for why you were permabanned.

I commented on BrownHairedGirl’s RFA. The most toxic user ever on Wikipedia. I can assure you, there are those on Wikipedia who committed far worse offenses and they remain. Like I say - a cesspool that doesn’t respect article writers.

Ah, I see, you were instigating constantly and people were sick of your shit. Seems like a reasonable ban, especially when you violated an IBAN already.

Re: Apple rejected my dictation app for using the accessibility API

#150

Post by [deleted] »

phainopepla2 wrote: post #148
Wowfunhappy wrote: post #144

Earlier quoted context omitted.

> However, I would like to point out that Apple isn't totally wrong here because the accessibility API unfortunately is way too broadly scoped, and because of that you literally get access to everything on the computer like you you can screenshot listen and and move the cursor... I want apps to be able to do that!

Then they should use an appropriately scoped API, as OP suggested.

[deleted]
Post reply on HN