NEW Claude 2.0 Is Unstoppable for Building Apps (Master it in 16 minutes)

0:00 Adtopic just turned the Claude desktop app into something completely different and people are already calling this Claude 2.0 and this might be the biggest Claude update of the year. You can now

0:08 create multiple sessions under one main chat. You have a new built-in iOS simulator right inside of Claude and just a massive upgrade to the overall layout of the app. Now, there are 15

0:18 features that I want to cover in this video, which is quite a lot. And if I just went through each of these one by one, I think the video would get very boring pretty quickly. So, instead, I'm

0:25 going to build a brand new app together with you guys. And I want to show you all these new features while I'm building the app. So you can see how these features are actually being used

0:33 in real life. And some of these features really blew me away cuz they make building an app so much easier than it used to be. So if you know the tricks that I'm about to show you, you're going

0:41 to be able to build your apps a lot faster and you'll save a lot more tokens doing it. Let's get started. All right, so this is called Sprout. This is a plant care app and it's the app that

0:50 we're going to be building today as I'm showing you all the new features of the Claw desktop app. And here's how the app will work basically. So, you want to add your plants that you want to track. And

0:58 the app basically reminds you when to water your plants. And each plant here is this little character. If you forget to water it, it will start to droop. But as you water it more, it will perk back

1:09 up. Now, I'm going to use the new Clot desktop app to build three different things here for Sprout. Number one is going to be the mobile app itself. And number two, a web dashboard where you

1:17 can manage all your plans from your computer. And also a short launch video to promote this app. Now, before Claude can build anything, it needs to know where to build it, right? And this is

1:27 the first thing you're going to see when you open the app. And this is something called setting up the environment. And it's right over here under the chat box. Now, in the old desktop app, you can

1:35 just simply select a folder and you can start building. But now, you have to pick an environment first. And to be honest, this actually confused me at first, too. But essentially, an

1:43 environment is just where Clot runs. Right now, there are a few places where Clot can run. You can either run on a computer, the cloud, or another remote computer that you connect to. So now you

1:53 have to pick the computer first and then which folder on that computer. Now, for what we're doing today, you want to choose local here, which is your own computer. This is the one that I use the

2:01 most, and it's the only one that can open the brand new iPhone simulator that I'm going to be showing you later. All right, so I'm going to pick my Sprout folder here, and Claude will actually

2:09 remember this setting. So the next time I log in, I can just click on the Sprout folder, and I'm good to go. And I think that's a nice feature to have. Now there's also this cloud option. So with

2:18 this one, clot actually runs on anthropic servers instead of your own computer. And it works from your project files online in a place like GitHub, right? But you have to connect it to

2:27 your GitHub account. So it can store some files, right? This way it will keep running even when your laptop's closed. But of course, if you don't use GitHub, you can ignore this for now. Now, once

2:36 you've started building something, if you look over to the right side here, you're going to see this new panel, which is called the session rail. And this is where a lot of the new features

2:43 live. Now, if you don't see this panel, you want to look at the top left corner, and you want to make sure that you're actually on cloud code and not chat. Now, there are a few cards here, which

2:51 I'm going to explain as we go. But the card on top here is the environment card. It will show you which computer and which folder Claude is actually working in. So, if you forget, you can

2:59 go in here and confirm. I kind of check this every time I start something new cuz if you're in the wrong folder, Claude will basically build your app in the wrong place. All right, so this is

3:08 one of the biggest updates here, which is called nested sessions. Now a session is just one chat that you're having with Claude. But now Claude can actually start multiple sessions which are called

3:17 nested sessions. So for example, we're building three different things here. The app, the web application, and also the launch video. And I'm going to ask Claude to actually build all three at

3:26 once. So I can just say, hey, I want you to build three different things here. I want you to build the Sprout mobile app and also a web app where people can manage their plans and also a 20 second

3:36 launch video. And do these three in parallel, each in its own session. Now, when you hit go, you're going to notice that Claude first writes this to-do list over here, which is also a new update.

3:44 So, you can see what Claude is actually doing and also the sequence of things that it's going to complete first and it will check off each item as it goes. And I think this is super helpful so you

3:53 always know what it's working on. Now, if you look to the sidebar on the left, Claude has actually started three new nested sessions and they are created in this drop down under my main session

4:01 here. So, you can see that one is building the app, the second one is building the web application, and the third one is creating that launch video. Now, I like this feature a lot because

4:08 it helps Claude be more focused on one specific job and it doesn't get mixed up with other tasks. And the nice thing about this is that when a session finishes, it reports back to your main

4:17 chat, which is kind of like the boss here. So, your main chat knows what's done and what needs your approval. Now, if you've used Cloud Code before, you might be thinking, doesn't Claude

