Augmented

Forwarding server and hosted agent architecture for T2V and agent-to-agent use-cases for x402.

[Augmented @augmentday]

Augmenting

[Augmented @augmentday]

Don’t buy scam tokens our official token is NOT LIVE YET!

Stay safe and join our community all real updates will drop there first.

[Augmented @augmentday]

After all the restless nights and endless improvements.
We are ready.

[Augmented @augmentday]

We reached an important milestone today 300 people want to augment their lives.
This is the time we go live and start rewarding our community
Expect us soon.

[Augmented @augmentday]

gm🌞
coffee. code. crypto. health.
stay sharp, stay AUGMENTED 💻🧠💪

[Augmented @augmentday]

“Too messy” was more about our specific needs and the dev experience at the time TinyBase is clearly powerful, but for our use case:

We were looking for something that felt more like a traditional ORM

Schema/query support was a priority (vs. key-value w/ listeners)

It felt like we’d need to write a lot of glue code to get everything working together

[Augmented @augmentday]

we used react native (via Expo) 👀
requirements:
- local offline first DB µ
- use existing ORMs / tooling
- sync db data between client devices
- backup db to cloud
- user opt-in

[Augmented @augmentday]

Just wrapped up the first draft of the rewarding system for @augmentday !
Users can now earn tokens for hitting streaks, staying focused, and maintaining great vitals

[Augmented @augmentday]

🎉 We're moving! The Augment waitlist is filling up fast someone just snagged spot #134 👀

👉 https://t.co/X3iFqojSZW
#SQLite #OfflineFirst #TanStackDB #Expo

[Augmented @augmentday]

Am Really excited about the TanStack DB roadmap syncing to SQLite and querying directly sounds like the kind of native persistence Expo apps really need. Will definitely be watching that closely.

In the meantime, love the workaround idea with syncing PG → SQLite → TanStack Collections. The starter looks super helpful

[Colosseum @colosseum]

Big week in the arena. Stay tuned.

[Augmented @augmentday]

Yeah, we’re not using Supabase. The main thing that felt like too much effort was building and hosting our own backend API just to handle syncing logic especially when we currently have zero users relying on it. It didn’t feel worth the time investment yet.
We’re using React Native (via Expo), and our goals were pretty specific: offline-first local DB, existing tooling/ORM support, optional sync across devices, and cloud backup. We checked out PowerSync and Replicache, but they both required more setup than we could justify for now.
So we’re keeping it simple: local-only SQLite with Drizzle ORM, and we’ll let the client occasionally pull fresh data via API — syncing and backup can come later when needed.

[Augmented @augmentday]

Today is @augmentday

We're building the world's most advanced system for your personal longevity and vitality.

A New Open Source Health Ecosystem
focused on accelerating longevity and vitality, while protecting your data and privacy.

https://t.co/6gkULAFw6M
We are open for contributions on github repository
https://t.co/ISu5HgEMVh

[Augmented @augmentday]

for more info about this check our github:
https://t.co/huZe2Xbvew

[Augmented @augmentday]

other paths: - build out custom syncing logic with
@powersync_ or @replicache : too much effort for 0 users

[Augmented @augmentday]

felt better - like entering the matrix 💊
or getting an implant in cyberpunk 2077 📷
and we've been cooking 📷 👀