I’m trying to figure out whether bubble.io is the right software for my project.
I want to build a website where the user
goes through a questionnaire (~50 data points per user)
pays and
based on the answers gets shown custom results (gets shown up to 100 different content nuggets a ~500 words).
Example: If you answer you smoke, you get the how-to-stop-smoking content snippet shown on another page (behind a paywall). Based on other answers, you get other additional content shown etc.
Here is how I would do it with bubble:
Get form-input via the bubble inline element
Use custom build or wordpress as CMS for the personalised results pages?
Get a paywall via the stripe plugin
Add custom code to manage the conditions and stitch everything together
→ Is there a faster, less custom solution I’m missing? 3rd party/ payed solutions are fine.
→ How long do you think a total newbie would need to get the basic version running?
Really it depends upon your web developer experience. If you have been a developer of software engineer in the past you will get up to speed really quickly, once you’ve worked out the quirks of Bubble.
If you are a total newbie it might take you longer.
Currently, I have only rudimentary coding experience i.e. “built a calculator” level. Do you think 1 week of getting to understand the bubble basics of the tool, 1 week for the POC and 1 week to fine tune all functionality is realistic? Fulltime that is.
I agree, you can do this directly in Bubble. Store the question answers in the database as the user answers each one. At the end of the questionnaire, have a workflow that redirects to the correct page based on their answers.
Thanks for the answers! Building everything in one tool without custom code would be amazing.
Does this even work with the conditional visibility? I’d imagine one results page for all customers with the following content:
[show content 1, if condition 1 is met]
[show content 2, if condition 2 is met]
…
Is this the right way to think about it?
You will build your app in a week, and it might work, but it’ll be . You’ll build yourself into holes, and learn what you did wrong.
You’ll then rebuild it, and do the same again.
The third time, your app will probably be a good enough standard to push live.
This is correct. Given that you’re dynamically showing and hiding content, option sets might be best to use to store the questions + possible answers, though other use cases would prefer them to be in the database. Each Question (option) would have a list of Answers (Answer is another option set), a Correct Answer (option), and any other values you want.
You can then show and hide content based on the user’s Question Responses (a data type/table, which contains the User, the Question they’re responding to, their Answer, when they did it etc)