4:25 already have helpers that work in the background? Yes, it does, but you can't really click into each session and talk directly to those agents. So that's why I think this setup is a lot better

4:34 because each one of these sessions is actually a chat that you can click into. So if I go into this mobile app session here, maybe I ask it to, hey, make the plans a bit around her and give it a

4:44 bigger smile. And when you do that, only this session changes while the other two just keep going in the background. So as you can see, you can just fix one thing without stopping all the other builds.

4:53 Now, there is one downside though. Each session has its own memory. So three sessions running at once will actually use up your plan faster. So I wouldn't really run more than four to five at a

5:02 time. Now the big question is when should we use nested sessions versus a normal session. So I think nested sessions are great when the jobs are separate like over here we're building

5:11 the app the web app and also the launch video and they're not dependent on one another to finish but if one job needs another one to be finished first that's when I just want to have one session.

5:20 Quick ad break from our sponsor Omnisad. If you're running a small business right now you know how important it is to have an email list. is a direct line to your audience. But actually managing that

5:30 email list can be timeconuming. Even for my own newsletter, I have to keep checking my open rates, figure out how to analyze all the data. Plus, I still have to find time to write the content.

5:39 Well, Omnisign just fixed all of that and help you manage everything on one single platform. And what's interesting is that they just released Namcp connector for Claude and CHBT, which

5:49 means that you can manage your entire email operation directly from the EI tool that you use every day. So instead of going through a separate dashboard trying to figure things out yourself,

5:57 you can just go to Claude and ask, "Hey, how did my email campaigns perform last month?" And because Claude is connected to Omniscent, it knows exactly how many emails were sent, the open rate, the

6:05 click rate, and how much revenue you made. Or you can ask, "Which automation is making me the most money?" And it now gives you all the data without you having to look it up yourself. Or you

6:13 can also ask, "Are my subscribers growing or dropping off and it gives you a full snapshot of what's been happening with your subscribers?" And even gives you recommendations. And if you go to

6:21 their website, you can even grab all these prompts that you can immediately use to see some of the interesting things that you can do with this connection. And by the way, there's

6:27 already 150,000 brands that use Omnisan. And even if you're on another platform, they'll help you migrate everything in just about 5 days. And if you guys want to try this out, you want to click the

6:36 link in the description below and use code Jason Lee and you'll get 30% off for the first 3 months. Thanks again Omnisan for sponsoring this video. Now, back to the content. Now, there's

6:45 another feature that work a lot like Nesta sessions and it's called quad projects. So the nested sessions I showed you previously, all of these are actually running on my own computer. But

6:54 with cloud projects, they run in the cloud instead. And the way it works is that when you start a project, you only need to talk to one main chat. You basically tell it what you want and it

7:02 will actually split up the work and start several new sessions automatically. And after each one finishes, they're going to report back to the main chat. So it's basically

7:10 nested sessions, but in the cloud. And I see a couple of big benefits to this. Because it is running in the cloud, it will keep going even if your laptop's closed. So you can basically give it a

7:19 long task and close your laptop. You can go away and it's going to still keep working. Now there's one thing to note though. I think this is great if you're building something that runs on the web

7:27 like the Sprout dashboard here that we're building. But if you're building an iPhone app and you want to test it on the built-in iOS simulator projects can't really do that cuz it runs in the

7:34 cloud and the simulator only runs on your own computer. And also Cloud Projects is still in beta and it's only rolling out to some people on Pro and Mac. So you might not see it yet. And it

7:43 also uses up your plan faster cuz every one of those sessions are running at the same time and your files get uploaded to enthropic server. So I won't be using this too much for now, but I think it

7:52 can be really useful for some type of projects. And once this is out of beta, I'm going to be doing more videos on this. Now the next feature is called side chats. So when you're using claw to

8:01 build anything, especially if you're not technical, you're going to come across a lot of terms that you don't know like what is expo go, what is a salei, why are we building this using react native?

8:10 I definitely didn't know what all of these meant when I first started. So if you have a question while Claude is working, you can just type /btw and ask it your question. Or you can go directly

8:20 to the panel here and ask it something like, "Hey, what is expo and why are we using it?" And Claude will answer you in the side tab here. And it's not going to affect the main build. And because my

8:29 question does not appear in the main chat, it won't affect Claude's memory in the session, which is obviously great cuz it won't burn extra tokens and fill up your memory context window. And it

8:38 just keeps everything clean. Now, speaking of context window, the next feature I want to talk about is this context card. So, if you look at the session rail on the right again, it is

8:44 the second card down. It's going to show you how much of Claude's memory you have actually used up in the session. And this is super important because if you have a big project, Claude does really

8:53 well for the first hour or so and then it will start losing performance like you know is forgetting your app's colors or is just redoing things that you already fixed. And this is happening

