5 Beginner’s Mistakes on Bubble You Should Avoid

there are five specific mistakes we see lots of people making when building apps on bubble and today we're breaking down what each one of those is plus how you can avoid them these are mistakes you might be making right now with your app without even realizing it and they could lead to an unscalable poorly performing app in the long run so stick around to the end to steer clear of these problem areas it's Gabby over at coaching no code apps we help non-technical entrepreneurs build custom apps so they can launch their app-based businesses or grow their existing businesses all without coding now let's jump right into mistake number one which is focusing on building the logic of your bubble app prior to the database structure most bubble applications are very data driven which means that you need to have a strong data architecture set up before you really dive into the core functionality of your application right a data-driven application typically means passing data between Pages things are much more Dynamic your users should be able to create entries in that database and modify those records as well you want to be able to display that information back to the users when they're searching for something right you should be able to manipulate that information so that things are formatted in a certain way you want to be able to create relationships between your data that way you can have really clean organized efficient and scalable applications and features that run off of that data you may want to be able able to perform calculations if your app is very math heavy if you're working with financial based applications or you know dashboards or analytics you might want to do some aggregations and so how you store this information into your database is really important and does have a ripple effect on how the front-end designs may come together or the logic comes together and of course you want to be able to create custom privacy rules around who can access what data you can only do that once you have your structure set up first a lot of people are skipping this part and Diving straight into the design and just kind of throwing things on the page to see what works and it doesn't work that way you have to focus on your database structure before anything else the next common mistake we see is creating too many static designs in the application this can become a problem because you're limiting yourself Dynamic designs on the other hand allow you to create a more scalable application that can really evolve with your users with your growing data over time okay and bubble has many different places in the editor that allow you to create Dynamic structures everything from your front-end designs right using reusable elements for example using conditional statements to change behaviors and appearance properties when those conditions are met to your workflows right you can create a lot of streamlined flows again with conditional statements you can make things more scalable in that way and then of course in your database structure and we've actually got an example here on the screen of comparing a static structure to a dynamic structure that achieves the same thing but you'll see that you get more benefits out of the dynamic structure so on the left we have a data type for a company profile right we might want to save the company's name their logo and then just their General website but then let's say this application wants to capture all of their social network profile links right so the users can link out to them and see their profiles on all the popular networks so with this static structure there's hard-coded fields that have been created for five separate links well that's a problem what if the company has more links than five what if there are new networks that come onto the scene that become popular you've really limited yourself here with this type of structure it's not wrong but you're going to hit a ceiling very quickly as things evolve compare it to the structure on the right now we're actually introducing a second data type to help us with this but it's much more effective so the company profile record on the right has just the name the logo in the general website but then there is a relationship field that links out to a list of other records a list of social link records and because the company will now be in control of creating however many Social Links they need for whichever networks that they have their profiles on this is a much more Dynamic structure you do not need to anticipate a certain number of links that a company may have so be careful with creating too many static designs in your application this isn't to say that static designs are wrong there are definitely cases where it makes sense to make those decisions for your users but be mindful of how scale available some of those structures might be be mindful of how much extra work it's going to require you to to to go through if a change needs to happen right make this application work for you not the other way around the next common mistake we see is ignoring the issue Checker in your editor and also your database as a way to troubleshoot problems in your application look we are not going to get the logic right from the beginning this is very normal you're going to encounter issues you're going to need to troubleshoot the need to solve them this is how you learn this is how you get better at um creating the right kind of logic not just so that things are technically correct and they are actually function for your users but so they are the most efficient approach to things in your application your issue Checker is there for a reason it's producing issues for a reason don't ignore them you're going to create extra work for yourself if you leave that issue to grow to you know over a hundred 200 issues we've definitely seen that it just creates a bigger mess in your editor address those issues because oftentimes you'll find that you need to correct a sequence of things just from clearing out one issue you don't want to leave those hanging around too long because then you're testing environments could actually be inaccurate right the less issues you have present the more accurate your testing is actually going to be and also your database use that as a testing tool as a troubleshooting tool check your tables make sure that your records are getting created properly if the relationships are being stored properly another common mistake we see is designing your logic without any visual cues for your users it's very likely that you're creating something that's interactive right your users are going to make selections they're going to click buttons they're going to fill out forms they're going to create data in the database and if you're not giving them any kind of visual feedback that things are happening in the application they're going to think it's broken and that's a problem so you need to make sure that you create visual cues with any any interactivity that would otherwise be invisible right where things would happen behind the scenes so for example let's say that your users fill out a form right they enter in their name their email they add some other pieces of information and clicking on a button creates a new record in the database well that's technically invisible to them if they click that button you know without any other logic added into that workflow the page is not going to do anything bubble is not going to assume to show the user some kind of a success message you actually have to tell bubble to do those things so with the simple resetting of the inputs which is an action you could add in there right so it clears the form it lets the user know that their their information was submitted in addition to showing some kind of a success alert message or a confirmation message right that really helps the user close the loop it helps them understand that okay the action I took was completed the application has received that information for me and now I can move on okay now we're not all user experience designers that's okay but it's a little tip like this that you just want to be mindful of as you build things out and these things may become apparent to you as you test your own application from the user's perspective but just be mindful of it as you put together the logic and the designs and all of these flows keep your users aware of what's going on in the application help them right don't make them think too much things should be more intuitive when they're experiencing your app another mistake that we see happen all the time applies to everyone no matter what type of application you're building and that is relying on too many plugins now don't get me wrong there are a lot of plugins out there that we use all the time we love them because they do fantastic work and they do extend and the capabilities of your application but you want to be careful with how much dependency you have on external plugins right if you have a ton of plugins installed into your application each one of those is a separate dependency you're dependent on the publisher keeping that plugin updated you're dependent on the publisher keeping that plug-in bug free so plugins are great when you really can't build out the functionality yourself but if you can right and it might require some creativity right you may need to combine different Native bubble elements and custom logic custom States and you know things need to come together to create the same outcome but it is very much worth the control you have not to mention all of the learning that you'll go through by putting something like that together okay so do your homework when you install plugins I'm not saying that plugins are bad there's certainly a time and a place and there's a lot of really great ones out there but do your homework make sure that they're reliable and then it makes sense to depend on that plug-in versus building out the same kind of functionality yourself if possible there are of course lots of different things you'll want to avoid when building your app on bubble and to take a full Deep dive into this join our free extended training at coaching nocodeapps.com forward slash Workshop will guide you on how to build your no code app correctly so you don't run into surprise issues down the road join us at coaching nocodeapps.com Workshop [Music] thank you

Channel: Coaching No Code Apps

Views: 13,377

Keywords: bubble app builder, build an app without coding, apps without code, visual programming, no code app development, bubble.io, bubble.io tutorials, no code movement, no code mvp, no code apps, bubble.is, bubble tutorial, bubble.is tutorial, bubble help, bubble support, bubble.io tutorial, bubble app tutorial, bootcamp, buildcamp, bubble.io lesson, matt neary, bubble beginner

Id: rMTkm0E2WlE

Length: 9min 35sec (575 seconds)

Published: Wed Sep 07 2022