I was asked to install a mobile app to get access to the itinerary of a trip to Disneyland I'm taking with the kids. Fuck that noise: couldn't it have just been a Web page? An hour of reverse-engineering later, it is, and it's superior in virtually every way to the "app" that it replaces.
Atmospheric doesn’t have to be an app - Applied Meteorology
You can just build features into the websites you've already got!
Atmospheric doesn’t have to be an app - Applied Meteorology
You can just build features into the websites you've already got!
taken.
A web page that tells you what your browser gave away the moment you arrived. No login, no form, no permission. Most pages do this. None of them tell you.
at-store | Apps on the Atmosphere
Discover apps and tools across the Atmosphere. Find your next favorite app today!
CoMaps emerges as an Organic Maps fork
The open-source mobile app Organic Maps is used by millions of people on both the Android and i [...]
but should apps see our data? - building [at] habitat
thinking small on the protocol
Introduction | HappyView
HappyView is the best way to build an AppView for the atproto. Upload your lexicon schemas and get a fully functional AppView, complete with XRPC endpoints, OAuth, real-time network sync, and historical backfill, without writing a single line of server code.
Am I Building the Torment Nexus? - What happens when an AppView gets an easy window into atproto spaces.
I built a tool that lets HappyView operators browse the contents of atproto spaces, and the moment I saw it working I got a pit in my stomach. Here's what the community had to say about whether it should exist, and what it needs to look like if it does.
ATproto Apps
Browse a curated directory of ATproto apps and services—clients, feeds, tools, games, and more—with clear alternatives and links to try them.
ATproto Apps
Browse a curated directory of ATproto apps and services—clients, feeds, tools, games, and more—with clear alternatives and links to try them.
calendar pt. 1: ATProtocol beyond AppViews - building [at] habitat
our approach to permissioned data (part 1!)