3 things to know using Coda backend for a no-code app

What I learned:

1. Dianna used Coda as a backend to handle all the app logic as well as experience for helping you find the best tea. Coda lacks in slick UI. It looks very low fidelity. To overcome this, especially when testing out an idea using Coda is fine. But if you do want to promote it and ship it like Dianna, you can use Carrd for your landing page. This is really smart to easily, quickly and cheaply dress up the landing page so that when a user first discovers their product you can impress them. First impressions matter.

2. Coda can be used to create app like functionality. Dianna stated that she used it for "the logic around recommending different variations of tea depending on the user preference." i have not personally used Coda so I don't have an educated opinion on the topic.

What I would advise is that you check out this app, see what type of experience it is, and use it as a model or barometer to measure against the desired output you have for your idea.

The worst thing to happen as a Maker is to try a no-code tool and discover that its not going to do what you need it to do. Modeling is a quick way to verify if you should invest time in a particular no-code tool like Coda.

3. I have not heard Coda being overly technical and is a low to mid learning curve. This is not from my own experience but from what conversations I have had with other Makers.

What can Coda be great for? It can be a great internal tooling or MVP for your app idea. Because the UI is not polished, but it does have business logic and app functionality built in, its a great way to test and validate your idea, without spending a lot of money or time invested.