Podcasts about reactjs

Piyush Jain, Founder and CEO of Simpalm and co-founder of Ducknowl, is on a mission to solve real-world challenges by combining technology and entrepreneurship. With over 15 years of experience building custom software solutions, Piyush helps businesses turn complex ideas into practical applications by blending technical depth, business acumen, and a strong problem-solving mindset. We explore Piyush's AI Ideation Framework—Validate idea, Proof of concept, Design, Competitor analysis, and Feature selection—a practical approach to building software in the post-AI era. Piyush explains how AI can help teams better understand user personas, validate product assumptions, and rapidly prototype ideas, while human expertise remains essential in design, architecture, and production-grade development. He also shares how prompt engineering, peer-reviewed prompting, and a right-shoring delivery model can help businesses build smarter, faster, and more cost-effectively. — 3D Print Your Software with Piyush Jain Good day, dear listeners. Steve Preda here with the Management Blueprint, and my guest today is Piyush Jain, the Founder and CEO of Simpalm, a custom software development company, and the co-founder of Ducknowl, a candidate screening and assessment application business for high-volume recruiting. Piyush, welcome to the show.  Thank you, Steve. Thanks for inviting me.  Well, I’m very curious about the stuff that you have to share with us, and I’d like to ask first about your personal purpose. What is your “why,” and how are you manifesting it in your business?  Yeah, so that’s a very interesting question. And I think for every entrepreneur or tech founder, really, that's the motivation—why you want to do certain things. So for me, if I look at it, my personal “why” is: why are we not solving challenges? Or why are we not solving them the right way? Why are we not transforming our lives? I grew up in India and then came to the US, so I've seen many different parts of the world—from Asia to North America. I see people face different challenges, but then we are not focusing on solving those problems. A lot of it I see is there’s a lot of challenges in the world because I believe there are not enough entrepreneurs. Because entrepreneurs are the ones who really take risks, combine everything, and create solutions. That was like me, right? That’s what I learned growing up, that I think I can do that, right? I can combine the technical knowledge and the business acumen and create solutions that people like, solve their challenges. Growing up, like I'm more on the technical side.Share on X I was inclined more toward science and technology, but then as I got into my undergrad and grad school, I realized that I have that entrepreneurship aspect, but it's still around science and technology. That’s when I realized that, you know what, I cannot be a pure scientist or maybe a pure entrepreneur, but I can be someone who can combine these two, because my main driving factor is problem-solving. I can combine these two and then live my life, be very happy with what I do. That has been my motivation. I like it. So solving challenges and being an entrepreneur, and kind of combining the two—being the technical expert and the entrepreneur in one. Now, one of the things that we always talk about on this podcast is frameworks. And you have developed a really good one for AI ideation, which I think is something that everyone needs to do these days or use these days, and it helps you create business apps and other business applications. Can you share with me how that framework works, and what are the steps in it?  Sure, yeah, definitely. So just to give you a brief background, we've been building software for the last 15 years. Some companies have used different frameworks, whether it's Agile or Waterfall in SDLC, in building the software, right? There are different methodology that companies have used, and they've been good, successful—they've played their role. But now, with the advent of AI, things have changed. We had to figure out, in our organization, how to use AI, and that's how this framework was built. My team helped me building this framework as well.Share on X But we realized that we were losing business—we were losing clients—since we didn't have an AI framework that would fit our clients. Again, for me, it's a challenge. So anytime I see a challenge, it create brain juice in me, right? So I said, okay, let's figure out how we create this framework. How did you do it?  So really, we built this framework—very interesting. A lot of the steps are similar, but then a lot of things are different.Share on X Whenever client comes to us and says, “Hey, we want to solve this challenge,” what we do is we do enough research. And now we use a lot of AI tools to really understand the problem better and understand the user persona. When you build any software application, there is a person who's going to use that. Sometimes we used to do user research or focus studies to understand that. Now, with the help of AI, we can get a lot of ideas about the user persona. For example, maybe we are building a healthcare application for an anesthesiologist. I don’t know much about that. I know, I mean, because I have been through some medical surgery and all that, but I can't fully understand their user persona or their requirements with respect to the application we're building. But now, with AI, I can actually ask different AI models, “Hey, we are building this app for anesthesiologists. What are their pain points? How would they see it?” So all that deeper mindset and psychology we can get using AI.  You are validating the idea by interrogating AI applications.  What users are going to like and all that. So I will always use this term earlier. In software engineering, now we have this pre-AI and post-AI, right? If you read history, we talk about before Christ and after Christ, right? Yeah. So it's a similar thing now. Yeah, exactly. Or before Covid, after Covid. Before AI, after we did all the user research and everything and created a requirements document, we would usually do design, create like a visual design of the software. But now, with the AI framework, we don't do that. That's not the next step. What we do instead is create a quick prototype using AI platforms.Share on X  So there are a lot of AI platforms—like Lovable, Claude. Now ChatGPT launched Codex for coding, and Replit. Depending on what kind of application you're building—for example, maybe if you're building a web-based application—then I recommend using Lovable or Replit. They're very good at creating that. Whatever software you want to build, whatever user personas that you’re addressing, you can feed into that and it’ll create like a prototype application. Okay.  So what that does is actually, then this prototype, clients can just take it to their customers or internal users and get feedback. A picture is better than a thousand words. Organizations discussing an idea is very different from when they actually see something. Then everybody starts chipping in—“Oh yeah, I see this in the prototype, but I don't want this,” or “I want to move things around,” or “This is what I want.” Basically, building a prototype on AI platforms is much faster than building wireframes and design prototypes like we used to do earlier. So that has changed. So you're 3D printing your software, right?  Yes, exactly. There you go. Well, that’s a very good way you put it together. Yeah. So, yeah, exactly. You’re just 3D printing the software, right? So you can see it, visualize it, and then once you go through that, it creates a lot of better ideas about the software in faster time. So once you have that, then you go into UI/UX design. So in that also, there are two steps. One is wireframing. Wireframing is like creating the flow in black and white. It's like creating a skeleton of your software. It does not have the color, the font, or the branding, but you just create all the different user journeys, the screens, the flow, and the fields that will be there on the screen. So we have integrated AI into that step as well. Earlier, it used to be created by a designer or a business analyst. Now we are using software like Uizard or UX Pilot, where we define what we want—what kind of user journey, flows, and screens—and it creates that. It spins out those wireframes in minutes. So really that has reduced now. The time it used to take to create wire frames is faster now.  So you're designing the wireframes with AI?  Yes, but it's just the wireframe part of it, and it's still guided by our expert VA or designer—someone who knows how to really visualize things and has done a lot of wireframes and sketches. So they know what to tell the AI. Prompting is very important. It's very important that you know how to prompt—what to ask for—so that you can get variations and differentiation in the wireframes. You don't want a standard AI-created wireframe. Everybody can recognize AI-generated images now, right? If I show you one, you'd say, “Oh yeah, it's AI-generated.” I know that, right? Yeah. So again, we keep the human intelligence. We're not asking AI to create the full software end-to-end. It never works—it'll never work. It just doesn't. I know that's a strong statement, but I'm saying that based on experience and an understanding of human behavior and psychology. So AI agents will not be able to code software, in your opinion?  No, they can do the coding, but they cannot build the whole software end-to-end—a production-deployed software. Because these software are being used by humans. You have to have human intelligence to understand and define what you need and how it works.Share on X You can maybe create some software, but it doesn't work very well. Even if you use all these platforms, you can cut down your production time and cost by 30%, 40%, 50%, right? That's the number we are seeing—30 to 50% reduction, depending on the software you're building and the objectives. So just to recap—you validate the idea by interrogating Claude and ChatGPT, asking about the needs of that customer, the psychology of the customer—that's step number one. Step number two is 3D printing the software with Lovable or Replit—so proof of concept. And then you design the wireframes. And then what's next after you design the wireframes? What's the next step?  So that’s a good thing. That’s it. Now I'm going to talk about the human element—some people listening to this podcast will be surprised. Now it comes to visual design, right? So you've created the skeleton, and now you have to add the skin, the tone, the color, the emotion to the design, to the workflow. Now, we have tried AI, but it doesn't work. It's very monotonous. So we use an experienced visual designer, a UX designer, for that step—to give it emotion. When you use AI—I wish I could show you some examples—it creates very similar kinds of designs for apps and software. So what we did is we gave it three different apps with very different objectives and everything, and the designs it came up with were very similar—blocks, buttons—very monotonous. So there's no differentiation. And design is the main thing that becomes the differentiator, right?  Yeah.  So that's what we learned from our experience. And I say that very categorically in all of my talks—that visual design, final UX, has to be human, not AI.Share on X Because you are communicating emotions, right? And AI is still not there to communicate emotions.  Yeah. It doesn’t have emotions.  Well, some people will argue with you and say, “No, it can understand if you're sad or unhappy.” But my response to that is—it's because we've programmed it that way. But things change based on situation, context, ethnicity, culture, fear—how people express nervousness, fear, and all that—it's very different. So there was this AI video interviewing company five or six years ago. They were sued by the Department of Justice because they were trying to detect emotions of people like anxious, nervous, when the interview was happening.  It turned out their model was trained only on one race—they didn't account for other races or ethnicities. So their model failed, and they were sued by Department of Justice for that. So yeah, emotions is something—maybe they have unlimited dimensions, we don't know. So it's hard to program that. So basically: ideation, prototype, wireframe, and then final visual design—that's the discovery and design framework. Now, when it comes to development framework, this is where AI has been a game changer—the coding part. But again, you have to be very careful about how you use AI in your coding pattern with your coding team. It depends on the application, it depends on the tech stack, right? Every platform has its own strengths and weaknesses. For example, if you want to build a web-based application in the React JS framework, then Lovable is great. That's very good—very efficient and cost-effective. Then Claude is there. Claude has been really good in software engineering. I would say it has been built and designed mostly for coding, right? Anthropic—their idea, their starting point—was coding, how to make coding and software engineering better.  So they've been a front runner in the race. ChatGPT is trying to catch up using Codex, and Copilot is great. Copilot is mostly used by enterprises who are on the Microsoft stack. They use Copilot a lot for coding in .NET and enterprise-level applications. They’re used to co-pilot. It’s because they feel comfortable with Microsoft security policies and all that. That’s fine. But in general, we see Claude to be at the top—from our perspective. We've also built a framework for software coding. In software development, there's a popular process called peer review. So when you create source code, you get it reviewed by your peer—your colleague.Share on X  Is this what happens on GitHub?  Yeah, yes. So basically anywhere—any source code repository—you can do that. So your team members can help you make your code better and more efficient.  Yeah, I understand. But now we have a step called prompt peer review. When you're using prompts to build software, those prompts get reviewed by team members. Because if your prompts are not very specific or good enough all the way through the SDLC, you can run into a lot of challenges trying to fix the code. Because now you have a situation where you have code that you have not written fully, and when you ask AI to change something in the code, sometimes it ends up changing a lot of things that you don't want it to change. Yeah.  That's what we've seen, and that's why we evolved. Before we build any software, we create maybe a 10-, 20-, 30-page prompt document, where we go through each screen and function and write it out. It's very sophisticated—it has evolved really well. But the thing is, it takes a few days to do that within the team, because we know if we do it right, the next step is faster and more accurate. So really, the prompt document—think of it more like an architecture document. Earlier, we used to create a solution architecture document, defining all the tools, the design, everything.  But now it's more like an AI-driven solution architecture document with prompts, which get reviewed by team members. So we do that, and then we run that, and we get the code and everything. So I have a CTO club—I run a CTO Club in Maryland—and I was talking to CTOs. They're all using this, but some of them are so advanced that they actually define the test cases in the beginning. They define, “Okay, this is what I want, this is the function I want, and these are the test cases I want it to pass.” That's even more advanced. If you can do that, you can have very efficient code.  Yeah, I love it.  So is that the end? You have your test cases, you design the prompt, you peer-review the prompt, and you already had the prototype, so now you're coding the software—what's the last step?  Yeah. Then there’s an integration as well. So AI doesn’t do the integration so well. You can do the front-end coding, you can do the back-end coding, you can probably create the APIs. APIs require a lot more human intervention. But once you have that, then you have to connect it, right? You have to connect the front end with the backend. A lot of that is still done by the programmer. It's hard to rely on AI for doing that. And again, it depends on the application. Maybe if it's a smaller application, maybe you can have AI do that. But if it's a bigger application—we mostly build bigger applications—then integration, then final QA and testing, and deployment.  So all that is there. But in each of these steps, you can use some sort of AI tool to speed up the process. But the key is you still have to have your architecture, the process. You have to know the steps more. You have to be a good, experienced developer to use AI efficiently if you want to build a production-ready application. You can build a prototype. Anybody can build a prototype on Replit or Lovable, but it's not going to be production-ready that you can give to your customer and charge them money. So that’s the differentiator.  Yeah, I understand. So Piyush, I’d like to switch gears here. I understand the AI ideation framework—that's great. We talked about the technical part of it, the curiosity, the technical challenges. Let’s talk about the entrepreneurship part, which is also part of your profile. So what drives the growth of your business? What would you say drives it?  For us, there are multiple factors that drive the growth of our business. The first is, again, our problem-solving attitude. Any client that comes to us we communicate in that modelShare on X The problem, the challenge, the solution, the business part, the value proposition we bring. And the second factor is our location. We are here in Maryland, and we have another office in Chicago. So being here, we have a global shoring model—that's a main driving factor of our business from the entrepreneurship perspective. So what the global shoring model is: our client-facing team, the senior team, is here—solution architects, sales engineers, designers, project managers, business analysts—they are here in the US, client-facing. And our dev team and testers are in our offshore locations.  Some people call it hybrid shoring. I call it right shoring. The reason I call it right shoring is because in this model, you have the right people at the right shore, so you get the most value. Here, you have people who understand the culture, the product, the context—because products are used by people in a certain culture. And if you are not in that culture, if you haven't experienced it, it's always harder to design the right software solution. I was one of the first people to start that model here in the DMV area for mid-size and smaller companies. This model existed before, but mostly for large enterprise companies. They have used that. But I started to offer that 16 years ago to smaller companies. Either companies were just going offshore, or they were doing onshore, right? I introduced this hybrid—or right-shoring—model, and it has been well received by our customers. So that’s it.  So what is one thing that you’re trying to figure out in your business right now?  Right now, what I'm trying to figure out in my business is scaling. I mean, we have built solutions for many different industries. We have built solutions for different clients in fintech, healthcare, education, nonprofit, startups, IoT, construction. But now what we are trying to figure out is how do we create some off-the-shelf solutions for different industries? Because one challenge we see is that, from the client's perspective, getting custom software built takes time and money. But in certain use cases, we can have off-the-shelf, industry-specific solutions, and then customize those based on the client's needs.  So that's what we are trying to figure out—across different industries, what those solutions can be—so we can scale and also make it easier. And these are more like AI-driven, off-the-shelf solutions that are customizable. So think of it like Salesforce—its core is off-the-shelf, but then you can customize the front end and a lot of other things. Not exactly like Salesforce, but more like industry-specific solutions for different use cases—nonprofit, construction, right? With those, overall, we can build solutions faster.  That’s fascinating. So how has the offshoring—or right shoring, as you call it—model evolved over the past 10 years? Is it different now than it was 10 or 20 years ago?  Yeah, I think that's a great question. It has evolved and changed. Earlier—maybe 10, 12 years ago—when we were talking about hybrid shoring, we were mostly talking about the US and Asia. But now we have different players. We have the nearshore model, which has become quite popular as well—like South America. We have team members in nearshore locations as well, in South America, because we want to leverage different time zones, resources, and culture. And we've seen very positive results. Then you have Eastern Europe. We have competition from countries like Ukraine, Belarus, Romania, Poland. I think it’s the part of the globalized world, right? It's like energy flowing in different spaces—it's not limited to one place, which is great. That's one way it has evolved.  I also know some companies working in Kenya—there are developers there. Some companies are setting up in East Africa, West Africa. So different places are playing roles now. That’s one thing I see. And now, with the help of AI, what's going to happen is it will play two roles. One— in many situations, with AI, you can do more things onshore. That’s one aspect of it. And second—with AI, someone sitting offshore who knows how to use AI can become very competitive as well. We don't have enough data yet to fully see how this will evolve, but maybe in a year or so, we'll see how it plays out.  But I also find that with these simultaneous translation tools—like Apple, I think an iPhone can now translate in all languages. Essentially, another barrier falls that if the language and knowledge of your offshore contractor is not perfect, they can understand things much more clearly because of simultaneous translation. Even on Zoom, you can now flip a switch and they can read what's being said in their own language during a conversation. So that's amazing, I think.  Yeah. That’s amazing. That’s amazing. They can understand more about the culture and mindset. So that's something have to see. Again, I think it depends on the use case, the application, the problem we're solving. But in some cases, it might be great news for onshore—we can keep more dollars here. But keeping dollars here with AI also means a lot of that spend is going to AI, right? So that's one thing—we have to be very careful. Yesterday, in our tech breakfast, our presentation was about how to optimize your AI tokens. There are some companies spending $150,000 per year per employee on tokens. Wow.  That's like the salary of one employee.  Yeah.  A mid-level developer—$150K—they're spending that much. And then they’re trying to figure out how to optimize it. And on top of that, they have cloud costs, right? AWS, Azure—those costs are still there—and then you add AI. So it's a lot of money. You really have to be very smart about understanding and optimizing it. That’s why the prompting is so important, right? It's not just about getting the right software—it's also about getting the cost down.  Yeah. Again, you need expert people who can prompt well, because it's about being able to communicate well. Prompting is about communication—it's about clarity, brevity, security, all that stuff. So, Piyush, we're coming close to the end of the recording. If someone would like to learn more about the applications you develop, how you're using AI, and how you can help their business develop technology, where can they find you? What's the best way to get in touch with you? Sure, there are many ways people can reach out to me. They can go to my website, www.simpalm.com—we have a contact form there. They can submit the form, or they can reach out to me via email directly at contact@simpalm.com. They can also connect with me on LinkedIn. I'm on LinkedIn—message me there if somebody needs anything. I always like discussing problems and what the solutions can be. If anybody reaches out to me, I'm always very quick to respond.  That's awesome. So Piyush Jain, the CEO of Simpalm—and we didn't even talk about your other business, Ducknowl—thank you for coming, and thank you for sharing your insights and your framework on how to build an ideation framework for AI. So thanks for sharing that. And if you're listening and you enjoyed this conversation, then stay tuned, because every week we have another entrepreneur sharing their insights and frameworks with you. So make sure you follow us on YouTube, subscribe, and give us a review on Apple Podcasts. So thanks for coming. Thank you, Steve. It was a pleasure talking to you. Important Links: Piyush's LinkedIn Piyush's website

