I recently decided to take privacy more seriously and one of the experiments I am trying is using web versions of apps instead of their native mobile counterparts. The tracking practices of big tech have become increasingly aggressive, and web versions with AdGuard provide a much better privacy experience.

Why app tracking is getting worse

Native mobile apps have access to more data than web versions, though modern operating systems have significantly restricted this access. Here’s what they can still track that web apps cannot:

• Advertising identifiers: Google’s Advertising ID (Android) and Apple’s IDFA (iOS) - resettable but still used for tracking
• Location data: GPS, WiFi networks, Bluetooth devices
• App usage patterns: How long you use each app, when you open them
• System information: Device model, OS version, battery level
• Network data: WiFi networks, cellular carrier information
• Biometric data: Fingerprint, face recognition usage patterns

Modern protections exist but aren’t perfect. iOS App Tracking Transparency (ATT) requires explicit permission for cross-app tracking, and Android has similar restrictions. However, apps can still collect significant data within their own ecosystem.

Web apps are limited to what the browser allows. While they can still track you, the scope is much more limited and easier to control with privacy tools.

The solution: Web versions with AdGuard

I use Safari with AdGuard for iOS to access web versions of apps. This combination provides several advantages:

• Better ad blocking: AdGuard blocks most ads and trackers in web versions
• Reduced tracking: Web apps can’t access device-specific data
• Easier privacy control: Browser settings and extensions provide more control
• No app store dependency: No need to install potentially tracking-heavy apps
• Cross-platform consistency: Same experience across devices

The key insight: Web versions with proper privacy tools often provide a better user experience than native apps, especially for content consumption.

Real examples: What works and what doesn’t

LinkedIn: Mixed results

LinkedIn’s web version is functional but has limitations. The web interface works well for basic browsing and messaging, but AdGuard doesn’t block promoted posts as effectively as it does on other platforms. The “Download our app” prompts are frequent but manageable.

What works:

• Basic profile browsing
• Messaging
• Post reading
• Job searching

What’s annoying:

• Frequent app download prompts
• Some features require the app
• Promoted posts still get through

Instagram: Surprisingly good

Instagram’s web version is actually quite good. AdGuard blocks most promoted posts and ads effectively, and the interface is clean and functional.

What works:

• Photo and video viewing
• Stories (with some limitations)
• Basic interaction (likes, comments)
• Direct messaging
• Explore page
• Reels (now fully supported in web version)

What’s missing:

• Some advanced features
• Default push notifications (web push requires explicit permission)

Reddit: Excellent web experience

Reddit’s web version is probably the best example. The interface is clean, AdGuard blocks promoted content effectively, and the experience is often better than the mobile app.

What works:

• All basic Reddit functionality
• Good ad blocking
• Clean interface
• Easy navigation

What’s missing:

• Some advanced mobile-specific features
• Default push notifications (web push requires explicit permission)

Loyalty programs: Screenshot approach

For loyalty programs, I use screenshots of QR codes and barcodes. This eliminates the need for tracking-heavy apps entirely.

Current approach:

• Screenshot QR codes and barcodes
• Store in Photos app
• Use when needed
• No app installation required

Future plans:

• Investigate custom Apple Wallet cards
• This would provide even better convenience

AdGuard effectiveness

AdGuard works well for most web versions, but effectiveness varies by platform.

What AdGuard blocks effectively:

• Most display ads
• Promoted posts on Instagram and Reddit
• Tracking scripts
• Pop-up ads
• Social media tracking pixels

What AdGuard struggles with:

• LinkedIn promoted posts (platform-specific issue)
• Some in-app purchase prompts
• Native app download prompts (these are legitimate site features)

The key benefit: Even when AdGuard doesn’t block everything, the tracking scope is still much more limited than native apps.

Limitations and annoyances

Web versions do have some drawbacks:

App download prompts

Most web apps constantly prompt you to download the native app. This is annoying but manageable. The prompts are usually dismissible, and after a few visits, they often become less frequent.

Feature limitations

Some features require the native app. Examples include:

• Advanced LinkedIn features
• Real-time notifications
• Some camera and media features

Performance differences

Web versions can be slower than native apps. This is especially noticeable on older devices or slower connections.

Offline functionality

Web versions require internet connectivity. Native apps often have offline capabilities that web versions lack.

The privacy trade-offs

Using web versions involves some trade-offs:

What you gain:

• Reduced tracking: No device-specific data collection
• Better ad blocking: More effective with privacy tools
• Easier privacy control: Browser settings and extensions
• No app permissions: No need to grant location, camera, contacts access
• Cross-platform consistency: Same experience everywhere
• Control over notifications: Opt-in push notifications instead of default interruptions

What you lose:

• Some features: Advanced functionality may require native apps
• Performance: Web versions can be slower
• Offline access: Limited offline functionality

The results

After switching to web versions:

• Reduced tracking: No more device-specific data collection from these apps
• Better ad experience: AdGuard blocks most unwanted content
• Simplified device management: Fewer apps to maintain and update
• Improved privacy: More control over what data is shared
• Reduced random scrolling: An added benefit is that I find myself scrolling less if the apps are not there.

The approach isn’t perfect, but it provides significant privacy benefits with manageable trade-offs. For apps I use frequently, the web versions work well enough that I don’t miss the native apps.

What’s next

I’m continuing to explore this approach for other apps:

• Testing more web versions: Trying web versions of other apps I use
• Apple Wallet integration: Investigating custom loyalty cards
• Browser optimization: Fine-tuning Safari settings for better privacy
• Alternative approaches: Looking for other ways to reduce app dependency

The key insight: Native apps have become increasingly aggressive with tracking, while web versions with proper privacy tools often provide a better, more private experience. The trade-offs are worth it for the privacy benefits.

The web-first approach has become my default for new services. If a web version exists and works well, I’ll use it instead of the native app. The privacy benefits are real, and the user experience is often surprisingly good.