BuildShip For Beginners: MUST KNOW Beginner Tips To Get Started FAST!

you've probably seen me use an amazing tool called build ship to build fairly complex apps indeed it's an awesome no code tool that nicely complements another app building tool such as flutter flow this approach allows you to build out your apps UI using a tool such as flut flow and then develop all your logic Flows In build and so in today's video I want to share with you some important getting started tips that allow you to hit the ground running quickly and easy easily and I'll also close out this video with some powerful and easy to leverage techniques that you can use for your next app all right so here we are in build ship and as you can see I already have one workflow a fairly complex workflow that I built for a previous app and so the first thing that we need to do is we need to create a new workflow and we can do that by clicking this button here and we've created a new workflow that by default is titled Untitled workflow now the next thing that I like to do is I like to rename this workflow because the name is fairly generic and not very descriptive so I'm going to click on settings here and I'm going to rename it and I'm going to call it workflow one which is equally as generic but at least I know what this workflow is about so I'm going to hit save now the first thing that you want to do when you're creating any workflow is you need a trigger but you also need to do something else a lot of people know about the trigger but a lot of people miss out about this important Next Step so we're going to create a trigger and typically you're going to start with a rest API call unless you have a very very good reason for some of the other trigger so I'm going to select this rest API add this trigger and then I'm going to configure it so I'm just going to call it test here and I'm I'm just going to leave it as a get request this is fine get works for fairly simple request now at this point I have the beginning of my own workflow but it's not complete yet we've done 50% we still need to do the other 50% and to show you why this is not enough let's go ahead and deploy it and you can deploy it by cck clicking this ship button so it's going to deploy it and essentially what it's doing is it's converting all of this into code and uploading it into the cloud so it's using the Google's uh infrastructure and has uploaded into the cloud and now this code is available on the cloud and you can reference it using this endpoint so we're going to copy this endpoint and we should have something that works right so if you run it we get back this now let's say I add a node that's going to be doing something useful well if I click here I can select some of the other nodes and you have these uh basic operations right so like generate with AI feature noes paste from clipboard and then you have various sections so you have the core which we're going to be talking about a little bit later then you have the Integrations and you also have the various utilities so let's say I'm going to add a utility called the crawler and I add it here so now we have two nodes and let's say uh this scroller I'm going to give it a starting URL so this URL let's say we give it Hacker News which is a great website if you are into Tech and let's say we configure a selector so I'm just going to put a container right here now if we deploy it uh we should have the beginning of a real app so if I copy this here and I paste it here let's see what happens okay so it says okay and why does it say okay when we are using a crawler well this brings me to a tip and the tip is that you always want to have not only a web hook but you always want to have the socalled return node and you can find this as the first node in the score section so anytime you're creating a workflow you always want to start with two nodes okay your web hook node or your trigger node and the return node and then in the middle you're going to have the actual logic where you're going to be doing something whether sending a request to open AI crawling you know talking to a database etc etc but you always want to have your main logic wrapped inside of these two nodes because if you don't have these nodes uh you're not going to have a functioning app okay so now here we can specify what we want to return right cuz we've done our logic here but we're not outputting anything right which is the job of this note so here I can say hello world and if I deploy it here we're going to get back okay 200 hello world I come over here and I click here and we have we should have hello world when we execute this now the reason it's taking some time is because it's doing all the crawling and we're not really kind of looking into that we're simply outputting hello world and so just to emphasize you want to start with a trigger node and you want to end with a return node and then in the middle you will put all of your logic now the next important tip that I want to give you is that you want to Define your request okay so what do I mean by that well this is our first node here so which means that this node receives the request right so if you use a browser or you use an app to send a request which is what you're going to be doing from flutter flow or like we are testing from a browser or a third party tool we are sending a request and along with that request we are telling it what we want to do and we are also giving it additional data right so with this request we're simply referencing this workflow here which is what we called it this test workflow which uh is denoted by this path equals test okay this allows us to send it to a specific workflow and this uh build chip tool will understand that when we you know send a request to test we want this workflow to function but along with the path we can also send additional data right so with a get request you're kind of limited right with a post request you can send more data but still with a get request you can send something called a query string right so if I go back here I have this test well I can say well name equals James okay so let's say I want to send some extra data and because we need this data right it's Dynamic you know we we we're going to have the user or the app or whatever you might have sending data this data is going to be dynamic but we know that you you know the app or whoever is sending this data is going to be passing name and this name equals something in this case James this is going to be dynamic but because we know name is going to be in there we can tell build chip that we know that name is going to be there so keep an eye on name for us right and the way you do it is by clicking here and then you click on edit and here you can edit all kinds of things that we're going to get to in just a second but right now you want to click on request and when you click on request you have all of these things that bill ship knows about right so it knows about a query which is your query arguments right that we're going to be passing that we're passing right now essentially it knows about a possible body as well as request headers right so when you are doing a get request you're typically not going to be passing a body a body is only going to be passed if you're dealing with post request but with a query uh regardless whether you're doing a post or a get you can pass query arguments and so what you want to do is you want to click on query and you can click here and you can give it the various things like you can assign uh names or Keys as they're called that are going to be inside of this query string object okay so I've just created a new key and I'm going to give it a name right so I know this is going to be you know it's going to be name right because that's what we have but we don't know the value right the value is going to be dynamic so we're we going to give it name here and here I'm going to give it a label called name as well now label is important because label allows you to reference this specific request element here this request key from other nodes okay so key is important because key is actually the part of the request whereas name here is uh so that you can find it easily right you can call it anything that you want as long as you know what it means okay next you want to click on Save there very very important you want to click on Save otherwise it's it's not going to save anything okay so now this note here uh will know not only about the query object which is always the case it's also going to know about the specific data so in this case we're telling you that hey expect the name okay so we we gave it name and here we're doing something okay we're doing something um we're just going to leave it as is but let's say you want to output something having to do with the name right well in this case you can click here and you can click on variables and now you have access to the previous node so we have access to the crawler node here and we have access to this request node here which is this web hook uh trigger node so instead of clicking on request you can click here and you can click on query and you can select name and that's only going to give you access to this name and so here this is going to reply with the name so we're going to deploy it right here okay it's deploying right now okay it has deployed go back here now I'm giving it name equals James right so this is what I'm kind of sending it and it should know what name is because we've told it right and we we are referencing it okay so it should say James okay we're going to execute this it's going to take a couple of seconds because of that crawler node that we have that we're not yet using but we are going to be using but it should output James right here okay okay and there you see James here okay so this is an important tip because as you are building more and more complex apps it's going to make your life a lot easier right so you can work with requests you you're going to be working with body right if you're going to be sending like like a lot of data in a post request you're going to be dealing with body as well so as an example let's say we're working with a post request and inside the body I am going to be sending in a I don't know like City okay so I'm going to be passing the city but not only that I'm going to be passing ing something else I'm going to be passing a state okay so just to show you how it works so now this is going to expect a body right so this is going to be a post request with a body and it's going to be expecting city and state so we're going to hit save and we're going to change this to post okay so this is going to be a post request now we're going to click on ship so that it ships it and in fact we need to change this right here so I'm going to click here and I'm going to go into request and I'm going to go into body and I'm going to select I can do both right so I can click on City and I can hit I can put a comma variables request body State and now it's going to format it as a city comma state so we're going to exit out hit uh ship or deploy copy this but the problem now is because this is a post request you can't really send it from a browser okay so if you do that you should get an error right workflow not found and that is because was there's no such thing as a get workflow we only have a post workflow so technically that that workflow that we're trying to exit with a get request does not exist anymore okay so in this case we need to use another tool and I like to use Rapid API which is a free tool for Mac so if you have a Mac and you like free tools you don't want to pay for a tool you like this tool I really like this Tool uh you can Google for it and you can download it if you're using another platform Linux PC whatever there's lots and lots of tools such as this one so don't get upset all right so here we're going to go into file we're going to create a new request we're going to open up a new window and here we're going to create a post request paste this URL and now if we go into body we can create a body request and this is going to follow a Json uh format right and the way this works is that you want to open curly braces and then you're going to say see City and let's say the city is Miami and state let's say the state is Florida okay close the braces now the next thing I want to do is I want to click on Json so that it uh validates it right so if you go back to text it has nicely formatted okay and so if we go back to our workflow what should the result be it should be Miami comma Florida Okay so we've let's go ahead and deploy just in case in case we made some changes which I don't think we did in this case but this is good practice anyway and now let's go ahead and execute and see what happens so it's going to take a couple of seconds because of that middle node if we remove that node it's going to be a lot quicker so let's go ahead and wait a couple of seconds and this is the response that you're seeing Miami comma Florida which were part of the inputs right so we pass city as Miami so as you can see here City Miami State Florida and it responds with Miami and Florida I had to fix the response to look like this so if you're going to be using variables make sure that that you wrap them inside of this uh dollar sign and uh open bra open curly brace Clos curly brace dollar sign open Cur open curly brace closed curly brace and you only need to do that if you are displaying variables if you're displaying a piece of text you don't need to do that so if I say something like if I do something like hello from I don't really need to do anything with this piece of text so if I go ahead and ship it it should work fine okay we deployed it let's go ahead and run it should say hello from okay and there you see it hello from Miami Florida and so as you can see this particular technique is very very useful okay it's very very useful so that you can reference all the data everywhere whether from a request or somewhere else from other nodes right CU you're going to be building your workflow it's going to have multiple nodes you'll be able to reference it uh pretty much from anywhere so make sure that you put this to good use now this next specific tip is is actually something that I discovered fairly recently and it would have come in handy if I knew about it before because it it can really really help you a lot so I'm going to go ahead and delete this note for now we may add it in the future and so now we have a very very simple workflow now depending on what you may send and depending what's going to happen typically you want to see what's happening in your workflow right you don't want to just keep deploying it and seeing the results which is essentially what you're going to be doing when while you're testing it right what you want to have access to is the variables as you know your workflow is executing right and the easiest way to do it instead of you know constantly deploying it and printing out the variables is you can log it so if you click here you can search for log okay and if you scroll down you see this uh utility node called log message to console and this is very very helpful okay so we're going to click here add this note and now we have a special note that will log pretty much anything that we want to the console okay and what is the console well the console is a place with that displays all the stuff that are only available to developers okay so this stuff is just you know information something that's happening various notes um anything that you want to see so that you know you can confirm that the workflow works that you do not want to make available to your end users okay and typically this is something that you need to do while you're testing your app so as an example remember we are we have this uh web hook here and we are passing uh something that looks like this we have a request and we have city and state now let's say you want to make sure that this workflow works as expected and you don't even care about this return Noe here right you may not not even have it so I'm just going to delete it for now right and so as you're sending this request you want to make sure that you're parsing it correctly right cuz remember we have this thing here we have this city and name but let's say you're passing in a city and that city is not you know it's not being outputed correctly or it's not being used as an input somewhere so what you want to do is you want to make sure the city is actually you know your workflow is capturing the request properly and so what you can do here is you can lo message so what I'm going to do is I'm going to come in here and I'm going to say um city is City and then I can say well I'm going to input a variable here and I'm going to come in here body input City and now we have a log message that was generated for us and so now if you exit out and let's say I ship it I I ship this workflow I deploy it when we run it we should see a message with the variable in the log right and where's the log well if you click here you see all your logs so every time you run the workflow you're going to have a new entry here right so what I recommend is clicking here so that you can see the newest log entry okay have all of these things refreshed and so now let's go ahead and send that same request we're not going to get this output here cuz we deleted the response note but we should have an entry in the logging okay so I'm going to execute this request it should be very very fast we get an okay which is the default response and now if we go back to build ship and we do a refresh so that we see the latest entry and we open it up right we expand it you should see logging information right so in this case you see this logging so if you open that up you see logging here right as you can see it says City Miami which means it's capturing the city correctly and now you can come back here and you can do something else you can say State and you can do state is a state right so query body State you can do that you can close that and now it should list all the variables that we care about so this is very very helpful believe me I wish I had known about this before because it would have saved me so much pain okay so now let's go ahead and deploy it and now if you run the request you should have another logging entry with more information so in this case you're going to have city and state together so let's go back here let's go rerun it it's very very fast and here you want to refresh it so you get the last entry here okay so this is the last entry you can also turn on autof fetch that's going to automatically fetch the last log entry and so this is the last log entry here and you want to make sure that you either have autof fetch turned on or you do it manually cuz otherwise you're going to be looking at Old Log entries right that are obviously not going to have the information that you're looking for because you've done some changes in your app and so the logging information you know maybe from yesterday or like from an hour ago is not going to accurately reflect what you have in your app right now so you want to make sure that you you're you're either doing it manually here or you have autof fetch turned on I just recommend turning on autof fetch all right so this is the last logging entry here and if you scroll down you see this logging entry okay and you see everything right you can see it here but if you have a more complex log entry you might have to expand it and see it right there so now we know that this system you know this workflow in build chip is correctly uh getting the variables which is a half of the battle or even more than half the battle because a lot of times you're passing in data you're sending in the request but it's not picking it up for whatever reason maybe you have a bug here maybe the system has a bug there's a bug somewhere and that means none of your nodes your entire workflow is pretty much you know can be thrown out the window right because you're not capturing the request so here you can see that this is being Capt correctly and we are good to go so we can keep building the nodes right and I definitely recommend that you guys do this in the beginning right you you have your uh web hook trigger node you expect certain variables right or maybe even you know you're not like picking out the individual variables you can log the whole request you can log all the headers you can log everything everything about the request you can just log and then you can kind of analyze right you can check it out you can see if you're getting the right information and once you made sure of that you can continue building now this next tip here is going to save you a ton of time okay so let's say we have this workflow we have a test post we have a loging and let's say we're outputting something so I'm just going to do a return note here and let's say it's 200 and we want to Output the name of the city okay so I'm going to go into request uh body and just City that's all I really care about so now we we have a complete workflow right we have the trigger node we have the response node and we have a logging okay so very very basic workflow but still a complete workflow now there's two things that you can do at this point okay you can ship it you can deploy it which takes a little bit of time right it can take a couple of seconds it can take 30 seconds sometimes it really depends or you can test it right now this is going to save you a lot of time so let me show you how this works right if you click here this essentially simulates a request right so here you can fill in all the stuff for request it's kind of like making a fake request right cuz why would you want to deploy it and then go ahead and you know fetch a tool to test the request if you're simply at the testing stage right you want to be using this testing feature here this is an awesome awesome feature and in fact lots of tools that like this don't even have this feature it's going to save you a lot of time so if you click here it's already filling in the name for you okay I don't think James was there I think I put that myself but name is definitely going to be filled out for you and so this means that you can send in a request with the query parameters right this is great except that we don't really we're not really using these query parameters right we are sending a body so you're going to come in here and what you can do is well I already have the body here I can just copy it here and paste it in here if you didn't have it you'll just do it manually okay and then you can also go into headers and send a header if you want so this is enough we're going to click on test workflow and let's see what happens and there it is and like in less than a second we get a a a response type which is what we have here and we get back the actual uh value right which is the city here now let's go ahead and change this to something else let's say I do something like hello from okay now if we do that we need to wrap it in back ticks and put this inside this with the dollar and the uh the semicolons okay uh excuse me the dollar and the curly braces okay so once we have that go back into test go into body we have this request everything is there right you don't have to you don't have to re-enter the the request stuff the request query string or the request body it's all there click on test workflow it's building executing there it is less than a second or was that a second I don't even know what that was okay very very quickly and as you can guess that's a lot quicker than you know clicking on ship and waiting for it to deploy and then you know using a tool all of that is going to take time you want to do it quickly you want to do it quickly let's try something else I'm going to go into body and let's say San Diego San Diego California let's put see it should say hello from San Diego okay now if I modify this and I say uh and state or just something like this and here I can insert a new variable request body State and we're going to wrap it like this and we're going to come back to test body now it should also reference the state test workflow building executing hello from San Diego andca very very quickly right this allows you to move fast that's kind of what you want you want to be moving fast and you know when you're building anything you're building a nap you're doing it from scratch you're building a flutter Flow app you're building a build ship app you're always going to be testing right you're always going to be testing because you're GNA be making bugs right that's kind of the name of the game really right and so as you can see it's very very fast and it's very very helpful now this is just one way of testing right here this allows us to test the entire workflow but we can also test the individual node right so if you click on any of your nodes you're going to have this uh play uh this play icon right so if you click on that you can test a particular node because if you think about a workflow you have the input in the beginning that's typically your request not always but typically going to be the request and then you have an output at the end right with a node you also have an input into the node and the output into the node so when you combine all the nodes you know you're only dealing with the end points and so what we're going to do is we're going to add another node that we can test individually right so we're going to click here and let's say I want to add a node that does something with AI right we're going to be using open Ai and I'm going to do chat now right now this Noe is part of the workflow but because it has a play icon we can test it separately right so I can click here and we have another dialogue box and I can just simply fill out the values and that's going to run this note separately right it's not going to run it as part of a workflow so I'm going to fetch my API key right here I have my key system prompt you're a helpful assistant and the user request what's the capital of Mexico okay pick a model that we want and run this specific node and let's see what we get and as you can see we got a result output the capital of Mexico is Mexico City so now you know that this specific node works with the inputs that we have provided and that means that pretty much any input is going to work provided that you're using a valid API key and provided that you have given it reasonable prompts so this is very very helpful because now you can just test individual nodes with their own input and output instead of testing an entire workflow by giving it an input and output obviously we can click here and we can test this entire workflow as well and this is something that you should be doing as well but starting out you want to be testing out these nodes individually and by the way you can click on this green icon and see the previously outputed result right so as you can see we have this result here this is adjacent object and you can copy this value if you may need it for something else but it's there now my next tip is going to be a little bit more advanced and this is going to come in very very handy as you're building more and more complicated and customized workflow let's say you want to add a node but you're not quite sure if there's a right node for what you're trying to do right you've browsed all the nodes and you've searched around back and forth up and down down and up but you can't really find the right node well in this case you can select an empty node add this node here and you can get this node to do pretty much anything that you want you can write a little app that's going to be executed as part of this node so right now this node expects a name as a parameter but you can modify that right you can click here and you can change this mod to do pretty much anything that you want so for instance if we go into input it has name you can give it another parameter right you can call this parameter City and I can say City you can go into output and you can Define the kind of things that this node is going to be outputting right now as you can see the output is called output and it's of type string so you can change it into an array a Boolean a number something that you should be familiar if you have worked with flutter flow and you've built custom functions you can also Define what kind of value is going to be returning as well as the arguments is going to be taking in so it's very very similar to flutter flows custom functions or pretty much how you customize any piece of custom logic in any uh no code app builder okay and so let's say we have name and city as our inputs right name and City and if you come over to this node logic here you have access to all of this information and so right now we have access to name but if I put comma and I put City we now are going to have access to name and City so right now this returns hello and so that means we can actually save this and we can also test this node right so let's say uh we click here and we want to test the values right so let's say the name is James the city is NYC and if I run this node what do I get back as the result I get hello and so now you can click here and you can get it to all put something else so you can say well I wanted to Output name right so you can do name here and click save and in fact you don't need to hit save and get out you can actually test it right here so let's say I give it James and the city I'm going to give it NYC right now we're only outputting Hello name so I can click on test node here and let's see what the output is and now it says hello James and let's say we want to take into account the city as well hello James from and we're going to say City okay let's go ahead and test it out and see what it says hello James from NYC and so this obviously gives you the freedom to do anything that you want right this is essentially JavaScript right so you can go to Chad GPT and you can ask it to build a custom app and typically the way you're going to be doing it is you're going to be copying this you're going to give it to chat GPT and you're going to say well here's a sample template of a function you're going to paste this you're going to copy and paste this and then you're going to ask chat GPT to do pretty much anything that you want you know whether to send a request somewhere or output something or anything that you want I'm actually thinking about making a complete separate video on this topic right here so if you want to see a more kind of Deep dive on using chat GPT on building your custom noes or anything of that sort let me know in the comments below but right here you have access to anything right this is your JavaScript so this is obviously going to be for more advanced stuff it's the same thing with you know custom widgets and flutter flow or custom functions or custom actions you have flutter flow you have that you know a drag and drop UI Builder but anytime you need something a little bit custom something a little bit more advanced you should have the ability to do it and this is exactly how you do it using this custom node and so obviously you can you know you can enter more code here you can give it more parameters it's a little app that runs within that bigger app called the work flow okay so you can customize it you can do a ton of cool things so as an example if I go into inputs I can add another input let's say uh State and State and I have it here which is what's going to be displayed uh as I'm building my workflow and then if I go into node logic I can say from City from uh and I want to put it here State and then State here okay okay so now there's no issues not everything looks good let's go ahead anate Nyc New York test this node right here and see what we get as you can see hello James from NYC from New York now all of these tips are very very helpful and they're going to help you hit the ground running so that you can start building workflows whether they're simple or a little bit more complex but the real power of this tool lies in some of the more complex and more powerful things that you can do with it namely what you can do is you can click here let's say and you want to add another node and you have access to very very interesting nodes right so in the score section you can do parallel you can do repeating you also have this empty node which is what I just talked about that allows you to essentially customize it to any way that you want but let me show you a very very powerful node that will allow you to achieve a lot of interesting things so if you click on Parallel and you add this node and what this node allows you to do is it allows you to create nodes that will be executed in parallel okay so let's go ahead and delete this empty node we don't really need it and leave this parallel as kind of the middle the intermediate node right so we have the first node we have the last node and then we have these these intermediate nodes and so in this case what we can do is we can add logic that's going to be executed in parallel so not sequentially how typically it's done it's going to be executed in parallel and so what do we want to do well let's say that we want to call open Ai and we want to create two calls that are going to be executed in parallel and so I'm going to search for open AI I'm going to send a chat here and I can also click here I can copy this click here and I can do paste from clipboard Okay click here now we've created two nodes that are going to be executed in parallel so we're going to get our API Keys here API key here API key here we're going to create a system prompt you are my helpful assistant and let's say the same system prompt and let's say for the user request I'm going to ask it what is uh 5 * 5 and here I'm going to say what is 10 * 10 and we're going to select a model let's say we want to use I don't know 3.5 turbo is going to suffice and now when we run this whole workflow these nodes are going to be executed in parallel okay so in fact we we can just test it out right we can just simply test it out because we don't really need to deploy it now we can deploy it if we want to but right now testing is going to be sufficient so we're going to click here and because this specific workflow does not depend on our request we don't really need to fill anything out we're just going to click on test workflow and see what happens see the kind of result that we get okay and now it's telling us hello from undefined and undefined now the reason we see that is because of this right we don't have city and state we're not working with those variables but one thing you should notice is that this has uh ran successfully so if you click here you're going to see the output and so this is awesome because we see that these uh successfully these NOS were successful right and so what we can do now is we can click here we can delete all this we can delete all this here and we can go into variables and I'm going to click in parallel and I'm going to select the first open eye chat I'm going to select this Al put here and in fact in fact what I can do is I can just click here and I can go into parallel just give me everything all the noes that were executed in parallel just show me what happened okay so let's go ahead and test this again test workflow and we should see the actual data now because that's what these this output node is tasked with and there we see it so we what we have here is we have an object that contains uh two other objects so this is our object here so let me show you let me show you what's happening so I'm going to copy this I'm going to use a tool called Json viewer I'm going to paste this and that way you can see it easily right so as you can see we have an object we have one object which is that Json object and inside that Json object we have two more objects and the output of each object is this right here and this is because that's how open AI nodes are configured right so if you come over here you see output this is this output right here that's how that specific open AI node is configured right right we get output but we also have another output as the field inside the output object which is exactly what you're seeing here you're seeing the object and then the output field and so this is another nice thing is that if you're using any of the built-in nodes you want to go into output and you want to see how the data is being uh fetched how the data is being uh gotten so that way you can just reference the exact data very very helpful and it's going to save you a ton of time but regardless now we've executed uh a workflow that has two parallel nodes and obviously you can add more nodes that you want to have executed in parallel and this could be pretty much anything right let's say you're building a crawler and you want to crawl multiple sides in parallel or you want to do a calculation parallel or you want to access one llm then another llm in parallel there's so many things that you can do and this is very very powerful and in fact I haven't really seen this functionality all that much uh when it comes to other tools very very awesome functionality definitely recommend it and this is just the beginning there's so many other things that you can do with this amazing tool especially when you look at core modules right you can do branching looping uh you can do repeat and plus you have tons of different Integrations which are essentially nodes that do something specific right pre-build nodes that use a specific platform or a specific tool or a specific product to do something right so things like algolia replicate database file storage uh Google Cloud Storage lots and lots of amazing things that allow you to build fairly complex workflows without really needing to code unless uh this is something you have to do and if you need to add some code you can do that as well like I explained in this video so an awesome tool definitely give it a try I've been using it for my apps and I'm very very happy with it now if you guys are impressed with build chip like I am and you're thinking about using it with some of the apps that you're going to be building in the future or maybe you're using it right now then you definitely need to check out our amazing patreon Community because just recently like a week ago I did a deep dive on build chip right I talked about build chip I talked about some of the struggles some of the interesting techniques that I use when I was building a fairly complex workflow right so we had like one workflow and then this thing was calling other workflows it was a fairly complex app and I shared with you guys some of the things that went inside my head as I was building this app but also some of the tips and tricks that I learned while building a fairly complex app that are going to be useful just about anyone right whether you're building a simple app or a more complex app and so if you're looking to do a build ship or if you're just looking to build you know flutter flow apps or no code apps regardless what you're going to be doing you definitely need to check out our amazing patreon Community because over there you're going to find more content you'll be able to view and or clone my flutter flow no code apps you'll also be able to uh View and or clone some of my templates here in the future once this functionality becomes available and you're going to have access to more content right so q&as uh our deep Dives uh some of the other content that I put out for our special members it's all there and beyond all that when you join our amazing patreon Community you're going to be supporting this Channel and supporting my work that is highly highly appreciated so if you're getting value from the content that I'm putting out whether it's these videos or some of the apps that I'm building workflows you name it you're going to find more content there plus you're going to interact with amazing Community that's eager to learn and they're always helping each other and plus I'm providing support as well so definitely check it out you can learn more about it using the link in the description and hopefully I will see you there

Channel: James NoCode

Views: 5,969

Keywords: buildship beginner tutorial, buildship for beginners, buildship tips and tricks, buildship tips for beginners

Id: pttGcGP2_GE

Length: 41min 23sec (2483 seconds)

Published: Tue Dec 19 2023