In this episode, I share an honest update about the future of the Rocket Ship Podcast.After running the show for quite a while and experimenting with different formats, I've decided to pause the podcast for now. In this episode I explain why, what changed, and what I want to explore next.

React Native 0.84 is here (with Hermes V1 by default), WebAssembly is landing inside Hermes, Expo is experimenting with AI “Agent Skills,” and there might be a new React Native framework coming from TanStack

This week's episode is packed with deep React Native ecosystem updates, a clear shift toward AI-first tooling, and some really positive momentum on Tiny Harvest. We talk new APIs, better performance, smarter automation - and why it feels like AI has officially crossed a tipping point for most developers.⚛️ React Native Radar⏳ Expo SDK 55 – still not released, likely 1–2 weeks out

This week's episode is packed with Expo-heavy updates, early looks at AI agent tooling, and some honest numbers and lessons from Tiny Harvest. We also zoom out and talk about the idea that we might be living through an Industrial Revolution of Software.⚛️ React Native Radar

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/413Alexandre Malavasi - CTO at Marelo & Author of "Modern Full-Stack Web Development with ASP.NET Core"Albert S. Tanure - Cross Solutions Architec at Microsoft & Author of "ASP.NET Core 9 Essentials"RESOURCESAlexandrehttps://x.com/alemalavasihttps://github.com/alexandremalavasihttps://www.linkedin.com/in/alexandremalavasiAlberthttps://x.com/alberttanurehttps://github.com/tanurehttps://www.linkedin.com/in/albert-tanurehttps://www.codefc.io/enDESCRIPTIONMicrosoft Cloud Solution Architect Albert Tanure interviews Microsoft MVP Alexandre Malavasi about his fourth book, "Modern Full-Stack Web Development with ASP.NET Core". The discussion explores the challenges of writing comprehensive technical books, the importance of foundational knowledge in full stack development, and how to integrate ASP.NET Core with modern JavaScript frameworks like React, Angular, and Vue.js.Alexandre emphasizes that successful architecture decisions depend primarily on team expertise and the ability to facilitate change, rather than following trends.The conversation also highlights the critical importance of looking beyond just coding - encompassing project planning, DevOps practices, monitoring, and continuous optimization - to truly bring value to customers and become well-rounded software engineers.RECOMMENDED BOOKSAlexandre Malavasi • Modern Full-Stack Web Development with ASP.NET Core • https://amzn.to/4pvEXnYAlexandre Malavasi • Implementing Design Patterns in C# 11 and .NET 7 • https://amzn.to/49CapwnAlexandre Malavasi • Enterprise Applications with C# and .NET • https://amzn.to/4iiVidkAlexandre Malavasi • Implementing Design Patterns in C# and .NET 5 • https://amzn.to/3JU5UD2Albert Tanure • ASP.NET Core 9 Essentials • https://amzn.to/43bH73tBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This week's episode is a quieter one on the news front - but a big one for reflections.We look at the latest signals from the React Native ecosystem, then zoom out into what I've been building lately, why I can't stop thinking about my game project, and how AI has quietly become one of the most useful tools in my daily workflow.⚛️ React Native RadarState of React Native 2025 survey: early impressions & what stands outJavaScript Rising Stars 2025: what's gaining traction (and what isn't)

