Zero to $10 Million with React Native + Next.js - Fernando Rojo - (Next.js Conf 2021) on HackerTube: recommended by 2 Hacker News commenters across 2 separate months, 2022.
talk · intermediate · dated
Fernando Rojo explains how BeatGig reached $10M in sales with one frontend engineer by sharing code between React Native and Next.js, covering navigation, animation, theming and performance.
Linked as the origin story and rationale for Solito and for sharing code between web and mobile.
“His video at Next.js Conf was really informative”
6 Hacker News comments link this video. Each one links back to its thread.
It's mainly cross platform components (Fernando refers to them as screens) that can be used on the web, iOS, and Android. In Next.js, you can import these components as pages. On iOS, file based routing does not exist. Solito fills in the cracks. His video at Next.js Conf was really informative: ▶ this video .
in “Solito – React Native and Next.js unified” · View on HN
This talk at Nextjs Conf explores cross platform solutions for common issues like routing, styling and animation. Found it to be quite helpful! ▶ this video
in “Building a Cross-Platform Web and Mobile App from the Ground Up” · View on HN
For anyone interested, here is the keynote introducing Solito from Next.js Conf 2021 by it's creator Fernando Rojo. ▶ this video
in “Solito – React Native and Next.js unified” · View on HN
Creator of Solito here. I've built a number of React Native libraries (Moti, Dripsy, etc). Happy to answer any questions. I originally gave a talk at Next.js Conf about how/why we use Next.js with React Native: ▶ this video Navigation is the hardest piece of sharing code across platforms. Web has plain URLs for navigation state, whereas apps have complex sets of nested navigation patterns (stacks, tabs, modals, drawers). By combining the approaches into a single mental model and API, devs can build for Web and Mobile with ease. This is touched on at length in the "Methodology" and "Gradual Adoption" sections of the Solito docs. The gap between web devs and native devs is shrinking. This stack enables you to ship native apps and websites with a single codebase. I'm the only frontend engineer at our startup, and I was able to do just that as we scaled to thousands of users (see [link] ). My goal with Solito is to 1) provide the code to let others do it, and 2) perhaps more importantly, document clear patterns to deal with platform differences.
in “Solito – React Native and Next.js unified” · View on HN
1. you can code share with iOS and Android. 2. the primitives provided by React Native solve the many bugs you get from low-level CSS and HTML. there are many other reasons, I touch on all of them in my Next.js + React Native talk at Next.js Conf: ▶ this video I built [link] with React Native and Next.js as the only front-end engineer and designer, and our iOS app and website share 99% of code across hundreds of screens.
in “Solito – React Native and Next.js unified” · View on HN
And then there's one sr front end dev who started doing $10 mn ARR with a web app and react-native apps for iOS and Android from a Next.js monorepo all by his lonesome ▶ this video I really think the React-Native and Next.JS (and tRPC and Prisma and GQL) have hit a PHP-style tipping point where we are going to see a great new flowering of cross platform web and mobile apps (last seen in the Facebook / Wikipedia era 2007-2014 era and driven by MySQL + PHP + jQuery + Phonegap). I feel excited, the hype is finally real. So yeah sometimes that mixed abstractions complexity works against you, I feel like every decade or so it converges into a stack you can really use to effectively GTD.
in “Is the madness ever going to end?” · View on HN