> Meta relied heavily on selling personalized advertising, which required it to be able to target particular demographics and interest groups. This was achieved by tracking individual users across different apps.

Yet another reason to dump native apps (many of which are built using the Facebook SDK despite having nothing to do with FB) in favour of web apps.

▲

ujkhsjkdhf234 a day ago | parent [-]

I like my native apps and I'm not a fan of PWAs because they cannot be made to easily run offline.

▲

rchaud a day ago | parent | next [-]

What third party app are you running offline? By third party I mean something not built into the OS like a notes app, file manager or camera app.

▲

ujkhsjkdhf234 a day ago | parent [-]

Fitness and calorie tracker, ebook reader, notes app (Android doesn't have a good notes app built into the OS), music player app for music I have locally on my phone, and an app that configures my bluetooth headphones.

	▲	NoiseBert69 a day ago \| parent [-]
		Gadgetbridge is running great locally without dumping your most intimate data into a vendor cloud.

▲

nickthegreek a day ago | parent | prev [-]

running meta's social media apps offline doesn't seem particular compelling.

	▲	ujkhsjkdhf234 a day ago \| parent [-]
		I can't tell if you are deliberately being obtuse but they are talking about apps overall and not Meta's apps. Many apps use Facebooks SDK because of the Facebook Pixel for tracking and advertisement. Web apps don't prevent that and again, cannot be easily run offline so I'll stick with my native apps.