3
9 Comments

Turning your "app without code" (ex. inside) to traditional stack. How did YOU do it successfully?

Lately, I've been trying to post different topics here to engage users and get the creative juices flowing for myself and everyone else. Today, I'm asking about situations in which your simple, single-function or minimalist websites that you've built without code grew to require a traditional front-end/back-end architecture.

As an example of the above, picture an app built entirely using Zapier integrations. I'm going to make up something silly here, so bare with me:

Say you wanted to make affiliate money off of a simple website that recommends a coffee machine to coffee lovers based on their need and budget. Using the following flow, you could easily do this with Zapier integrations and NEVER require custom code, user logins, page routing, a back-end database, etc.

1. Typeform - User fills out a premade survey/form so we can collect email and learn about their coffee needs (do they prefer coffee pods/k-cups/ground beans/ espresso? do they want to brew single cup or enough for a whole family?, what is their budget?, etc.)
2. Google Sheets - receive and log all user responses and contact info from Typeform. In another Google Sheet, manually map all survey/form responses to a recommended coffee machine from Amazon that makes sense.
3. Mailchimp - Send email with nice template to user, using their email address and other contact information logged in our Google Sheets spreadsheet, and include in the email the coffee machine we recommend. This link will be an affiliate link and you'll make % off the sale. EASY!
4. Automation - If you're feeling fancy, you can use Google Scripts and other things within Zapier to automatically send the coffee machine recommendation email without having to do it manually.

Of course, once you need to implement user logins, manage users, do anything custom, display a growing or changing set of data, you'll need a database and other technology that a full Zapier-integration setup like the example above just won't be able to handle.

Were you ever in this situation? What did you do, and what do you recommend to people like me who have been relying on these integrations as a nervous response to diving into custom code solutions?

  1. 1

    Excellent idea. In fact, I have a coffee related domain waiting to be utilized. Guess, now is the time to establish another web property :)

  2. 1

    Bubble.is as mentioned by @shaunkelleher looks great.

    Also, https://appdrag.com/ looks even better.

    1. 1

      Appdrag looks cool. It seems like more of a front-end development tool with good looking templates whereas bubble allows building of more full-featured apps but is harder to make a good looking front-end

      1. 1

        Ya their marketing page needs work. It's actually a really bad ass back end system that uses lambda but replaces api gateway with something much faster:

        https://cf.appdrag.com/front/docs/AppDrag_White_Paper.pdf

        And apparently bubble is dog slow:

        https://www.indiehackers.com/forum/0b9ef7d36c?commentId=-L5aVNcq2mdl6i6NXI0b

        1. 2

          I'm about to start a new product and considered bubble just to get the non-technical founder to also be able to play around, but I'm slower with drag&drop than reactJS, and it makes me very uncomfortable to have my own app's source be hidden from me.

          1. 2

            Ya I agree, just coding something is easier than drag and drop. It's a hard problem people have been trying to solve forever. People are building substantial businesses attacking pieces of it though, which is nice to see.

        2. 1

          I'm always interested in new code free tools (not being a developer) so thank you. Yes, bubble is very slow its a real problem. Another downside of bubble is its very hard to do good responsive design. Appdrag seems to address that. I would love to migrate from bubble but appdrag just doesnt seem versatile enough yet. For example the project I'm working on right now requires interacting with another service's api which you can do with bubble but apparently not with app drag (if I'm wrong please correct me).

  3. 1

    This comment was deleted 7 years ago

    1. 1

      I understand your question. Depending on the situation you might decide to do one or the other.

      But i believe you can do a lot without coding (Page builder + using Visual SQL for most API functions + using provided jQuery sample code to call your API functions) or coding really few parts and using provided starter cloud functions in NodeJS for more advanced use cases (combining actions, sending an email, call another api/system, ...)

      This way you will have a prototype you can improve and turn into a product without rewriting it completely, add developers later they won't be lost.

    2. 1

      This comment was deleted 9 years ago