simonhamp

it was supposed to be public. maybe it got reverted. the team were moving super fast

Awesome story! Thanks for sharing. I will now go and have a listen

You need to check out what we've been building with SuperNative - it's one codebase, but you end up with two truly native apps.

But if you could get slick native mobile apps with less code (i.e. higher quality abstractions), that would be better

Yep. It's a full copy of the state of the origin

Just use copy-on-write clones. They're way more flexible, faster and easier to reason about.

I don't get spending all this time on tooling that tries to ease working with worktrees when they're just not the right abstraction for the way we're working now.

You don't have to ditch cross-platform building entirely just to escape dependency hell

Agree to a point, but human resource is literally the main cost in most businesses, so there's that

Conway's law also plays a big part here and it's kind of TBD to see if agentic development will minify or magnify its effects

100% with you. I'm fed up of having my M3 36GB run out of memory because I have Chrome, Slack, Discord and Claude all open at the same time

That's why I'm building SuperNative

I hate to break it to you, but we already have it: it's called PHP

Seems like you've never had to worry about accessibility in hybrid apps...

Hallelujah!

One other person in this place gets it: "fewer tokens, faster progress"

Electron, Tauri, React Native/Expo, Flutter (and countless others) are the wrong kind of abstractions, built for a time pre-AI, solving pre-AI problems

We need a new post-AI abstraction that embraces this opportunity!

That's why we're building SuperNative