Startups
The definitive Niantic reading guide
An annotated list to everything written on Niantic to accompany our EC-1
In just a few years, Niantic has evolved from internal side project into an independent industry trailblazer. Having reached tremendous scale in such a short period of time, Niantic acts as a poignant crash course for founders and company builders. As our EC-1 deep-dive into the company shows, lessons from the team’s experience building the Niantic’s product offering remain just as fresh as painful flashbacks to the problems encountered along the way.
As we did for our Patreon EC-1, we’ve poured through every analysis we could find on Niantic and have compiled a supplemental list of resources and readings that are particularly useful for getting up to speed on the company.
Reading time for this article is about 9.5 minutes. It is part of the Extra Crunch EC-1 on Niantic. Feature illustration by Bryce Durbin / TechCrunch.
I. Background: The Story of Niantic
Google-Incubated Niantic, Maker of Ingress, Stepping Out on Its Own | August 2015 | In August of 2015, Niantic announced that it would spin out from Google and become an independent company. As discussed in WSJ’s coverage of the news, Niantic looked at the spin out as a way to accelerate growth and collaborate with the broader entertainment ecosystem.
-
Entertainment6 days ago
Teen AI companion: How to keep your child safe
-
Entertainment6 days ago
‘Wallace and Gromit: Vengeance Most Fowl’ review: A delightful romp with an anti-AI streak
-
Entertainment5 days ago
‘Dragon Age: The Veilguard’ review: BioWare made a good game again
-
Entertainment5 days ago
Polling 101: Weighting, probability panels, recall votes, and reaching people by mail
-
Entertainment4 days ago
‘Only Murders in the Building’ Season 4 ending explained: Who killed Sazz and why?
-
Entertainment4 days ago
5 Dyson Supersonic dupes worth the hype in 2024
-
Entertainment3 days ago
When will we have 2024 election results online?
-
Entertainment3 days ago
Social media drives toxic fandom. Is there a solution?