2025 is coming to an end - and instead of another release recap, this episode takes a step back.In this year-in-review, I reflect on what actually mattered in React Native in 2025:the shifts that changed how we build apps, what was overhyped, what quietly became important, and the lessons I'm taking into 2026.This is a calm, opinionated look at the year - from the perspective of someone building apps, teaching developers, and navigating a fast-moving ecosystem.

Àlex y David revisan las predicciones realizadas para 2025 para analizar con transparencia qué se ha cumplido y qué retos han marcado el año en MarsBased. A pesar de no haber sido un año récord, con una facturación estable en los 2,8 millones de euros, la empresa ha vivido un crecimiento estructural sin precedentes al incorporar a diez nuevos perfiles en doce meses. En este balance, se detalla el impacto de la pérdida de un cliente clave, el cambio del mercado hacia contratos más cortos y la decisión estratégica de estandarizar el stack tecnológico en Ruby y React para ganar eficiencia operativa.De cara a 2026, el análisis se enfoca en la reactivación del sector y la apuesta por la Inteligencia Artificial, que se proyecta como un motor de negocio fundamental. Con una estructura de equipo ya consolidada y el podcast como nuevo eje de comunidad, MarsBased marca el ambicioso objetivo de alcanzar los 3,5 millones de euros de facturación. Este vídeo ofrece una visión realista sobre la gestión de una consultora tecnológica, comparando las expectativas iniciales con la realidad de un mercado en constante transformación.Support the show

This week's episode covers a big React Native release, a critical React security vulnerability, and a wave of performance and DX improvements across the ecosystem. I also share updates from Tiny Harvest and talk about the realities of AI-assisted coding as projects grow.⚛️ React Native Radar

This week's episode covers a mix of major React Native updates, powerful new tools, and insights from publishing my AI-engineered farming game, Tiny Harvest. We also talk about early experiments like React Native Rails and what CSS Grid means for the future of layout on mobile.⚛️ React Native Radar:✨ Gifted Chat v3 rewrite – modernized API, performance fixes

