# Antigravity TagSpotter - Share data with Firebase

DevFeed: [Antigravity TagSpotter - Share data with Firebase](<https://devfeed.tech/articles/antigravity-tagspotter-share-data-with-firebase-32039.md>)

Original publisher: [Read original article](<https://www.maiatoday.net/p/antigravity-tagspotter-share-data-with-firebase/>)

Published: 2026-07-09T20:34:04Z

Content type: tutorial

Language: en

Sources: [maiatoday](<https://devfeed.tech/sources/maiatoday.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [Google](<https://devfeed.tech/topics/google.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [data](<https://devfeed.tech/topics/data.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [antigravity](<https://devfeed.tech/tags/antigravity.md>), [code](<https://devfeed.tech/tags/code.md>), [data](<https://devfeed.tech/tags/data.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [google](<https://devfeed.tech/tags/google.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

## AI overview

The article describes planning and implementing Firebase-based cloud storage for TagSpotter, including authentication, offline use, cross-device syncing, shared data packs, schema changes, migrations, and platform SDK constraints. It finds that defining requirements and edge cases required substantial planning before implementation.

## Source excerpt

The challenge - Firebase with Google Plugins Now that I can see my graffiti spots on multiple platforms the obvious next step is I want to keep the data in the cloud so that I can capture spots when I'm out and about and then look at them and edit them on the laptop later. For this I need some kind of auth and data storage - like Firebase. Like before, can I do the implementation on a weekend. Easy enough? Well Antigravity 2.0 has firebase super powers in the form of Google shipped plugins but figuring out what I really want and what the edge cases are was not trivial. The prep grill-me grill-me grill-me For this exercise I was pretty confident antigravity could code up my solution. Just look at all these built in firebase skills. What I wasn't sure of was what I actually wanted. Let's get some ideas. I wanted users that didn't want to log in, not to be forced to do this. So there was the idea of an offline mode. Then when I do log in and I happen to change something on my phone and then on the desktop it should take the latest edit. I wanted it to update in the background but realistically only when I finish editing a spot. What happens when I delete a spot? How will it work when I import a pack? What happens when the photographer name is the same but the email differs? Can I have a way to save a pack of spots and just share a code to see it? What then, will I be able to change them? How does the db schema change? What migrations are needed? Will the old share packs work? How do I even set things up properly on firebase? What about desktop, there isn't an SDK for desktop? And so on and so on. I was clearly better at asking questions than building especially since I didn't know how to integrate the SDK on iOS. I spent about two evenings planning and changing my mind to come up with this plan It required multiple rounds of /grill-me and also asking antigravity for some suggestions on how things could work and picking the options I liked best. The plan had important s