WEBVTT 00:00:00.000 --> 00:00:03.299 Imagine crafting a fully functional mobile game 00:00:03.299 --> 00:00:06.660 complete with intricate enemy patterns, power 00:00:06.660 --> 00:00:09.480 -ups, all that stuff. Yeah, or maybe like a really 00:00:09.480 --> 00:00:11.619 robust note -taking app, one that syncs across 00:00:11.619 --> 00:00:14.179 all your devices. But not in months, not even 00:00:14.179 --> 00:00:16.399 weeks. Oh, wait. We're talking minutes, like 00:00:16.399 --> 00:00:19.120 maybe 14 minutes from just a simple text prompt. 00:00:19.359 --> 00:00:21.899 Today, we're taking a deep dive into Rourke AI, 00:00:22.199 --> 00:00:25.390 and it's powered by, well... The much anticipated 00:00:25.390 --> 00:00:28.649 GPT -5. Yep. Welcome to the Deep Dive. Today, 00:00:28.730 --> 00:00:31.570 we're really unpacking something pretty intriguing 00:00:31.570 --> 00:00:35.850 here. RORC AI. It promises to genuinely democratize 00:00:35.850 --> 00:00:38.789 mobile app development, making creation accessible 00:00:38.789 --> 00:00:41.310 in a way we really haven't seen before. That's 00:00:41.310 --> 00:00:43.350 right. It's like having a fast track pass, you 00:00:43.350 --> 00:00:45.469 know, for your app idea straight onto your phone. 00:00:45.530 --> 00:00:48.250 Forget Xcode. Forget all those complicated setups. 00:00:48.390 --> 00:00:51.310 It's just pure AI generation right there in your 00:00:51.310 --> 00:00:54.109 browser. Pretty wild. So we'll start by looking 00:00:54.109 --> 00:00:57.070 at what's traditionally been the mobile development 00:00:57.070 --> 00:01:00.149 nightmare. Oh, yeah. Then explore how RORC offers 00:01:00.149 --> 00:01:03.490 a truly mobile -first solution. And then, crucially, 00:01:03.609 --> 00:01:06.609 we'll put it through its paces. Some real -world 00:01:06.609 --> 00:01:09.209 tests. Absolutely. We've got two big challenges 00:01:09.209 --> 00:01:12.030 lined up for it. First, building a playable 2D 00:01:12.030 --> 00:01:14.430 space shooter. Okay. And then a practical, you 00:01:14.430 --> 00:01:17.069 know, data -driven note -taking app. And we'll 00:01:17.069 --> 00:01:19.989 also cover the essentials, the pricing, where 00:01:19.989 --> 00:01:24.230 it really shines, its current limits, and what's 00:01:24.230 --> 00:01:25.750 actually going on under the hood, technically 00:01:25.750 --> 00:01:27.750 speaking. And ultimately, we'll be asking the 00:01:27.750 --> 00:01:30.530 big question, is this really the future of app 00:01:30.530 --> 00:01:32.950 creation? Let's maybe start by considering the 00:01:32.950 --> 00:01:35.209 historical landscape. For creators who aren't 00:01:35.209 --> 00:01:36.569 technical, what's been the biggest headache? 00:01:36.730 --> 00:01:39.290 The wall they hit before they even start. Oh, 00:01:39.310 --> 00:01:41.689 it's really that initial setup and just the sheer 00:01:41.689 --> 00:01:44.370 complexity of testing. Right. You spend way more 00:01:44.370 --> 00:01:46.329 time fighting with the tools and configurations 00:01:46.329 --> 00:01:49.329 than, you know, actually building anything cool. 00:01:49.689 --> 00:01:51.489 So you have this great idea, but you're stuck. 00:01:51.810 --> 00:01:53.909 Exactly. Locked out because you can't even get 00:01:53.909 --> 00:01:57.349 your development environment to compile a basic 00:01:57.349 --> 00:01:59.890 hello world or test it on your actual phone. 00:02:00.010 --> 00:02:02.700 It's crazy. Right. We're talking about grappling 00:02:02.700 --> 00:02:05.680 with something like Apple's Xcode. Ugh, Xcode. 00:02:05.879 --> 00:02:08.139 Which is this massive, intricate, integrated 00:02:08.139 --> 00:02:11.159 development environment, an ICE. Yep, I -D -E. 00:02:11.280 --> 00:02:13.719 And you often need multiple computers, seriously, 00:02:14.039 --> 00:02:16.939 just to compile a basic starter project sometimes. 00:02:17.300 --> 00:02:19.020 And then there's the friction of testing, getting 00:02:19.020 --> 00:02:21.400 the app from the computer to the phone. Oh, it's 00:02:21.400 --> 00:02:24.270 often like... 10, 15 manual steps. It's a total 00:02:24.270 --> 00:02:26.389 black box problem. You're basically coding blind, 00:02:26.669 --> 00:02:28.990 you know. No live preview on the actual device. 00:02:29.189 --> 00:02:32.469 None. Which makes AI coding for mobile traditionally 00:02:32.469 --> 00:02:35.810 feel super clunky, just inaccessible for most 00:02:35.810 --> 00:02:38.310 people. So you're saying the sheer setup and 00:02:38.310 --> 00:02:41.449 testing complexity that's been the biggest barrier 00:02:41.449 --> 00:02:43.949 locked people out. Absolutely. That's been the 00:02:43.949 --> 00:02:46.909 showstopper. But Roark, thankfully, just flips 00:02:46.909 --> 00:02:49.289 that whole broken paradigm right on its head. 00:02:49.409 --> 00:02:52.229 How so? Well, it's inherently mobile first. And 00:02:52.229 --> 00:02:55.530 importantly, it's powered by GPT -5. The latest 00:02:55.530 --> 00:02:58.949 advanced AI model. Exactly. Known for its sophisticated 00:02:58.949 --> 00:03:01.750 reasoning, multimodal code generation, all that 00:03:01.750 --> 00:03:04.509 good stuff. And its core philosophy seems to 00:03:04.509 --> 00:03:07.349 be about speed and accessibility. Yeah. Taking 00:03:07.349 --> 00:03:10.370 an idea to a testable app in minutes. That's 00:03:10.370 --> 00:03:13.840 the key. Speed. accessibility it's a huge shift 00:03:13.840 --> 00:03:16.300 so how does it work practically it's pretty simple 00:03:16.300 --> 00:03:18.719 actually you get a single prompt interface right 00:03:18.719 --> 00:03:20.860 in your browser just describe the app you want 00:03:20.860 --> 00:03:24.500 okay then for instant mobile testing this is 00:03:24.500 --> 00:03:27.060 the cool part you just scan a qr code with your 00:03:27.060 --> 00:03:31.400 phone wow beat so no complex ide needed at all 00:03:31.400 --> 00:03:34.400 nope everything happens right there in the browser 00:03:34.400 --> 00:03:36.860 and it's cross -platform truly cross -platform 00:03:36.860 --> 00:03:39.680 one build works seamlessly on ios android and 00:03:39.680 --> 00:03:42.370 the web and updates are live Real time. Yeah, 00:03:42.509 --> 00:03:44.389 which is remarkable. You make a change in the 00:03:44.389 --> 00:03:46.729 prompt, tweet something. And you see it on your 00:03:46.729 --> 00:03:48.789 phone moments later. Almost instantly, yeah. 00:03:48.990 --> 00:03:52.129 So this mobile first approach, it just bypasses 00:03:52.129 --> 00:03:54.310 all that setup hassle. Completely. You jump straight 00:03:54.310 --> 00:03:56.870 to testing your actual idea. Okay, let's dive 00:03:56.870 --> 00:03:59.270 into that first real test then. Building a playable 00:03:59.270 --> 00:04:02.870 2D space shooter from scratch. Right. And the 00:04:02.870 --> 00:04:05.650 strategy here was what we called creative freedom. 00:04:05.990 --> 00:04:09.050 Meaning the prompt wasn't super prescriptive. 00:04:09.449 --> 00:04:12.750 Not micromanaging. Exactly. It gave the AI a 00:04:12.750 --> 00:04:16.470 clear core function, a 2D side -scrolling space 00:04:16.470 --> 00:04:19.449 shooter, fast -paced arcade action, that kind 00:04:19.449 --> 00:04:21.810 of thing. But left room for style. Yeah, room 00:04:21.810 --> 00:04:24.209 for interpretation, like asking for a pulsing 00:04:24.209 --> 00:04:26.089 soundtrack vibe. It wasn't just about function. 00:04:26.129 --> 00:04:28.509 It was about the feel. Okay. And how did it go, 00:04:28.610 --> 00:04:32.100 watching it build? Honestly? Genuinely impressive. 00:04:32.319 --> 00:04:34.720 Watching Rourke build this game, Cosmic Defender. 00:04:34.759 --> 00:04:37.540 Cosmic Defender, okay. Yeah. You see the AI's 00:04:37.540 --> 00:04:40.240 thought process, like its plan, on one side of 00:04:40.240 --> 00:04:43.000 the screen. And then there's a live mobile preview 00:04:43.000 --> 00:04:45.180 on the other side showing the app just coming 00:04:45.180 --> 00:04:47.560 to life piece by piece. What kind of features 00:04:47.560 --> 00:04:49.829 did it manage to include? Well, it had this really 00:04:49.829 --> 00:04:52.670 vibrant neon aesthetic, kind of reminded me of 00:04:52.670 --> 00:04:55.470 Geometry Wars. Oh, cool. An animated Starfield 00:04:55.470 --> 00:04:58.569 background, multiple complex enemy types, not 00:04:58.569 --> 00:05:00.769 just simple blobs power -ups. And the controls. 00:05:01.050 --> 00:05:03.350 Touch controls can be tricky. Flawless touch 00:05:03.350 --> 00:05:06.490 controls right out of the box. Seriously, these 00:05:06.490 --> 00:05:08.670 features would normally take a human dev hours, 00:05:08.709 --> 00:05:11.490 maybe days. But here's where it gets really interesting. 00:05:11.810 --> 00:05:14.949 The magic moment, we called it. Okay. From the 00:05:14.949 --> 00:05:17.230 browser to having the game running on your phone. 00:05:17.790 --> 00:05:20.189 About five seconds. Five seconds? How? You scan 00:05:20.189 --> 00:05:24.149 a QR code. You install this free app called ExpoGo 00:05:24.149 --> 00:05:27.449 just once. Right. And then boom, the game instantly 00:05:27.449 --> 00:05:30.430 launches. Full screen. Feels totally native. 00:05:30.769 --> 00:05:34.509 Whoa! Yeah! Whoa! Imagine the possibilities. 00:05:34.649 --> 00:05:37.610 A tool like this for like a billion creators 00:05:37.610 --> 00:05:40.490 out there. It's a game changer. That instant 00:05:40.490 --> 00:05:43.389 transfer, that seamless launch. Yeah. It really 00:05:43.389 --> 00:05:45.629 does shift things. Totally. And then there's 00:05:45.629 --> 00:05:48.230 the patch power. Patch power. Yeah. We gave it 00:05:48.230 --> 00:05:50.750 a simple prompt like, make the enemy ships look 00:05:50.750 --> 00:05:53.430 like actual spaceships, not just geometric shapes. 00:05:53.629 --> 00:05:55.910 Yeah. It updated the live game almost instantly. 00:05:56.110 --> 00:05:58.029 The visuals changed right there on the phone. 00:05:58.129 --> 00:06:01.250 So this rapid iteration, it just transforms the 00:06:01.250 --> 00:06:03.670 creative feedback loop. Fundamentally, ideas 00:06:03.670 --> 00:06:05.529 become testable realities almost immediately. 00:06:05.829 --> 00:06:08.250 Refinement gets super fast. Okay. So games are 00:06:08.250 --> 00:06:11.360 one thing. Fun, visual. But what about more practical 00:06:11.360 --> 00:06:14.220 apps, data -driven stuff? Right. That was the 00:06:14.220 --> 00:06:17.300 next test, building a fully functional note -taking 00:06:17.300 --> 00:06:20.120 app. And this prompt pushed the AI a bit harder. 00:06:20.240 --> 00:06:22.319 Yeah, definitely. We push it on data persistence, 00:06:22.600 --> 00:06:24.720 making sure notes actually save. Crucial for 00:06:24.720 --> 00:06:28.160 a note app. Totally. And UI complexity, different 00:06:28.160 --> 00:06:31.279 input types like typing and freehand drawing. 00:06:31.379 --> 00:06:34.339 Drawing too, okay. Even asked for search, themes, 00:06:34.759 --> 00:06:38.290 folders. The works. And the results. Surprisingly 00:06:38.290 --> 00:06:41.149 comprehensive, really. A clean editor, seamless 00:06:41.149 --> 00:06:44.129 autosave that just worked, real -time search, 00:06:44.610 --> 00:06:48.250 light and dark themes. Wow. It felt remarkably 00:06:48.250 --> 00:06:50.889 native on the phone, like genuinely indistinguishable 00:06:50.889 --> 00:06:53.410 from a professionally developed app. I'll admit, 00:06:53.490 --> 00:06:55.149 this is where I still wrestle with prompt drift 00:06:55.149 --> 00:06:57.870 myself sometimes, you know, getting the AI to 00:06:57.870 --> 00:07:00.490 stick to the plan precisely. But Rourke did great, 00:07:00.649 --> 00:07:02.610 mostly. Mostly. Okay, here comes the reality 00:07:02.610 --> 00:07:06.100 check. Yeah. While maybe 95 % of the app worked 00:07:06.100 --> 00:07:08.959 flawlessly, there was one point of failure. Drawing 00:07:08.959 --> 00:07:11.360 feature. Yep, the freehand drawing feature. It 00:07:11.360 --> 00:07:13.680 just didn't function correctly on the mobile 00:07:13.680 --> 00:07:15.939 device itself. Looked okay in the web preview, 00:07:16.060 --> 00:07:18.680 but not on the phone. Ah. So that highlights 00:07:18.680 --> 00:07:21.120 something important. It does. Highly specialized 00:07:21.120 --> 00:07:24.199 or like really complex touch interactions. They 00:07:24.199 --> 00:07:26.259 might still need a human touch to really perfect. 00:07:26.560 --> 00:07:29.699 So it's powerful, but not quite magical everywhere 00:07:29.699 --> 00:07:32.259 yet. Not quite magical everywhere. Not yet anyway. 00:07:32.420 --> 00:07:35.220 Powerful. Yes. So what this specific limitation 00:07:35.220 --> 00:07:39.160 tells us is that these niche complex UI interactions 00:07:39.160 --> 00:07:44.060 are still a frontier for autonomous AI. Even 00:07:44.060 --> 00:07:47.160 GPT -5. Exactly. That's the current edge. Okay. 00:07:47.199 --> 00:07:49.079 So you've built an app, maybe two apps. That's 00:07:49.079 --> 00:07:51.620 fantastic. But what about getting it out there 00:07:51.620 --> 00:07:55.100 into users' hands? Rourke also acts as a kind 00:07:55.100 --> 00:07:57.600 of launchpad, right? Exactly. Yeah, a launchpad. 00:07:57.980 --> 00:08:01.019 Beta testing is incredibly easy. How easy? You 00:08:01.019 --> 00:08:02.879 can generate a private link, send it to friends, 00:08:03.019 --> 00:08:04.879 or you could even tweet a public link if you 00:08:04.879 --> 00:08:07.220 wanted broader feedback. It's a genuine friends 00:08:07.220 --> 00:08:10.000 and family test flight, but super simple. Okay. 00:08:10.329 --> 00:08:11.990 And then getting into the actual app stores, 00:08:12.170 --> 00:08:16.230 Apple's portal is famously complex. Oh, notoriously 00:08:16.230 --> 00:08:18.550 so. But Rourke has what they call the easy button 00:08:18.550 --> 00:08:21.310 for app store submission. An easy button. Sounds 00:08:21.310 --> 00:08:24.149 good. Yeah. Instead of wrestling with Apple's 00:08:24.149 --> 00:08:26.769 confusing developer portal, Rourke gives you 00:08:26.769 --> 00:08:29.870 a simple guided form. You fill it out. And it 00:08:29.870 --> 00:08:32.450 handles the back end complexity. It manages that 00:08:32.450 --> 00:08:35.250 entire complex submission process in the background 00:08:35.250 --> 00:08:38.269 for you. Uploading builds, certificates, provisioning 00:08:38.269 --> 00:08:41.720 profiles. All that stuff. That really does make 00:08:41.720 --> 00:08:44.419 publishing accessible, especially for non -technical 00:08:44.419 --> 00:08:46.419 folks. It totally levels the playing field. And 00:08:46.419 --> 00:08:49.340 what about the cost, the investment? Works pricing 00:08:49.340 --> 00:08:51.639 seems pretty simple and transparent. Yeah, they 00:08:51.639 --> 00:08:53.720 have a starter plan. It's $20 a month, gets you 00:08:53.720 --> 00:08:56.000 100 messages. Seems perfect for your first few 00:08:56.000 --> 00:08:59.139 apps or just experiment. 100 messages. Okay. 00:08:59.240 --> 00:09:01.279 Then there's the professional plan that's $50 00:09:01.279 --> 00:09:04.980 a month for 250 messages. And that unlocks more 00:09:04.980 --> 00:09:07.120 advanced features too, like... github integration 00:09:07.120 --> 00:09:09.740 right github good but here's the usage reality 00:09:09.740 --> 00:09:11.940 check that really blew my mind oh yeah remember 00:09:11.940 --> 00:09:14.639 those two apps we built the space shooter game 00:09:14.639 --> 00:09:17.360 and the note taker yeah together they used only 00:09:17.360 --> 00:09:20.200 three messages three out of a hundred on the 00:09:20.200 --> 00:09:23.500 starter plan three that means the twenty dollar 00:09:23.500 --> 00:09:26.220 starter plan could realistically help you build 00:09:26.220 --> 00:09:30.299 like 30 or more distinct apps maybe even more 00:09:30.299 --> 00:09:33.340 depending on iterations wow That's incredible 00:09:33.340 --> 00:09:36.000 value. It's insane value. It truly de -risks 00:09:36.000 --> 00:09:38.659 creativity and exploration. You can try out lots 00:09:38.659 --> 00:09:41.100 of ideas without breaking the bank. So what you're 00:09:41.100 --> 00:09:44.460 pointing to is that this super low barrier to 00:09:44.460 --> 00:09:47.460 entry for both creation and publication, it just 00:09:47.460 --> 00:09:50.879 significantly boosts innovation by enabling rapid, 00:09:50.940 --> 00:09:53.620 cheap experimentation. Precisely. More ideas 00:09:53.620 --> 00:09:56.779 get tested. More cool stuff gets built. Sponsor. 00:09:57.240 --> 00:09:59.879 Welcome back to the Deep Dive. We've seen Roark 00:09:59.879 --> 00:10:02.279 build a couple of apps, handle deployment. Let's 00:10:02.279 --> 00:10:03.919 zoom out a bit. Where does it fit in the whole 00:10:03.919 --> 00:10:06.600 ecosystem of development tools? Yeah, good question. 00:10:06.720 --> 00:10:08.879 I kind of think of Roark as being like a specialized 00:10:08.879 --> 00:10:11.600 surgical instrument specifically for mobile development. 00:10:11.720 --> 00:10:13.639 Okay, surgical instrument. Compared to what? 00:10:13.759 --> 00:10:16.279 Compared to general AI coding assistants, which 00:10:16.279 --> 00:10:18.259 are maybe more like a Leatherman multi -tool. 00:10:18.899 --> 00:10:21.240 Versatile, but not specialized. Exactly. Leathermans 00:10:21.240 --> 00:10:23.080 are great, but you wouldn't use one for brain 00:10:23.080 --> 00:10:26.159 surgery, right? Roark is tailored for this one 00:10:26.159 --> 00:10:29.879 job. Getting mobile apps built fast. So Rourke 00:10:29.879 --> 00:10:33.080 really excels because it's mobile first. That 00:10:33.080 --> 00:10:35.879 simple QR code testing. Yep. Instant feedback. 00:10:36.120 --> 00:10:38.679 It's accessibility, especially for non -technical 00:10:38.679 --> 00:10:41.879 users. Crucial. And that true cross -platform 00:10:41.879 --> 00:10:45.080 functionality from one code base. Those seem 00:10:45.080 --> 00:10:47.240 like its core strengths. They absolutely are. 00:10:47.480 --> 00:10:51.360 But, like any tool, there are trade -offs. Of 00:10:51.360 --> 00:10:53.980 course. Such as? Well, it can sometimes be a 00:10:53.980 --> 00:10:56.399 bit slower than pure text -based AI assistance, 00:10:56.759 --> 00:10:59.320 especially when generating code for really complex 00:10:59.320 --> 00:11:01.940 features. We saw it struggle with that really 00:11:01.940 --> 00:11:04.080 complex drawing interaction. Right, the Node 00:11:04.080 --> 00:11:06.879 app. And it offers maybe less granular control 00:11:06.879 --> 00:11:09.580 over the underlying code structure compared to 00:11:09.580 --> 00:11:12.059 writing it all yourself or using a more general 00:11:12.059 --> 00:11:14.840 AI assistant. Plus, there's always some degree 00:11:14.840 --> 00:11:17.120 of platform lock -in with specialized tools. 00:11:17.399 --> 00:11:19.139 That makes sense. Yeah. But it does offer an 00:11:19.139 --> 00:11:20.850 advanced toolkit to kind of mitigate. some of 00:11:20.850 --> 00:11:23.490 that it does yeah which is smart the github integration 00:11:23.490 --> 00:11:26.350 is key that acts as your escape hatch escape 00:11:26.350 --> 00:11:29.049 hatch meaning meaning you own your code you can 00:11:29.049 --> 00:11:32.370 export it anytime take it off the platform customize 00:11:32.370 --> 00:11:34.909 it manually integrate it into other workflows 00:11:34.909 --> 00:11:38.610 you're not stuck that's important for trust and 00:11:38.610 --> 00:11:41.940 for sensitive info yeah Like API keys. For that, 00:11:42.039 --> 00:11:43.580 they have environment variables. That's like 00:11:43.580 --> 00:11:47.100 your secret vault. Okay. API keys, database credentials, 00:11:47.360 --> 00:11:49.500 stuff like that kept completely separate and 00:11:49.500 --> 00:11:52.200 secure from your main code base. Good practice. 00:11:52.519 --> 00:11:55.919 And finally, database connectivity. Yeah, that 00:11:55.919 --> 00:11:58.559 gives your app a persistent brain. A persistent 00:11:58.559 --> 00:12:00.840 brain. I like that. Right. It allows for essential 00:12:00.840 --> 00:12:03.879 features like user accounts, syncing data across 00:12:03.879 --> 00:12:07.159 devices, and building a genuinely scalable architecture 00:12:07.159 --> 00:12:09.899 if your app takes off. So that escape hatch, 00:12:10.080 --> 00:12:12.299 the GitHub integration, is actually pretty critical 00:12:12.299 --> 00:12:14.940 for the platform's long -term viability. It deals 00:12:14.940 --> 00:12:17.159 with those lock -in concerns. Absolutely. It 00:12:17.159 --> 00:12:19.820 ensures code ownership, builds trust, and makes 00:12:19.820 --> 00:12:22.159 it viable for more serious projects, too. Okay, 00:12:22.200 --> 00:12:24.480 so these demos, the game, and the Node app, they're 00:12:24.480 --> 00:12:26.379 just scratching the surface, really. Oh, totally. 00:12:26.500 --> 00:12:29.240 Just the beginning. Rourke unlocks a whole universe 00:12:29.240 --> 00:12:32.440 of potential applications, custom task managers 00:12:32.440 --> 00:12:35.419 for your team. Internal business tools, maybe 00:12:35.419 --> 00:12:39.240 simple CRMs, educational games for kids, even 00:12:39.240 --> 00:12:42.279 interactive art projects. The possibilities are 00:12:42.279 --> 00:12:44.960 huge. It's worth maybe touching on what's actually 00:12:44.960 --> 00:12:47.679 under the hood to understand why it works so 00:12:47.679 --> 00:12:49.480 well. Yeah, the tech stack is pretty interesting. 00:12:49.539 --> 00:12:51.779 It's like a holy trinity of tech. Holy trinity, 00:12:51.879 --> 00:12:55.149 okay. You've got GPT -5 as the brain. doing the 00:12:55.149 --> 00:12:57.110 reasoning, the code generation. Right. Then you 00:12:57.110 --> 00:12:59.830 have React Native. That's the skeleton. It's 00:12:59.830 --> 00:13:03.210 a super popular framework from Facebook meta 00:13:03.210 --> 00:13:05.769 now. For building cross -platform apps that feel 00:13:05.769 --> 00:13:08.809 native. Exactly. Write once, run on iOS and Android, 00:13:09.070 --> 00:13:11.700 feels like a real app. And the third part. Expo. 00:13:11.700 --> 00:13:14.039 That's the launchpad. It's this open source framework 00:13:14.039 --> 00:13:17.259 and platform built on top of React Native. Expo 00:13:17.259 --> 00:13:20.039 simplifies a ton of the development and deployment 00:13:20.039 --> 00:13:22.659 headaches. It's what enables that instant QR 00:13:22.659 --> 00:13:25.360 code testing and the easy over -the -air updates. 00:13:25.720 --> 00:13:27.919 So a solid foundation. What about the future? 00:13:28.059 --> 00:13:30.840 What can we expect? Well, looking ahead, we can 00:13:30.840 --> 00:13:33.399 probably expect things like a plan approval mode. 00:13:33.580 --> 00:13:36.240 Letting you review the AI's plan before it generates 00:13:36.240 --> 00:13:39.299 code. Exactly. More granular control, probably 00:13:39.299 --> 00:13:42.200 extensive template libraries to start from, and 00:13:42.200 --> 00:13:44.659 maybe even multi -user collaboration features 00:13:44.659 --> 00:13:47.090 down the line. So looking at the competitive 00:13:47.090 --> 00:13:49.750 landscape, Rourke seems to have carved out a 00:13:49.750 --> 00:13:52.750 really unique niche. I think so. It's definitely 00:13:52.750 --> 00:13:55.669 more accessible than traditional coding. It's 00:13:55.669 --> 00:13:58.169 more specialized for mobile than the general 00:13:58.169 --> 00:14:01.289 AI code assistance. It's more complete, more 00:14:01.289 --> 00:14:04.730 powerful than simple no -code or low -code builders. 00:14:05.049 --> 00:14:07.490 Right, which often hit a wall. They do. And it's 00:14:07.490 --> 00:14:10.690 more current, leveraging GPT -5. So who is this 00:14:10.690 --> 00:14:12.870 really for? Who should be using Rourke right 00:14:12.870 --> 00:14:16.019 now? I'd say non -technical entrepreneurs, definitely. 00:14:16.100 --> 00:14:18.259 People with ideas, but no coding background. 00:14:18.539 --> 00:14:21.159 Okay. Rapid prototypers who need to test ideas 00:14:21.159 --> 00:14:23.879 quickly. Solo developers who want to accelerate 00:14:23.879 --> 00:14:26.379 their workflow. And who maybe shouldn't use it. 00:14:26.480 --> 00:14:29.340 Or where might it not be the best fit? Probably 00:14:29.340 --> 00:14:32.340 not the best fit for like super complex enterprise 00:14:32.340 --> 00:14:34.980 applications with deep legacy integration. Makes 00:14:34.980 --> 00:14:37.590 sense. Or highly performance -critical games 00:14:37.590 --> 00:14:41.149 that need really deep, low -level engine optimization. 00:14:41.570 --> 00:14:44.529 Or maybe teams already working with massive existing 00:14:44.529 --> 00:14:47.789 codebases where integrating this might be tricky. 00:14:47.970 --> 00:14:49.909 But those technical underpinnings in React Native 00:14:49.909 --> 00:14:53.169 Expo, they suggest that the apps it builds are 00:14:53.169 --> 00:14:54.950 pretty robust and scalable, right? Oh, yeah. 00:14:55.279 --> 00:14:57.799 Building on industry standards like React Native 00:14:57.799 --> 00:15:01.220 and Expo ensures the apps are modern, performant, 00:15:01.220 --> 00:15:03.960 and inherently scalable for most use cases. It's 00:15:03.960 --> 00:15:06.720 not building toy apps. Okay, so wrapping this 00:15:06.720 --> 00:15:08.500 up, what's the big takeaway here? What does this 00:15:08.500 --> 00:15:10.909 all mean? I think Rourke represents a genuine 00:15:10.909 --> 00:15:13.649 breakthrough. It really does. It flawlessly solves 00:15:13.649 --> 00:15:16.149 one of the biggest, most painful problems in 00:15:16.149 --> 00:15:19.389 mobile AI development today. Which is? That massive, 00:15:19.409 --> 00:15:21.789 high -friction gap between having a brilliant 00:15:21.789 --> 00:15:24.950 idea in your head and having a testable, real 00:15:24.950 --> 00:15:27.590 application running on your phone in your hands. 00:15:27.590 --> 00:15:30.490 It bridges that gap. Completely. It's truly the 00:15:30.490 --> 00:15:32.590 ultimate tool right now for rapid prototyping, 00:15:32.669 --> 00:15:34.730 for building personal tools just for yourself, 00:15:34.909 --> 00:15:37.629 or creating really compelling, interactive client 00:15:37.629 --> 00:15:42.100 demos. And when you factor in the cost, roughly 00:15:42.100 --> 00:15:46.220 $0 .20 per app iteration on that starter plan. 00:15:46.279 --> 00:15:49.100 That's crazy cheap. Compared to hundreds of dollars 00:15:49.100 --> 00:15:51.539 an hour for a professional developer or spending 00:15:51.539 --> 00:15:55.240 months learning to code yourself. The value proposition 00:15:55.240 --> 00:15:58.759 is just. It's incredible. Truly insane. It completely 00:15:58.759 --> 00:16:01.200 shifts the economics of creation. So work isn't 00:16:01.200 --> 00:16:03.720 just another AI tool in the pile. No, I don't 00:16:03.720 --> 00:16:06.480 think so. It feels like a fundamental shift in 00:16:06.480 --> 00:16:09.080 how mobile apps actually get created. For a huge 00:16:09.080 --> 00:16:11.940 number of aspiring creators, that massive barrier 00:16:11.940 --> 00:16:14.759 to entry, it's just gone. So if you've ever had 00:16:14.759 --> 00:16:17.919 that app idea keeping you up at night. But you 00:16:17.919 --> 00:16:19.960 felt completely intimidated by the complexity 00:16:19.960 --> 00:16:22.779 of the code app stores. Yeah, that excuse is 00:16:22.779 --> 00:16:24.799 kind of gone now, isn't it? It seems like it. 00:16:24.860 --> 00:16:27.639 Your idea is now potentially just one prompt 00:16:27.639 --> 00:16:29.940 away from becoming a testable reality. It makes 00:16:29.940 --> 00:16:32.820 you wonder. What will you build? Exactly. We 00:16:32.820 --> 00:16:34.779 really encourage you listening to explore this 00:16:34.779 --> 00:16:36.899 space. Think about how these tools could amplify 00:16:36.899 --> 00:16:39.399 your own creativity, your entrepreneurial spirit. 00:16:39.700 --> 00:16:41.940 It's a really fascinating time to be building 00:16:41.940 --> 00:16:44.720 things. It certainly is. Thank you for joining 00:16:44.720 --> 00:16:47.559 us on this deep dive. Until next time, keep exploring. 00:16:48.200 --> 00:16:48.940 Eudoro Music.