AI Assisted Coding: Treating AI Like a Junior Engineer - Onboarding Practices for AI Collaboration In this special episode, Sergey Sergyenko, CEO of Cybergizer, shares his practical framework for AI-assisted development built on transactional models, Git workflows, and architectural conventions. He explains why treating AI like a junior engineer, keeping commits atomic, and maintaining rollback strategies creates production-ready code rather than just prototypes. Vibecoding: An Automation Design Instrument "I would define Vibecoding as an automation design instrument. It's not a tool that can deliver end-to-end solution, but it's like a perfect set of helping hands for a person who knows what they need to do."   Sergey positions vibecoding clearly: it's not magic, it's an automation design tool. The person using it must know what they need to accomplish—AI provides the helping hands to execute that vision faster. This framing sets expectations appropriately: AI speeds up development significantly, but it's not a silver bullet that works without guidance. The more you practice vibecoding, the better you understand its boundaries. Sergey's definition places vibecoding in the evolution of development tools: from scaffolding to co-pilots to agentic coding to vibecoding. Each step increases automation, but the human architect remains essential for providing direction, context, and validation. Pair Programming with the Machine "If you treat AI as a junior engineer, it's very easy to adopt it. Ah, okay, maybe we just use the old traditions, how we onboard juniors to the team, and let AI follow this step."   One of Sergey's most practical insights is treating AI like a junior engineer joining your team. This mental model immediately clarifies roles and expectations. You wouldn't let a junior architect your system or write all your tests—so why let AI? Instead, apply existing onboarding practices: pair programming, code reviews, test-driven development, architectural guidance. This approach leverages Extreme Programming practices that have worked for decades. The junior engineer analogy helps teams understand that AI needs mentorship, clear requirements, and frequent validation. Just as you'd provide a junior with frameworks and conventions to follow, you constrain AI with established architectural patterns and framework conventions like Ruby on Rails. The Transactional Model: Atomic Commits and Rollback "When you're working with AI, the more atomic commits it delivers, more easy for you to kind of guide and navigate it through the process of development."   Sergey's transactional approach transforms how developers work with AI. Instead of iterating endlessly when something goes wrong, commit frequently with atomic changes, then rollback and restart if validation fails. Each commit should be small, independent, and complete—like a feature flag you can toggle. The commit message includes the prompt sequence used to generate the code and rollback instructions.  This approach makes the Git repository the context manager, not just the AI's memory. When you need to guide AI, you can reference specific commits and their context. This mirrors trunk-based development practices where teams commit directly to master with small, verified changes. The cost of rollback stays minimal because changes are atomic, making this strategy far more efficient than trying to fix broken implementations through iteration. Context Management: The Weak Point and the Solution "Managing context and keeping context is one of the weak points of today's coding agents, therefore we need to be very mindful in how we manage that context for the agent."   Context management challenges current AI coding tools—they forget, lose thread, or misinterpret requirements over long sessions. Sergey's solution is embedding context within the commit history itself. Each commit links back to the specific reasoning behind that code: why it was accepted, what iterations it took, and how to undo it if needed. This creates a persistent context trail that survives beyond individual AI sessions. When starting new features, developers can reference previous commits and their context to guide the AI. The transactional model doesn't just provide rollback capability—it creates institutional memory that makes AI progressively more effective as the codebase grows. TDD 2.0: Humans Write Tests, AI Writes Code "I would never allow AI to write the test. I would do it by myself. Still, it can write the code."   Sergey is adamant about roles: humans write tests, AI writes implementation code. This inverts traditional TDD slightly—instead of developers writing tests then code, they write tests and AI writes the code to pass them. Tests become executable requirements and prompts. This provides essential guardrails: AI can iterate on implementation until tests pass, but it can't redefine what "passing" means. The tests represent domain knowledge, business requirements, and validation criteria that only humans should control. Sergey envisions multi-agent systems where one agent writes code while another validates with tests, but critically, humans author the original test suite. This TDD 2.0 framework (a talk Sergey gave at the Global Agile Summit) creates a verification mechanism that prevents the biggest anti-pattern: coding without proper validation. The Two Cardinal Rules: Architecture and Verification "I would never allow AI to invent architecture. Writing AI agentic coding, Vibecoding, whatever coding—without proper verification and properly setting expectations of what you want to get as a result—that's the main mistake."   Sergey identifies two non-negotiables. First, never let AI invent architecture. Use framework conventions (Rails, etc.) to constrain AI's choices. Leverage existing code generators and scaffolding. Provide explicit architectural guidelines in planning steps. Store iteration-specific instructions where AI can reference them. The framework becomes the guardrails that prevent AI from making structural decisions it's not equipped to make. Second, always verify AI output. Even if you don't want to look at code, you must validate that it meets requirements. This might be through tests, manual review, or automated checks—but skipping verification is the fundamental mistake. These two rules—human-defined architecture and mandatory verification—separate successful AI-assisted development from technical debt generation. Prototype vs. Production: Two Different Workflows "When you pair as an architect or a really senior engineer who can implement it by himself, but just wants to save time, you do the pair programming with AI, and the AI kind of ships a draft, and rapid prototype."   Sergey distinguishes clearly between prototype and production development. For MVPs and rapid prototypes, a senior architect pairs with AI to create drafts quickly—this is where speed matters most. For production code, teams add more iterative testing and polishing after AI generates initial implementation. The key is being explicit about which mode you're in. The biggest anti-pattern is treating prototype code as production-ready without the necessary validation and hardening steps. When building production systems, Sergey applies the full transactional model: atomic commits, comprehensive tests, architectural constraints, and rollback strategies. For prototypes, speed takes priority, but the architectural knowledge still comes from humans, not AI. The Future: AI Literacy as Mandatory "Being a software engineer and trying to get a new job, it's gonna be a mandatory requirement for you to understand how to use AI for coding. So it's not enough to just be a good engineer."   Sergey sees AI-assisted coding literacy becoming as fundamental as Git proficiency. Future engineering jobs will require demonstrating effective AI collaboration, not just traditional coding skills. We're reaching good performance levels with AI models—now the challenge is learning to use them efficiently. This means frameworks and standardized patterns for AI-assisted development will emerge and consolidate. Approaches like AAID, SpecKit, and others represent early attempts to create these patterns. Sergey expects architectural patterns for AI-assisted development to standardize, similar to how design patterns emerged in object-oriented programming. The human remains the bottleneck—for domain knowledge, business requirements, and architectural guidance—but the implementation mechanics shift heavily toward AI collaboration. Resources for Practitioners "We are reaching a good performance level of AI models, and now we need to guide it to make it impactful. It's a great tool, now we need to understand how to make it impactful."   Sergey recommends Obie Fernandez's work on "Patterns of Application Development Using AI," particularly valuable for Ruby and Rails developers but applicable broadly. He references Andrey Karpathy's original vibecoding post and emphasizes Extreme Programming practices as foundational. The tools he uses—Cursor and Claude Code—support custom planning steps and context management. But more important than tools is the mindset: we have powerful AI capabilities now, and the focus must shift to efficient usage patterns. This means experimenting with workflows, documenting what works, and sharing patterns with the community. Sergey himself shares case studies on LinkedIn and travels extensively speaking about these approaches, contributing to the collective learning happening in real-time.   About Sergey Sergyenko   Sergey is the CEO of Cybergizer, a dynamic software development agency with offices in Vilnius, Lithuania. Specializing in MVPs with zero cash requirements, Cybergizer offers top-tier CTO services and startup teams. Their tech stack includes Ruby, Rails, Elixir, and ReactJS.   Sergey was also a featured speaker at the Global Agile Summit, and you can find his talk available in your membership area. If you are not a member don't worry, you can get the 1-month trial and watch the whole conference. You can cancel at any time.   You can link with Sergey Sergyenko on LinkedIn.

This week's episode is packed with performance breakthroughs, new UI tooling, graphics innovation, and my own deep dive into AI-assisted game development. We compare Valdi vs React Native, explore what Uniwind v1 means for the styling ecosystem, and look at how WebGPU is reshaping the future of graphics on mobile.⚛️ React Native Radar:

You'll learn the six core JS skills to master before frameworks, why TC39 keeps changing the language, and how to test your skills with a challenge you can access below.

This week's episode covers another wave of React Native ecosystem updates — from Expo's new AI-native tools to faster storage, cross-framework experiments, and even a React Native + Godot integration.⚛️ React Native Radar:

This week's episode dives into all the major announcements from React Conf 2025—from the upcoming changes to React Native DevTools and React Foundation, to long-awaited features like CSS support and Hermes V1. Plus, I share updates on my latest projects, including the release of my Pocket Clone and progress on the Wolt Clone.⚛️ React Native Radar:

This week's episode covers the latest React Native ecosystem updates, a few personal wins, and what's next for my upcoming projects.⚛️ React Native Radar:React 19.2 – small update, big polishReact Native 0.82 RC5 – new fixes before the full releaseVega OS – Amazon's new platform for apps and gamesReact Native Enriched (RTE) – rich text editor by Software MansionNitro Fetch – faster networking from MargelolocalStorage API with Expo SQLiteLive Activities now even easier to integrateApp structure best practices for clarity and scalabilityOS Animations library now open sourceAccess iOS APIs directly from JS – new possibilitiesVoltra on the horizonUniWind public beta feedback looks promisingNativeWind v5 preview releasedHeader fix coming to React Native ScreensReact Native Buoy – floating debug & support tools inside your app

In this episode, I'm joined once again by Alberto Moedano aka Code with Beto. We discuss the exciting features of Expo SDK 54, including the introduction of React Native 0.81, the new Expo Router version 6, and the integration of Expo UI with SwiftUI.Beto and I also delve into the benefits of the Liquid Glass design, the improvements in build times, and the future of Expo Maps.Beto finally shares insights on his successful tool Snap AI and the importance of keeping up with SDK updates for better performance and user experience.