9:02 because its memory is getting full. So over here you can see the percentage that's being used and what is actually taking up the space. Right now I personally feel like claude starts to

9:10 lose performance when you get to about 300 400,000. So when it starts getting to that point you can actually click on this compact button on the card here and Claude will summarize the chat up to

9:21 that point. You will keep the important parts and free up some space. Now keep in mind that this is not perfect though cuz Claude can forget some of the smaller details when summarizing. So the

9:30 cleanest way and the thing that I personally do is when this gets full, I like to just ask it to provide a handoff prompt and tell it that I want to start a new chat. And when I get that prompt,

9:39 just copy it and paste it in the brand new chat. And now Claude can work from a fresh memory while still retaining all the information of what you built so far by reading this summary that you just

9:49 pasted. Now, right under the context card here is something called the connectors card. And this shows you all the apps that connected into Claude like notion, Hicksfield, Superbase. And this

9:57 has some impact on your memory. Although not a lot and not a lot of people know this, but even if it's not calling that particular tool in the session, it's still going to count against your

10:06 memory, although it's minimal. So, as good practice, if you don't use any of this, you want to just remember to shut them off. Now, going back to the session where we are building the iOS app,

10:14 you're going to see that every time Cloud finishes working on something, it is going to give you the suggested next steps. Now, this is something small obviously, but it is just a helpful

10:22 feature that Cloud has created by predicting what is the next thing that you're going to want to do. For example, if you just finished building your iOS app, you're probably going to want to

10:29 preview it, right? So, here it has predicted what you want to do next, and it's going to make that suggestion here in this card where you can just simply click yes or no. Again, something small,

10:38 but it makes the experience so much better. All right, so all these three sessions have actually finished, but because Claude says it's done, it doesn't mean that it actually works,

10:46 right? So, we're going to test all of these and we're going to start with the mobile app here. And that actually brings me to the new iOS simulator. And this thing is actually built right into

10:54 the desktop app. Now, of course, before this, if I wanted to test a mobile app that I'm building, I have to install the app on my phone and I have to tap through the app myself. And if I want to

11:02 make changes, I got to screen record it, explain Claude the changes that I want to make. But now, we have a simulator here. And the fact that it's built into the desktop app, you can actually test

11:10 everything directly here. And Claude can also see it. And more importantly, you can test it as well. So, you can now see that Claude is actually tapping through all the pages, every button here, every

11:20 screen on its own to check if everything works. And it's doing all of this autonomously. And you can see now that when it finds a bug, it's going to catch it and it's going to report back to you.

11:28 So you'll see when a user tries to water the second plant here, the animation doesn't really work. So Cloud is seeing that error and it's going back into the code and it's going to fix the bug and

11:37 it's going to test it again to make sure that everything works. Now the simulator here is not just for testing buttons or animations. You can also test things like your notifications, live

11:46 activities, and those animations that happen in this dynamic island here directly on this simulator. And of course, you can tap through all of this yourself because it just works like a

11:56 normal iPhone. And you'll notice they also have a lot more controls here. They have the return key, delete key, you can you can rotate the phone sideways, and you can even show or hide the keyboard.

12:04 And if you see a mistake, you can obviously take a screenshot or just do a screen recording right on the panel here and drop it in the chat. Now, big downside to this that you need to be on

12:12 a Mac and you have to have the Xcode app installed, which is Apple's app for building iPhone apps. It is a pretty big download of 10 gigs, but if you already have all this, I think this is a really

12:22 good way to test mobile apps. Now, if you don't want to install Xcode, I do have a small trick where you can build a custom panel on the right side here. So, you can still preview your app without

12:31 installing anything else. And you can even preview your app on the iPhone Duo here that has two separate screens. So, I'm going to be showing you how to set this up at the end of the video. All

12:39 right, the next one here is in app browser. Now, this is not new, but a lot of people still don't know about this. So, Claude can open your website using its inapp browser. You can click around

12:47 and check if everything works, right? So, if you're building anything that is web- based, like the Sprout dashboard here, Claude can actually open it in the browser, it can test everything just

12:55 like it did with the mobile app. So, now you can see that it's actually testing if all the buttons work. It's testing all different scenarios. And if you have a form on the page, Claude can also test

13:04 that as well. And not only that, but it can also make sure that your website is responsive and looks good on mobile. And this is super crucial cuz most websites are open from a mobile device. And if

13:14 you want to make changes, you can click on this button to take your screenshots. You can do some markups and you can send it back to Claude to fix. Now, speaking of fixing things, at some point when

13:22 you're building things, Claude might just head off in the wrong direction. For example, when I was building this web app, I did ask Cloud to make the design more fun, more colorful. And then

