Archive note: This article covers Facebook’s May 2020 Discover trial. The launch details below describe that period; they are not a promise that the service, participating networks or free-data allowance are available today.
Facebook introduced Discover as a way to keep people reading the web after their mobile-data balance ran out. Its approach combined a small, operator-provided browsing allowance with a stripped-down experience focused on text. The important distinction was between access to a wider choice of websites and access to every feature on those websites.
Where Discover launched
Facebook’s May 5, 2020 engineering announcement identified Peru as the first trial market and named Bitel, Claro, Entel and Movistar as its mobile-operator partners. The company also described plans for further trials in Thailand, the Philippines and Iraq. Those were rollout plans at the time, rather than evidence that every proposed deployment subsequently happened.
Contemporary TechCrunch reporting put the Peru trial’s free browsing allowance at 10 MB per day.
What text-based access meant
The Center for Democracy & Technology’s launch analysis described a service that removed bandwidth-heavy audio and video while delivering text-based website content. Participating carriers provided a limited amount of access outside normal data caps. This practice is called zero rating.
That arrangement could help someone fill a temporary gap before buying more data or renewing a plan. It did not provide an unlimited mobile-data plan, and a text-focused page could not reproduce the full experience of a video, audio or visually rich website.
For readers, “any website” therefore required an important qualification: broad website choice did not mean that all content types, interactive features or downloads would work as they did on a normal connection. The useful question was whether the information needed was actually present in the delivered text.
How the service worked
Facebook’s engineering account explained that Discover built on a web proxy: the intermediary fetched web pages and presented them to the user through the service’s domain. This made it easier for mobile operators to distinguish the eligible traffic.
Supporting third-party websites, including their scripts, also created security challenges. Facebook described separating trusted outer-page controls from the embedded website and adding protections against cookie manipulation, phishing and clickjacking. These were the company’s descriptions of its architecture, not a guarantee that every site or user session was risk-free.
Why it was compared with Free Basics
CDT contrasted Discover’s broader website choice with Free Basics’ approved collection of sites. The organization welcomed reduced gatekeeping over which sites people could visit, while emphasizing that a text-only connection remained less complete than ordinary internet access. Its assessment also raised accessibility questions, including how the service would accommodate people with print disabilities.
The trade-off matters when reading the original launch headlines. Removing a restricted site list addressed one concern; a limited allowance and reduced content still shaped what users could do. Discover was an experiment in extending basic access, and its launch alone did not establish how well it would work for everyone.
Reading this story today
If you are looking for connectivity assistance now, check your mobile operator’s current official offers and terms. Do not rely on this archived trial’s allowance, supported countries or old app links. A historical announcement is useful for understanding the project, but it is not a current sign-up or availability guide.
Image note: AI-generated editorial illustration of simplified mobile web browsing; not a screenshot of Discover.
