Hi Everyone -
A little frustrated at the moment, so I hope this isn't rambling... I am working on a side project and tried piecing something together using bubble.io, but the learning curve seems to be so high even for some of the most simple tasks. I was hoping to make a basic marketplace similar to zillow or bizbuysell, but when I run into even the smallest error, searching for a solution seems to only yield very technical responses or a myriad of how to videos and $450 16 hour 4 week training programs. I completed the tutorial, I've read the manual, I've watched other youtube videos... I was hoping that would be enough, but it seems that every specific workflow item has a specific and unique solution that is not very intuitive unless you understand coding or computer science.
If I am going to make this be a true side project, I dont think I am going to have the time to learn how to code so I can use a no code app. My fear is if any simple issue arises and it takes me 5 hours to fix, this becomes a full time job, not a side gig. To be more specific, I've spent 5 hours trying to get a map marker to relate to a repeating group cell when clicked on.
I guess I am just curious how other non-technical founders pieced together their companies? What made you decide to bring on a technical co-founder or outsource the tech requirements?
Ha. You may not learn how to WRITE code, but you'll learn TONS of coding PRINCIPLES that are very relevant when you do start to write code.
I'm a Ruby on Rails developer and when starting with Bumble, it really reminded me of Rails principles. You have a view, a database, etc. The only difference is that you set those things up with dragging/some typing inside a fields. To migrate to coding, all you have to do is how to EXPRESS THOSE SAME IDEAS with a bit more text.
I agree with that sentiment. Do you think it’s worth doing a deep dive of bubble so I can
I think bubble would be fine (though frustrating at times) to get an MVP together. Really I am more interested if bubble will provide me a good enough Tech foundation for the time and Money spent learning it.
Could you build this platform on Wordpress? Chances are you can and it's much easier than Bubble if you're gonna end up hiring a tech cofounder anyway once validated.
cc @jamesdevonport
Thanks for the page @rosiesherry
@SLUzer07 I can definitely sympathize. I'm a non technical founder and have built several apps using Bubble (some of them pretty complex!). One was even acquired recently.
One thing I would say is to really try and start with the most basic possible version of your app, ship it and go from there. I've spent a long time trying to get certain very specific things working, and often with Bubble you have to approach things from an unusual angle.
Have you tried the official Bubble Community? I found they were always insanely helpful and I ended up being able to resolve pretty much every issue I have.
Having also built a startup using the VC funding route (having to hire and manage engineers) I really recommend persevering with Bubble.
For most people you're going to ship your first version of your product much quicker and work out whether people actually want to buy / use it without blowing a ton of cash on engineering time.
If things go well, you're in a much better position to transition to a 'code' version f your product if you prove there's a demand - and you've worked out most of the core UX using no code.
So I really recommend watching those YouTube videos (Coaching No Code channel is awesome) and just taking one step at a time, Bubble is insanely complex so there is a lot to learn. Don't get disheartened and keep going... you'll get there!
Also happy to help out if you're stuck on anything, drop me a DM 🙌
Just to add a little bit of other reading. I found this great summary to the question: "Any advice on finding a technical co-founder."
"As a technical founder who is always surrounded by non-technical people, this is what I would personally look for.
Traction - as others have mentioned, traction is king (whether it be with investors, users, paying customers, or ideally all of the above). We want to know that we are joining something that is already moving at a fast pace and that we're coming in to help accelerate that / bring it to the next stage; not something that could potentially go somewhere if only there was someone to help it start. Ideas are pitched every day that are nothing more than theory and finger in the wind predictions so having something to show will really differentiate you from others. Sounds like you're already working towards this with the prototype and 200 early adopters so that is good.
Skillset / Experience - non techies need a CTO to code up the product. In return, show the techies why they need you. A truly compelling scenario would be one that the potential CTO can see that you have everything non-technical covered. Separating roles (e.g. the non-tech does 'sales & marketing, fundraising') is not enough, you need to show why you are an expert in those fields beyond any other non-technical founder we've talked to (e.g. you have a very specific 'in' with the market you're targeting, you've got 10 investors lined up to invest when the prototype is ready, you have hundreds of thousands of followers on <social media platform>). If we see that everything else is firing on all cylinders except the tech, then we can focus 100% on that and not have to question / worry about the rest.
A Compelling Story / Plan - beyond and perhaps even before telling us the actual product you're trying to create, sell us on why it is so desperately needed in the first place. Build a high level narrative around the problems that exist and why current solutions don't work, and then go into the specific solution you came up with. While we may be narrowly focused in building a single product, we also want to know where it fits in the grander scheme and how it will impact the world. Similarly, show a well thought out plan on the various stages of the company and how that will lead to inevitable success, with a large focus on the concurrent technical / non-technical timelines and how they fit together. You'll have to proactively fight the unfair (but perhaps not unfounded) perception that the non-technical guy will sit around twiddling their thumbs while we pour nights and weekends into building a product, and then get to work once it is done.
Lastly, don't position the technical work as just stuff that needs to get done so <more interesting next step> can happen. This interestingly happens quite often (e.g. "All I need is a simple iPhone app that sends messages and we'll be the next Twitter!"). It downplays our contribution to the overall company and shows naivety in how much actual work is required on all fronts for a startup to succeed.
In summary, make it apparent to the potential CTO that you've got everything not only figured out, but working in practice. Show that the technical product is just one piece of the equation and everything else is already in place, and they can rely on you 100% to deliver on all of those items (because you already have)."