Good to see this on HN, I’d love to share my journey with Takeout!

I first encountered Takeout about a year ago while experimenting with cross-platform development after reading this blog post: The Different Tech Strategies for Building a Cross-Platform App (https://magnemg.eu/the-different-tech-strategies-for-buildin...)

At work, we urgently needed an iOS app to enable push notifications for our logistics app, but our frontend was web-only and built with React/Next.js. Since the codebase was already several years old with many screens, we decided to port it to Capacitor, which led us to adopt a stack with Next.js and Capacitor (https://github.com/RobSchilderr/nextjs-native-starter).

However, once we began working with Capacitor, we ran into numerous issues. Dealing with the iOS keyboard and Safari WebView was almost impossible with famous scrolling issues, and Android’s Chrome WebView also suffered from poor performance (https://github.com/ionic-team/capacitor/discussions/3899).

This experience pushed me to switch to Expo with Solito and Tamagui, and the new stack has been a game changer. The support from Nate and the Tamagui team has been outstanding. Also Expo and EAS has been working flawlessly.

Now, with One, cross platform development is entering a new phase which address the final challenges of cross-platform development. Sharing code with Expo and Tamagui used to be manageable only for those familiar with cross-platform solutions, but now it’s becoming accessible to everyone. I bet it will be easier for new folks to understand how to work with Expo and Tamagui.

Combine that with local-first, and small teams will be able to build high-performance applications across three platforms using just one simple codebase quickly.

Context:

Tamagui Takeout is a paid fullstack starter kit based on Tamagui (and Drizzle): https://tamagui.dev/takeout

They’ve started a rewrite of Takeout to One (Zero instead of Drizzle, etc.), and are grandfathering in all existing users (also those who start using it before the rewrite is released). More in thread:

https://x.com/tamagui_js/status/1841985327139098649

PS: I’m happy you found use of my blog post about the various tech strategies/choices when making a cross-platform app. :)

That blog post was spot on in 2022! Cheers for that. Time for a re-write in 2025!

And thanks for adding the context on Takeout.

I get "programmers are also human" vibes reading this. It is so uncanny.

more context: https://www.youtube.com/watch?v=aWfYxg-Ypm4

Was this written by AI? It sounds very uncanny valley like. Or otherwise, is it a paid marketing post?

We're gonna need a new entry in HN guidelines about AI sniffing

The sheer number of Tech Nouns in this post is dazzling. What have we done.

Agree to this. Aan Apple fan acquaintance of mine recently said he might put away his phone because he could achieve everything with his watch and earpods and wanted to increase his concentration. He said he'd do his WhatsApp with voice messages and also call like that. He was fine with no display.

Why not look into an open source auth solution such as supertokens? It's almost free and you can self-host. That way you implement your own auth system but the security issues are mostly dealt by them.

Have you tried it with capacitor?

Yes, less useful. For example, apparently theres no capacitor plugin to create a "foreground service" in android. A search on Ionic's page takes you to the Cordova plugin.

Once in a while the Flutter/RN discussion shows up on Hackernews and I'd like to remind you all that Capacitor community is also alive and kicking.

For the past months I've been building an E-commerce with Capacitor/NextJS and its been quite a pleasant experience. If you're familiar with JS/TS and React, it's a great option for an e-commerce or a b2b SAAS app.

If you don't need many native components or a super slick performance, Capacitor might be the cheapest and quickest solution for web developers.

We are building our native app off from our web app, using Capacitor. One single codebase, 3 platforms targeted. Using very well established technologies that have a very good DX.

Great to hear you're having a similar experience. It became extremely easy for web devs to release mobile apps now.

I did native app development on-off from about 2010-2018, with at larger apps. Today I see little reason to have 3 code bases with the same features. You got 3x the same problems. Ok, there's Flutter and React Native, but their web code transpilation isn't great. Web Views (both in browsers and in apps) are just a super major technology with excellent developer tooling such as live reloading. Capacitor would always be my first choice today.

Very nice! Will use it for sure. May I ask you how you created that good looking demo gif?

I used:

- ScreenToGif to record video sequences and produce the final GIF: https://www.screentogif.com/

- Macro Recorder to record and replay user navigation: https://www.macrorecorder.com/

- Blender to edit the video, add text comments, and make the intro: https://www.blender.org/

Thank you for sharing!

Capacitor for sure. Check the top comment, it depends on your needs.

Agree! I have been building a React/Next capacitor application for a Dutch e-commerce with a colleague.

Up until now everything is fine for our purposes and performance is near native. Usually similar e-commerce apps require multiple teams, or at least 5+ employees, to release an app on web, Android and iOS. Due to the fact that we have just one single codebase, we can still manage it with the 2 of us.

I also recommend the Capacitor community on Discord in case you need help getting started.

I developed my own website to show the climate consequences per country: https://howhotwillitget.com

And try to educate those around me bit by bit.

If you are looking for an overview of future climate scenarios of each country worldwide: https://www.howhotwillitget.com. The coming months I am going to update the website with the new data and fix some running issues. Follow my Twitter if you want to stay updated.