This week's episode is packed with big updates in the React Native world—new tools, major releases, and even a glimpse into the future of the framework.⚛️ React Native Radar:Maestro 2.0 released – faster, more powerful mobile testingAudio support updates from Software MansionLegendList 2 brings better list performanceReanimated 4 stable – the next step for animations in RNNitro Fetch – the network layer gets an upgradeShopify migrates fully to the New ArchitectureModule Federation for React Native appsExpo Launch – a new way to get apps into the store fasterNew GlassEffect module in Expo SDKReact Native 0.81 – Android 16 support, faster iOS builds, SafeAreaView changesExpo SDK 54 beta now availableRFC0929 – removal of the legacy architecture officially on the way

In this episode, I'm joined once again by Jamon Holmgren, co-founder of Infinite Red and host of React Native Radio. We dive deep into the new React Native architecture - from TurboModules, Fabric Components, and Nitro, to whether it's time for everyone to migrate.We also explore how AI is already changing development, what the future holds for tools like Ignite and Reactotron, and whether React Strict DOM will reshape how we build for web. Jamon shares his perspective on current trends, and why he believes the next few years will bring a new wave of innovation in the React Native ecosystem.Previous Podcast with Jamon: https://podcast.galaxies.dev/episodes/055-why-companies-use-react-native-job-interviews-open-source-trends-with-jamon-holmgren

In this week's episode, we explore major updates in the React Native ecosystem—fresh UI tools, performance boosts, and what the end of the old architecture means for developers. Plus, we dive into the debate on web vs in-app purchases and share the latest AI dev tool trends.⚛️ React Native Radar:FlashList v2 – a complete ground-up rewrite for the new architectureCallstack Shimmer – fast, customizable shimmer effects for skeleton loadingRozenite – a new plugin framework for React Native DevToolsNew Expo Modules: Animated Toast, Liquid Glass View, iOS Popover TipElevenLabs React Native SDK – bring advanced AI voice features to your appVercel AI SDK v5 releasedUsing Expo Patch-Project for native changesContext Menu updates by Evan BaconNative CSS support coming to ExpoNew screen transitions in React NavigationDiscussion: Is anyone still using the React Native CLI?End of the old architecture – newArchEnabled=false removed in RN 0.82

This week's episode dives into what's next for animations, games, and performance in React Native—plus a wave of new tools and examples from the community.

In this week's episode, we explore new tools, visual upgrades, and some trending controversy in the React Native ecosystem—plus, I finally shipped my Amazon clone and share what's coming next.

This week, we're diving deep into some of the most exciting updates in the React Native ecosystem—and I'm sharing a few personal shifts too.

In this week's episode, we explore a handful of exciting tools and tutorials for React Native developers - plus a personal milestone:

In this week's episode, we explore the latest updates and trends in the React Native world—and beyond:

The AppJS took place and there's a lot to learn from the amazing talks about the current state of React Native and its future. From frozen architecture to React Native news and new packages, we dive into everything in this episode!Also in this episode:- Why Simon is killing his app- My next clone project

While the AppJS is about to kick off, we talk about some cool new packages and updates around Reanimated and a new solution for local-first apps!Also in this episode:- New React Native Essentials - Apple still doesn't like my app- New Expo Router v5 Course- Are you VibeCoding?

No big news besides the RC of React Native 0.80, which gives us time to talk about the current version hell for React Native developers, and a great new Expo DevTool for everyone using TanStack Query!Also in this episode:- RSCs are underrated- Preview of Dead Simple Invoice App- Apple doesn't like my app- Open Water Swimming & Cold Water Shock

Expo Router v5 was released, which dramatically improves authentication flows and finally allows to use RSC in production - although still in beta. Beyond that William Candillon shared epic updates about Skia and WebGPU, making even more powerful React Native apps possible in the future.Also in this episode:- Galaxies Lifetime pricing with one-time payment- Receiving Feedback on Podcast & Apps- Sharing my next app projects- Flutter devs love React Native

Expo SDK 53 was released after a short beta with many great new features, there are new AI packages for React Native to talk about and meanwhile Apple lost an important lawsuit that allows developers to make 30% more money with their apps!Also in this episode:- Why sleep recovery is critical for everyone- Next Galaxies Mission- New Galaxies Tools & Apps

React Compiler reached release candidate, LegendList v1 is finally released and Evan Bacon shares React Native performance tips - meanwhile Simon questions his existence and whether React Native was the right choice after allAlso in this episode:- How I use Convex and ElevenLabs to build a Captions clone- Why are you not using AI?- My vacation in Copenhagen- New App sales and motivation- Galaxies.dev merch

The Expo SDK 53 Beta was released, FlashList v2 is a complete rewrite and is React Native actually popular? I dive into the latest news from the React Native community, and share updates on the projects I'm working on.Also in this episode:- How I use Convex and ElevenLabs to build a Captions clone- Why are you not using AI?- My vacation in Copenhagen- New App sales and motivation- Galaxies.dev merch

What's coming with Expo SDK 53? I dive into the latest news, trends and upcoming features of Expo and React Native, and share updates on the projects I'm working on.Also in this episode:- How RevenueCat Paywalls make my life better- I talked with Google- "Is this sponsored by Expo?"- AI Image Trends

We're in a season of disruption—political shifts, evolving policies, contracting delays, and social tensions are impacting how business gets done, especially in the federal space. If you're a small business owner or leader trying to make sense of how to stay relevant—or just stay open—you're not alone.In this episode, we're unpacking how to navigate the high-stakes environment of public sector contracting when the rules seem to keep changing. We'll explore how policy, politics, and procurement slowdowns intersect with real-world business survival.Then, we'll shift gears and talk about tangible strategies to pivot smartly—without losing your footing. Whether you're repositioning your offers, realigning with a new customer, or expanding to commercial markets, this conversation is your guide to pivoting with power, not panic.Guest Bio:Shaun Edens founded Lucky Rabbit in 2020 and has since led its growth into a trusted digital modernization partner for agencies like USCIS, OPM, CMS, GSA, and ED, as well as commercial clients like CrabPlace.com. With a background in senior roles at firms including CTEC, TechFlow, Enlightened, and Booz Allen Hamilton, he brings deep expertise in agile transformation, cloud migration, DevSecOps, and enterprise architecture.Shaun holds an MBA from the University of Illinois and a B.S. in Computer Science from Morehouse College. He's certified in SAFe, Scrum, Product Ownership, and AWS, and skilled in tools like ReactJS, Go, Python, and CI/CD pipelines. Focused on innovation and transparency, Shaun continues to lead Lucky Rabbit in delivering human-centered, secure digital solutions that drive real impact.Call(s) to Action:Help spread the word about Unveiled: GovCon Stories: https://shows.acast.com/unveiled-govcon-storiesDo you want to be a guest or recommend a topic that you would like to learn or hear about on the podcast? Let us know through our guest feedback and registration form.Links:Lucky RabbitLucky Rabbit BlueTechFollow Lucky Rabbit on LinkedInSponsors:The views and opinions expressed in this podcast are solely those of the hosts and guests, and do not reflect the views or endorsements of our sponsors.Withum – Diamond Sponsor!Withum is a forward-thinking, technology-driven advisory and accounting firm, helping clients to be in a position of strength in today's complex business environment. Go to Withum's website to learn more about how they can help your business! Hosted on Acast. See acast.com/privacy for more information.

I'm changing the format of RocketShip! Learn all about why and what changes, the new times and topics we will talk about. This podcast will continue to be primarily about React Native, but also about shipping great apps, using AI and news for mobile devs!Also in this episode: - My latest app projects - My first experience with the Vercel AI SDK in Expo apps- Personal branding stories from Simon- Behind the scenes of a creator.

