this post was submitted on 22 Jul 2023
36 points (100.0% liked)
Technology
37573 readers
630 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What benefit would this even serve over just using your mobile browser or a WebView wrapper?
Its an additional option for those who prefer a native app. Do you have an issue with it?
I don't necessarily take issue with the app just for being an app, and it hasn't come out yet so not like taking issue with it now would be particularly meaningful. If it ends up being worse than the website that'd suck. If they end up making decisions that make the website worse to drive more people to the app, that'd suck too. Though these aren't things I necessarily think will happen, but I've definitely seen it happen way more often than I'd like with websites that go on to create apps. I do think that thinking it's just "an additional option" is a bit naïve since development resources would go into maintaining it and so naturally there would be an incentive for it to justify that. I just don't know what form that is, it could just be as benign as "more people will use it if there's an app."
You can collect far more data with an app than with a website because of device permissions APIs. You can then sell that data to advertisers and also use it to train your models.