zlacker

Just don't collect any data. Having an app doesn't mean you need to collect any data.

>>apigal+(OP)
Sometimes it is not whether or not you do, but if you send the signal that you could.

By refusing to provide a (superfluous) app, not only do you spare yourself the dev (and continued maintenance) costs, you also are not even as exposed to the data protection argument.

>>apigal+(OP)
But you need to develop and maintain 2 apps. And to deal with 2 ugly companies. And even F-Droid if you were an ethically responsible business. So the GP's approach makes sense if you want to run your business in a lightway fashion.

>>usr110+R5
I know it's not exactly the same because these tools are for internal use and never see the public, but react native works well while keeping the maintainence at a minimum. I'm not in on the ops site of device control, but our IT installs the APK packages directly through the enterprise control they have, so we don't have to deal with Apple or Google. So I agree with you completely on that part, but cross platform maintainence isn't as hard as it used to be if your toolsets support it.

I did maintain the Apple account for a previous place where I worked though, and holy hell that sucks. Not so much the day to day work, but being from the Scotish part of Denmark, it hurt my soul to pay them money (it wasn't even mine) to use their platform. Not sure if Google is as shit, never tried their store from the developer side.

>>devjab+Tc
Could you elaborate on how they don't deal with the AppStore and the Play Store? I'm new to this.

>>apigal+(OP)
I don't have the time to build a native app that will constantly be out of feature parity with the web app.

I also work for a large company and we can't keep all the apps in sync even with thousands of employees. It's just dumb.