Exercise 3: Why Guideline 4.2 Exists, and a Real Native Feature That Satisfies It — Possible Solution
==========================================================================================================

Guideline 4.2 exists because the App Store is meant to be a real,
curated collection of genuine software applications - not a listing
of thin, native-looking wrappers around content a browser could
already display just as well. If any website could simply be packaged
into a bare native shell and submitted as an "app" with no real,
distinguishing native functionality, the App Store's own core value to
users - a promise of real, purpose-built software - would be
genuinely hollowed out, since there would be nothing meaningfully
different between installing the "app" and simply visiting the same
website in Safari.

A simple content-browsing app - say, one that just displays a list of
articles or products pulled from a web feed - risks failing exactly
this test if it does nothing a mobile website couldn't already do
equally well. A real, concrete feature that would help it pass is
genuine offline access: caching the browsed content locally (directly
using SwiftData, this course's own real Architecture & Data Chapter 4
material) so a user can keep reading already-viewed articles or
browsing already-loaded products with no real internet connection at
all - something a plain website, dependent on a live network
connection for every page load, cannot genuinely offer.

Real push notifications for new content (Architecture & Data Chapter
8's own material) would be another concrete, genuinely native
capability serving the same purpose - alerting a user the moment new
content arrives, without requiring them to have the website open at
all, which is something no browser tab left in the background can
reliably do on its own.

ANSWER: Guideline 4.2 exists to keep the App Store meaningfully
different from a directory of websites, protecting its own real value
to users as a source of genuine, purpose-built software. A concrete
feature that would help a simple content-browsing app pass it is real
offline access via local SwiftData caching, letting the app do
something a plain website genuinely cannot: keep working with no live
internet connection.

WHY THIS WORKS AS AN ANSWER
------------------------------
This explains the real underlying reason the guideline exists (the
App Store's own distinct value proposition) rather than just restating
the rule, and names a specific, real, already-covered technical
feature (SwiftData offline caching) that would genuinely satisfy it.