Send a text and I may answer it on next episode (I cannot reply from this service

In this conversation, Simon Grimm and Matt Palmer discuss the capabilities and evolution of Replit, a platform that allows developers to quickly turn ideas into applications using AI tools. They explore the features of Replit, including its ability to create full stack applications, the integration of AI, and the unique advantages it offers compared to other development tools. The discussion also touches on the possibilities and limitations of using Replit for various types of projects. In this conversation, Simon and Matt discuss the challenges of managing Python environments and the advantages of using Replit for development. They explore how developers can integrate various tools into their workflows, the benefits of building with AI for rapid prototyping, and the importance of effective prompt engineering. The discussion also touches on the future collaboration between Replit and Expo, highlighting the evolving landscape of software development.Learn React Native - https://galaxies.devMatt PalmerMatt leads developer relations and product marketing at Replit, creating everything from tutorials to technical content. He got his start in data, working as a product analyst at AllTrails before moving to data engineering and eventually DevRel. He's worked on content with companies like LinkedIn, O'Reilly Media, xAI and Y Combinator. Outside of work, you can find him lifting weights or exploring the outdoors. Matt currently lives in San Francisco, but hails from Asheville, North Carolina.https://x.com/mattppalhttps://youtube.com/@mattpalmerhttps://www.linkedin.com/in/matt-palmer/https://mattpalmer.io/LinksReplit: https://replit.com/Replit X: https://x.com/replitReplit YouTube: https://www.youtube.com/@replitReplit Expo / React Native template: https://replit.com/@replit/ExpoReplit Sign-up:  https://replit.comExpo tutorial: https://www.youtube.com/playlist?list=PLto9KpJAqHMRuHwQ9OUjkVgZ69efpvslMExpo Blog: https://expo.dev/blog/from-idea-to-app-with-replit-and-expoTakeawaysReplit allows developers to create applications quickly and efficiently.AI integration in Replit enhances the development process.The platform supports multiple programming languages, primarily JavaScript and Python.Replit's workspace is designed for ease of use, requiring no installations.Users can deploy applications with a single click.Replit is evolving rapidly with advancements in AI technology.The platform is suitable for both beginners and experienced developers.Replit's unique features set it apart from other development tools.The community around Replit is growing, with increasing interest and usage.Building complex applications still requires significant effort and planning.  Python environments can be cumbersome for developers.Replit excels in managing single directory projects.AI can significantly speed up the prototyping process.Disposable software allows for quick iterations and testing.Effective prompt engineering can enhance AI outputs.Developers should focus on minimum viable prompts for efficiency.Replit's integration with Expo is a promising development.AI tools can help in learning and understanding code better.Collaboration between tools can streamline the development process.Keeping up with new tools and technologies is essential for developers.

In this episode, Simon and Beto discuss the latest findings from the State of React Native survey, highlighting trends in developer backgrounds, platform usage, income levels, and the evolving landscape of libraries and tools in the React Native ecosystem. They delve into the increasing popularity of local storage solutions, deep linking, and the rise of Zustand in state management, while also addressing the challenges and opportunities for solo developers in the mobile app space. In this conversation, Beto and Simon discuss the current state and future of React Native, focusing on various aspects such as Expo Router usage, styling trends, graphics and animations, component libraries, debugging tools, architecture adoption, build processes, AI in code generation, and community sentiment. They highlight the improvements in developer experience and the shift towards a more native approach in React Native development.Learn React Native - https://galaxies.devAlberto MoedanoBeto X: https://twitter.com/betomoedanoBeto YouTube: https://www.youtube.com/@codewithbetoCode with Beto Courses: https://codewithbeto.dev/LinksState of React Native Survey: https://results.stateofreactnative.com/en-US/TakeawaysThe State of React Native survey had over 3,000 participants, indicating growing interest.A significant number of React Native developers come from backend backgrounds.Solo developers can effectively use Expo and React Native to build apps.The trend towards local-first applications is gaining traction in the developer community.Deep linking is becoming increasingly important for app navigation.Zustand is rising in popularity as a state management solution.Inline styling remains a popular choice among developers.Expo is working on a new UI component library to enhance native app development.The future of data syncing and local storage solutions looks promising with new technologies. ExpoRouter is seeing increased usage and feedback is being actively incorporated.Styling in React Native is evolving, with inline styles gaining popularity due to AI tools.Graphics and animations are best handled with libraries like Reanimated and Skia.Component libraries are declining, indicating a shift towards more flexible styling solutions.Debugging tools are improving, with new options like Radon IDE and Atlas for Expo.The adoption of the new React Native architecture is growing, with many developers migrating successfully.EAS build is the preferred method for building applications, offering automation and a free tier.AI is becoming a significant part of the coding process, with many developers relying on it for code generation.Cross-platform frameworks are consolidating, with React Native and Flutter leading the way.The community sentiment around React Native is positive, with excitement for future developments.

In this conversation, Simon Grimm interviews Dohyun Kim, known as YourAverageTechBro, about his journey as an app developer and content creator. They discuss the challenges and successes in building apps, the importance of marketing, and the technologies used in app development, including React Native, Supabase, and AI tools. Dohyun shares insights on his most successful app, Montee, and the strategies behind its development and marketing, as well as the lessons learned from previous projects. In this conversation, Dohyun discusses the development of his app, Montee, focusing on the use of Next.js and Supabase for differentiation and backend management. He shares insights on API security, handling costs, and user management strategies. The importance of action bias in development is emphasized, along with ideation and keyword research strategies. The discussion also covers social media marketing tactics and preferences between web and mobile app development.Learn React Native - https://galaxies.devDohyun KimYouTube: https://www.youtube.com/@YourAverageTechBroTikTok: https://www.tiktok.com/@youraveragetechbroInstagram: https://www.instagram.com/youraveragetechbroX: https://x.com/youravgtechbroLinksMontee: https://www.montee.aiPerfect Interview: https://www.perfectinterview.aiGemini: https://ai.google.dev/TakeawaysDohyun prefers using technologies that allow for rapid development and shipping.He believes in copying successful ideas rather than focusing on originality.Montee, his AI meeting recorder app, achieved $1,500 in monthly recurring revenue shortly after launch.Dohyun discusses the challenges of app growth and the impact of churn on revenue.He highlights the importance of effective marketing strategies for app success.Dohyun prefers Supabase over Firebase for its relational database capabilities and better documentation.He shares insights on the technology stack used for PerfectInterview.ai, including Next.js and Gemini.Dohyun believes that app growth is often a series of step functions rather than exponential growth. Copy first and differentiate second is a key strategy.API keys should never be exposed in client-side code.User requests should always be traceable to prevent abuse.Action bias is crucial for shipping apps.Keyword research is not the only way to ideate apps.Social media marketing can drive app visibility.Instagram is currently more explosive for growth than TikTok.Web apps allow for faster updates and cash flow management.Developers should focus on building value-adding features.It's important to distinguish between fun projects and income-generating apps.

In this episode of Rocket Ship, Simon Grimm interviews Jack Herrington, a prominent figure in the React Native and Next.js communities. They discuss the challenges and changes in the React Native ecosystem, and the exciting developments around Module Federation and React Server Components (RSCs). Jack shares his experiences with React Native, the benefits of using Expo, and the performance gains associated with RSCs. The conversation also touches on the skepticism surrounding new technologies and the gradual adoption within the industry. In this conversation, Simon and Jack discuss the evolving landscape of React Server Components (RSCs), the impact of AI on app customization, and the rise of AI-driven development tools. They explore the integration of ShadCN, the future of universal apps, and compare RSCs with other frameworks like Svelte and Solid. The discussion highlights the challenges and innovations in the development community, particularly in relation to state management and the potential for AI to transform user experiences. They also delve into the ongoing debate between React Native and Flutter, highlight new features in React 19, and explore the potential of building custom Chrome extensions.Learn React Native - https://galaxies.devJack HerringtonX: https://x.com/jherrYouTube: https://www.youtube.com/@jherrGithub: https://github.com/jherrLinksFrontend Fire Podcast: https://front-end-fire.com/Pro Next.js Course: https://www.pronextjs.dev/Zephyr: https://www.zephyr-cloud.io/TakeawaysModule Federation allows for remote module updates without app store submissions.RSCs can improve performance by reducing client-side rendering time.The adoption of RSCs in the industry is slow due to existing codebases and frameworks.Jack's journey with React Native has been cyclical, returning to it multiple times.Performance gains with RSCs can be significant, especially on slower devices.Skepticism exists around new technologies like RSCs, impacting their adoption.Incremental adoption paths for frameworks can ease transitions for large companies. RSCs are still in development and face challenges.AI can significantly enhance app customization for users.Cursor is a popular AI-driven development tool that many developers prefer.ShadCN offers exciting possibilities for UI infrastructure.The concept of universal apps is becoming more feasible.The development landscape is shifting towards AI integration.Frameworks like Quick handle hydration differently than React.Solid and Svelte have similar functionalities to RSCs.AI models require extensive code examples for effective training.Zustand is gaining popularity in state management. Zustand has gained popularity as a state management library.Atomic state management allows for automatic updates based on dependencies.Choosing the right state management tool depends on the application's needs.React 19 introduces significant changes, especially with RSCs.Building custom Chrome extensions can enhance productivity and provide unique solutions.The debate between React Native and Flutter continues with no clear winner.Using the simplest state management solution is often the best approach.Understanding the context of your application is crucial for state management decisions.

In this episode, Simon Grimm welcomes Evan Bacon, the manager of DevTools at Expo, to discuss the latest developments in Expo, including the Expo Router, Expo Web, and the new React Server Components. Evan shares insights on the adoption of Expo Router, the future of Expo Web, and the exciting potential of DOM components. The conversation highlights the challenges and innovations in building universal apps and the importance of making app development accessible to all. In this conversation, Simon and Evan Bacon delve into the evolving landscape of app development with a focus on Expo, React Native, and the introduction of new technologies like RSC and EAS hosting. They discuss the challenges developers face with App Store reviews, the skepticism surrounding new features, and the future of server components. The conversation also highlights the potential of Expo targets for Apple and the exciting possibilities of building widgets and live activities. As they look ahead, they express optimism about the advancements in Expo and the broader React Native ecosystem.Learn React Native - https://galaxies.devEvan BaconTwitter: https://twitter.com/BaconbrixGithub: https://github.com/evanbaconBlog: https://evanbacon.dev/LinksRSC Code Example App: https://github.com/EvanBacon/expo-rsc-moviesExpo RSC: https://docs.expo.dev/guides/server-components/EAS Hosting: https://expo.dev/easTakeawaysExpo Router has been well received in the React Native community.The goal of Expo Router is to enable server-driven UI for developers.Expo Web has improved significantly with features like tree shaking and API routes..Expo Router version 4 is set to finalize the core features of the router.Expo Web is being actively used in new projects at Expo.DOM components allow for easier migration from web to native apps.React Server Components are currently in developer preview, with exciting potential.Skepticism towards new technologies is common but can change over time.RSC allows for running JavaScript not currently on the client.OTA updates are useful for caching and background fetching.EAS hosting provides a flexible solution for deploying apps.Expo targets for Apple enable the creation of various extensions.Widgets can communicate with apps via NSUser defaults.Real-time updates in widgets require clever workarounds.Expo's future includes more components and improved UI design.The integration of AI tools will enhance the development experience.

In this conversation, Simon Grimm interviews Ben Awad, a successful YouTuber and co-founder of the app Voidpet. They discuss Ben's journey from content creation to app development, the challenges and successes he faced, and the technical aspects of building his applications. The conversation also touches on the importance of user experience, monetization strategies, and the evolution of Ben's career in the tech industry. In this conversation, Ben Awad discusses his experiences and insights into React Native, game development, and the integration of AI tools in programming. He shares his journey from Android development to embracing React Native, the challenges of real-time gaming, and the evolution of the developer experience. Ben also touches on animation techniques in game development, his literary interests, and the future of his projects, including Voidpet and the Voidlog series.Learn React Native - https://galaxies.devBen AwadBen X: https://x.com/benawadBen YouTube: https://www.youtube.com/@bawadBen Github: https://github.com/benawadLinksVoidpet: https://voidpet.comVoidpet garden: https://voidpet.com/o/gardenHands of Greed book: https://handsofgreed.comTakeawaysBen Awad transitioned from YouTube content creation to app development.Voidpet gained popularity on TikTok before any code was written.He has learned from both successful and failed projects.The Voidpet app focuses on mental health themes.Ben's cooking app, Saffron, is still active and successful.He emphasizes the importance of user experience in app development.Ben uses a simple tech stack for his apps to avoid over-engineering.He believes that offline capabilities in apps are not always necessary.Ben prefers native styling in React Native over other styles.A time API is essential for validating timestamps in games.Ben's early experiences with Android development were frustrating.React Native's developer experience has significantly improved over the years.Real-time gaming in React Native presents unique challenges.Animation techniques are crucial for enhancing game visuals.Choosing React Native for game development was a strategic decision.AI tools have become integral to Ben's coding workflow.

In this solo episode, Simon shares the new Galaxies.dev Zero to Hero Mission and why now is the best time to learn React Native. From New Architecture to Debugging, Expo, and companies in the ecosystem, this podcast will reinforce your drive to build and ship awesome React Native apps in 2025!Join React Native Zero to Hero - https://galaxies.dev/missions/zero-to-hero

In this conversation, Simon Grimm interviews Samuel Newman, a developer at Bluesky, discussing his journey from university to app development, the intricacies of the Bluesky app and its underlying AT protocol, and the challenges and solutions encountered in enhancing user experience with React Native. They explore the role of Expo in app development, the importance of open-source contributions, and the future of Bluesky as it aims for significant user growth.Learn React Native - https://galaxies.devSamuel NewmanSamuel Bluesky: https://bsky.app/profile/samuel.bsky.teamSamuel X: https://x.com/mozziusSamuel personal: https://samuel.felixnewman.com/Samuel Github: https://github.com/mozziusLinksBluesky: https://bsky.app/AT Protocol: https://atproto.com/AT Proto Browser: https://atproto-browser.vercel.app/TakeawaysSamuel built a client for Bluesky before joining the team.Bluesky is a microblogging app built on the AT protocol.The AT protocol allows users to control their own data.The Bluesky app reached number one on the app store.Samuel's team faced numerous bugs in the app's development.They switched to a native bottom sheet for better performance.React Native requires a different mindset for developers.The AT protocol enables developers to build their own backends.Users genuinely own their data with the AD protocol.

Send us a textReactJS is the most popular JavaScript library. Love it or hate it, it's a safe bet to learn.Let's walk through how much JS you need to know before ReactJS, how to create your first component and what to do next.PS. I mentioned a video about working with APIs. You can watch it here.Shameless Plugs

In this conversation, Simon Grimm interviews Jamon Holmgren, co-founder of Infinite Red, discussing the evolution and advantages of React Native in mobile app development. They explore the early adoption of React Native, its comparison with Flutter, the job market for developers, and the importance of open source contributions in the tech industry. Jamon shares insights from his extensive coding experience and the strategic decisions that led Infinite Red to focus on React Native. They delve into the Ignite boilerplate for React Native development, the importance of choosing the right tech stack, and the utility of Reactotron as a developer tool.The discussion also touches on hiring trends in the React Native space, emphasizing the need for cultural fit and the unique hiring process at Infinite Red. In this conversation, Jamon and Simon discuss the importance of building a lasting company culture, essential skills for React Native developers, the significance of self-evaluation and continuous learning, effective networking and job searching strategies in tech, the future of React Native in the context of AI, and the trend towards universal applications while maintaining user experience.Learn React Native - https://galaxies.devJamon HolmgrenJamon X: https://x.com/jamonholmgrenJamon personal: https://jamon.dev/Jamon LinkedIn: https://www.linkedin.com/in/jamonholmgren/Jamon Bluesky: https://bsky.app/profile/jamon.devLinksInfinite Red: https://infinite.red/React Native Radio: https://reactnativeradio.com/Ignite: https://github.com/infinitered/igniteReactotron: https://github.com/infinitered/reactotronTakeawaysInfinite Red was founded through collaboration in open source.React Native was chosen for its cross-platform capabilities.React Native allows for significant code reuse, often exceeding expectations.The community around React Native is a major strength.Open source contributions can accelerate product development.Companies are increasingly investing in open source for strategic benefits.The job market favors React Native developers due to its widespread use.Ignite serves as a valuable resource for React Native developers.Ignite serves as a reliable boilerplate for React Native projects.Choosing the right tech stack can simplify development processes.Reactotron offers unique features that enhance the debugging experience.The UI of Reactotron needs improvement to appeal to developers.Hiring at Infinite Red focuses on cultural fit and seniority.Self-evaluation during the hiring process is crucial for accurate assessment.The job market for React Native developers is becoming more competitive.  Building a company culture that encourages long-term relationships is crucial.Investing in employees and understanding their needs fosters loyalty.React Native developers should focus on performance and state management skills.Self-evaluation helps identify areas for improvement and training needs.Networking is essential for job searching in tech.Active engagement on social media can enhance job prospects.AI will significantly impact the future of software development.Universal applications should prioritize user experience over uniformity.Convergence of tools is beneficial, but UI patterns must remain platform-specific.Continuous learning and adaptation are key to thriving in tech.

In this conversation, Simon Grimm interviews Kim Chouard, a developer and educator, about his journey in coding, the challenges of building a multiplatform music game using React Native, and the innovative app Odisei Play that aims to help users learn to play wind instruments. Kim shares insights on the creative aspects of coding, the evolution of React Native, and the technology stack behind Odisei Play, including audio handling and pitch recognition. The discussion highlights the importance of education, creativity, and community in the tech space. In this conversation, Kim Chouard discusses the evolving landscape of development tools, particularly focusing on AI tools and their implications for new developers. He shares insights on the Expo audio package and the challenges faced in audio synchronization within applications. The discussion also delves into the use of Skia for performance optimization in React Native applications, highlighting its capabilities and the need for better documentation. Finally, Kim emphasizes the importance of a web-first approach in React Native development, advocating for a unified community that leverages the strengths of both web and mobile development.Learn React Native - https://galaxies.devKim ChouardKim X: https://x.com/KimChouardKim personal: https://chouard.kim/Kim LinkedIn: https://www.linkedin.com/in/kimchouard/LinksOdisei Music's website (creator of Odisei Play): https://odiseimusic.com/Kim AppJS Talk: https://www.youtube.com/watch?v=PGvhniTxpu4&ab_channel=SoftwareMansionExpo AV: https://docs.expo.dev/versions/latest/sdk/av/Chromatic: https://www.chromatic.com/Storybook: https://storybook.js.org/TakeawaysKim's mission is to leverage games for alternative education.Coding can be a creative process, not just technical.Building a music game requires precise timing and performance.React Native's rapid evolution presents both opportunities and challenges.Odisei Play aims to make learning wind instruments accessible and fun.The app combines elements of gamification and music education.Skia is crucial for the performance of the Odisei Play app.Bluetooth technology can be optimized for real-time music applications.AI tools like Cursor can enhance coding efficiency.Community support is vital for navigating the fast-paced tech landscape. AI tools can accelerate development but may lead to inconsistencies.Expo AV is the only production-ready audio library available now, although it has some limitationNew opportunities of more robust alternatives for audio handling are on the horizon (expo-audio, react-native audio, etc.)Audio synchronization remains a significant challenge in app development.Skia provides a powerful canvas for creating high-performance applications.The integration of web technologies can enhance React Native development.Community collaboration is essential for overcoming development hurdles.Real-time audio recognition is complex and requires advanced algorithms.A web-first approach can simplify the development process for React Native.The React Native community is passionate and supportive.Future advancements in 3D and game development are on the horizon.

News includes a neat trick we learned that setup-beam can do for GitHub actions by reading a project's .tool-versions file, Wojtek's insight on reducing SDK API surfaces, Ash's support for UUIDv7, the introduction of the highly customizable Backpex admin panel, a new LiveView component library called SaladUI and its unique ReactJS component conversion feature, Jose Valim's technique of using AI for testing function names, and more! Show Notes online - http://podcast.thinkingelixir.com/209 (http://podcast.thinkingelixir.com/209) Elixir Community News - https://x.com/flo_arens/status/1805255159460532602 (https://x.com/flo_arens/status/1805255159460532602?utm_source=thinkingelixir&utm_medium=shownotes) – TIL setup-beam GitHub action can read asdf's .tool-versions file and parse the OTP and Elixir version out of it. - https://github.com/erlef/setup-beam (https://github.com/erlef/setup-beam?utm_source=thinkingelixir&utm_medium=shownotes) – The setup-beam GitHub action project. - https://github.com/erlef/setup-beam?tab=readme-ov-file#version-file (https://github.com/erlef/setup-beam?tab=readme-ov-file#version-file?utm_source=thinkingelixir&utm_medium=shownotes) – Link to README section about the version file support in setup-beam. - https://dashbit.co/blog/sdks-with-req-stripe (https://dashbit.co/blog/sdks-with-req-stripe?utm_source=thinkingelixir&utm_medium=shownotes) – Blog post by Wojtek on reducing the surface of SDK APIs by focusing on data, not functions. - https://x.com/ZachSDaniel1/status/1805002425738334372 (https://x.com/ZachSDaniel1/status/1805002425738334372?utm_source=thinkingelixir&utm_medium=shownotes) – Ash now supports UUIDv7, a Time-Sortable Identifier for modern databases. - https://github.com/ash-project/ash/pull/1253 (https://github.com/ash-project/ash/pull/1253?utm_source=thinkingelixir&utm_medium=shownotes) – GitHub pull request for Ash's support of UUIDv7. - https://uuid7.com/ (https://uuid7.com/?utm_source=thinkingelixir&utm_medium=shownotes) – Information about UUID7 as a Time-Sortable Identifier. - https://elixirforum.com/t/backpex-a-highly-customizable-admin-panel-for-phoenix-liveview-applications/64314 (https://elixirforum.com/t/backpex-a-highly-customizable-admin-panel-for-phoenix-liveview-applications/64314?utm_source=thinkingelixir&utm_medium=shownotes) – Introduction to Backpex, a new admin backend library for Phoenix LiveView applications. - https://github.com/naymspace/backpex (https://github.com/naymspace/backpex?utm_source=thinkingelixir&utm_medium=shownotes) – GitHub repository for Backpex, a customizable administration panel for Phoenix LiveView applications. - https://github.com/bluzky/salad_ui (https://github.com/bluzky/salad_ui?utm_source=thinkingelixir&utm_medium=shownotes) – SaladUI, a Tailwind LiveView UI toolkit that includes a unique feature to convert ReactJS components. - https://salad-storybook.fly.dev/welcome (https://salad-storybook.fly.dev/welcome?utm_source=thinkingelixir&utm_medium=shownotes) – Storybook for SaladUI to explore components. - https://ui.shadcn.com/ (https://ui.shadcn.com/?utm_source=thinkingelixir&utm_medium=shownotes) – React Shad/cn UI component framework storybook page. - https://salad-storybook.fly.dev/examples/convert_shadui (https://salad-storybook.fly.dev/examples/convert_shadui?utm_source=thinkingelixir&utm_medium=shownotes) – Example of converting a ReactJS component to SaladUI. - https://github.com/codedge-llc/accessible (https://github.com/codedge-llc/accessible?utm_source=thinkingelixir&utm_medium=shownotes) – Accessible, a package to add Access behavior support to Elixir structs. - https://paraxial.io/blog/owasp-top-ten (https://paraxial.io/blog/owasp-top-ten?utm_source=thinkingelixir&utm_medium=shownotes) – Blog post on how the OWASP Top 10 applies to Elixir and Phoenix applications. - https://owasp.org/www-project-top-ten/ (https://owasp.org/www-project-top-ten/?utm_source=thinkingelixir&utm_medium=shownotes) – The OWASP Top 10, a standard awareness document for developers and web application security. - https://x.com/josevalim/status/1804117870764339546 (https://x.com/josevalim/status/1804117870764339546?utm_source=thinkingelixir&utm_medium=shownotes) – José Valim's technique of using AI to help review or determine function names in APIs. - https://fly.io/phoenix-files/using-ai-to-boost-accessibility-and-seo/ (https://fly.io/phoenix-files/using-ai-to-boost-accessibility-and-seo/?utm_source=thinkingelixir&utm_medium=shownotes) – Article on using AI to boost image accessibility and SEO, demonstrating working with OpenAI and Anthropic using Elixir. - https://2024.elixirconf.com/ (https://2024.elixirconf.com/?utm_source=thinkingelixir&utm_medium=shownotes) – ElixirConf 2024 details, taking place from August 28-30 with various speakers and talks focused on Elixir. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern)

Building web UIs in Python has always been in interesting proposition. On one end, we have a the full web design story with artisanal HTML and CSS. On another end there are several Python platforms that aim to the bring RAD, rapid app development, style of building with Python. Those can be great, and I've covered a couple of them, but they usually reach a limit on what they can do or how they integrate with the larger web ecosystem. On this episode, we have Samuel Colvin to share his latest exciting project FastUI. With FastUI, you build responsive web applications using React without writing a single line of JavaScript, or touching npm. Yet designers and other tools can focus on React front-ends for a professional SPA like app experience. Episode sponsors bright data Sentry Error Monitoring, Code TALKPYTHON Talk Python Courses Links from the show Samuel on Mastodon: fosstodon.org Samuel on X: x.com FastUI: github.com FastUI Demos: fastui-demo.onrender.com FastAPI: fastapi.tiangolo.com Pydantic: pydantic.dev How Did REST Come To Mean The Opposite of REST Article: htmx.org Tailwind UI: tailwindui.com Dropbase: dropbase.io Anvil: anvil.works Flutter code example: github.com ReactJS code example: github.com Watch this episode on YouTube: youtube.com Episode transcripts: talkpython.fm --- Stay in touch with us --- Subscribe to us on YouTube: youtube.com Follow Talk Python on Mastodon: talkpython Follow Michael on Mastodon: mkennedy