13:30 I also ask it to make the color theme more green. And after some time, I felt that it actually went too far and I don't like it. Now, when this happens, you can simply ask Claude to undo all

13:40 this, right? But sometimes it doesn't know at which exact point that you want to revert to. So what you can do is you can use this feature called /re. So I can type in /re and it will pull up a

13:50 list of my earlier messages. So I can just pick this exact one right here, which is the point before I asked cloud to make everything more fun and colorful. And now the app is back to

13:59 exactly how it was. Now, just knowing that this feature exists, I think it's going to make a lot more people more comfortable in trying out new ideas because if Claude breaks something, you

14:08 can just go back to exactly where it was before. And if you think about it, this actually saves you more tokens, too. Cuz if you give Cloud manual instructions to undo something, you're actually going to

14:17 spend more tokens by just sending those instructions. And you also have the risk of it not getting it right in the first time, either. So, I think this is a great feature to have. Now, when I was

14:25 doing all that, the third session actually finished the launch video. And I'm going to play this for you. Now, none of these is actually video generation because Claude wrote every

14:33 single animation using code here. And Opus 5.5, which is the model that I'm using here, is really good at this. And the nice thing about having this written in code is that if I want to change a

14:42 color or a word here or how fast something moves, I can just ask it. And Claude is only going to change that part without touching the rest of the video. Now, Antaric also released something

14:51 called Claude Motion, which makes videos like this right inside of Claude app. And it kind of works the same way, but the difference is that it will give you a separate editor here. So you can

14:59 actually click in and change the words yourself or the timing. And when you're done, you can export it as a video in just one click. But the downside is that right now it's only available on team

15:09 and enterprise plans. But I'm pretty sure that it will come to the pro and max plans as well. All right. So by now cloud has produced a lot of files across a bunch of different sessions. So if you

15:18 want to find out where all the files are, you want to go to this output card here. It is the last card in the session rail on the right side. And I think this is just a nice way to see all your

15:25 output files in one place. Now, of course, building three different apps here can take a while. In reality, you're probably not going to sit at your desk watching Claude work through the

15:34 whole thing, and the moment that you step away, it's probably going to ask you to approve something. But there's actually this feature called remote control. Now, this has been around for a

15:41 few months, but they actually move the switch right in the environment card here, which makes it a lot easier to find. So, when you turn this on, you can carry on the same session from their

15:49 Claude app on your phone. So, if I were to go out and grab a cup of coffee and while I was out, Claude needs my permission to approve something. I get a notification on my phone and I can just

15:58 approve it immediately and it can continue building. Now, the remote control is off by default. You kind of need to toggle it on in every session, but if you do want remote control on for

16:08 every session, you can go to settings and you can enable that. But, of course, you got to remember that computer has to always be on and the cloud desktop app has to be open as well. Now, next is

16:16 auto continue. So, if you've ever hit your usage limit halfway through building something, everything just stops, right? And then you got to remember to come back and you got to

16:24 start it again. But that's not the case anymore cuz now when your limit resets, Cloud will actually automatically resume the session. Now, this has been on by default for some time now. So, you might

16:34 not have even noticed it, but I just want to mention it so that you know it's there. But keep in mind that if your laptop goes to sleep, claude also stops. So, you want to make sure that you go to

16:42 the setting called keep computer awake while cla works and make sure this is on. All right. So, our apps are pretty much ready to go. But there's one more thing that I wanted to show you cuz

16:51 Apple just released the iPhone Duo and it's got two screens. The front screen and also now a huge screen inside which is completely different from a normal iPhone, right? So, when I'm building an

17:00 app, I also want it to look good on this iPhone Duo. And I can't really test it on this iPhone simulator here cuz this is for the normal iPhone. But now we have something called Claude Mods. And

17:10 Cloud Mods allow you to customize how the Claude app works, even adding an extra panel. So, I did ask Claude to create me a new panel every time I build an iOS app as specifically for the

17:20 iPhone duo. So, I can see how my designs appear on this phone. And I don't even have to know how to code this. I can just simply ask cloud to do it for me. And now when I'm building apps, I don't

17:30 have to mention it in my prompt anymore cuz it will know to design an extra version for the iPhone Duo and preview it in this nice UI here. Now, this is just one example of what you can create

17:39 with Cloud Mods. If you want more ideas on what people have created, you can simply go to X and type in cloud mods and you get to see a bunch more ideas. Now, if you want to put all this

17:47 knowledge into building a real app, I recently recreated this app that helps people track their water intake and it's making 100K per month in the app store. And I recently made a video on this

17:56 where I teach you how to design a productionready app like this with beautiful motion graphics all by speaking to Claude in plain English. So, if you want to watch that video, you

18:05 want to click here.