George J

Some fresh new features in @titangymapp.bsky.social:
1. Full-year workout consistency heatmap
2. Workout volume by muscle groups

#BuildInPublic

New feature for power users on @titangymapp.bsky.social: explore your workout data using SQL

#BuildInPublic

New feature in @titangymapp.bsky.social: Calendar view for past workouts

#BuildInPublic

Building a quick admin-only local sqlite debug tool in @titangymapp.bsky.social got me thinking - what if this were also exposed to power users who want to build custom visualizations right within the app? 🤔

#BuildInPublic

New in @titangymapp.bsky.social: Supersets

#BuildInPublic

@titangymapp.bsky.social now also supports iPadOS and macOS

🤮

✨ New feature: A plate calculator that factors in what plates and bar you have at your gym

#buildinpublic

@titangymapp.bsky.social just hit $1,000 in revenue

It ain't much, but nice to see paying users on a product that offers most features for free!

#buildinpublic

‪You get a streak when you hit your “number of workouts” goal for the week. This can be a different number in different weeks. ‬

New in @titangymapp.bsky.social: A minimal streaks UI that stays out of your way, and plugs into the heatmap view!

A screenshot of https://georgejose.com showing a single blog post, and a graph view of related posts

A screenshot showing a graph view of related blog posts

Shout out to the Webpage HTML Export plugin on @obsidian.md for making it so easy to publish content

My personal website now uses this setup. What I find cool is how it generates a graph view of interlinked content.

github.com/KosmosisDire...

georgejose.com

I think it’s just an upside down photo

Just discovered the Book Search plugin on Obsidian that lets you have a completely local Goodreads like experience

I'm constantly blown away by what's possible on @obsidian.md

First personal workout in a while!

I'm personally noticing a massive performance boost with OPFS!

🚀 @titangymapp.bsky.social update:

You can now view your workout stats on a bigger screen, if that's your thing!

#BuildInPublic

And building with a sync engine like @powersync.com means I get instant reactivity for free (across platforms), without having to write repetitive boilerplate code to manage websockets and API endpoints

#buildinpublic @titangymapp.bsky.social

One of many nice things about building with #ReactNative is you can share code, not just between iOS and Android, but also with web.

Your web components can even contain a mix of react & react native code, including libraries like @tailwindcss.com.

#BuildInPublic

@titangymapp.bsky.social

Now's a good time to say, @titangymapp.bsky.social is 100% Canadian owned and operated 🇨🇦

#BuildInPublic

@bsky.app please improve your opengraph tags powering the link preview experience in many apps!

Here's a side by side comparison of link previews of basically the same post on X vs Bluesky, as seen on whatsapp.

Links to the posts:
x.com/swmansion/st...
bsky.app/profile/swma...

New in @titangymapp.bsky.social: Inline rest timers in workouts, workout programs and templates.

Smooth, continuous timer animation courtesy of React Native Reanimated.

#BuildInPublic

My hobby app @titangymapp.bsky.social just got a fresh new look 🎨!

Go check it out at www.titangymapp.com

I don't think we can afford to not take this seriously. The Orange Man is likely not just joking around here.

It was quite the refactor to move almost the entire app to this model over the holidays, but excited to see how it goes once I start an incremental roll-out!

(Moving small parts of the app to this model worked well before I decided to go all in)

Really loving how I'm able to make pretty much any flow instant without having to micromanage client code to call server endpoints, timing API calls right, server code to handle calls etc.

Using @powersync.com

I'm excited to see how this goes.

It's definitely an exciting time for local-first apps with platforms like @powersync.com, InstantDB, Triplit, @livestore.dev, @electric-sql.com etc

And perhaps the biggest concern of them all - sever load. With this approach my server gets a lot of (small) requests, one per database transaction. This is in contrast to how you'd usually model an API, where you'd have nested entities and fewer sever calls.

I also found that it didn't quite solve state management for me (but it did solve data management and syncing). SQLite queries are pretty fast, but doing a lot of them in parallel is much slower than in-memory lookups. I wrote a lightweight in-memory layer to solve for this.

It isn't possible to granularly watch specific rows for changes, you can only watch entire tables. This means it's harder to avoid unnecessary rerenders with react / react native.