No-Code App Showcase & Design Process

ClearBiz System App

Client Problem/Idea:

Our client JG wanted to build an app that could be a journal/diary and a business planner for entrepreneurs who wanted to start their own businesses but didn’t know where to start. This was going to be a tool that curated business content and resources. The client had 90% of their content ready and laid out into the sections that they wanted to present the info. 

Our Objective: 

Tiny Oak Studio’s job was to turn all this information into an easy to use and navigate mobile app. 

The Process: 

We started by wire-framing out all of the content into “screens.” This step was important in helping us figure out the type of “input fields” we needed to create in the app. 

The wireframes also helped inform the features of the app, ie: where we needed to place a “see more text” accordion widget instead of showing all the text at once; or where we should be listing content and in what way that would make the most sense.

Once we had a skeleton layout for the app, we went into building Version 0 of the app. Version 0 was the MVP of MVP’s. It was the simplest form of the app with the least amount of features. 

As soon as we had this working version, the client brought in test users. 

After letting users play with the app for one week, we collected and worked through the feedback, editing the app, polishing features and flows. 

One specific remark was that the checkout flow for buying the subscription plan felt like a ‘gotcha’ for users. A user mentioned that the pricing info should show up sooner in the flow, which we agreed with, and promptly updated, using conditional filters to dictate what content showed up when. 

Version 2 of the app came about because a core function, auto-saving, editable text boxes suddenly stopped working. 

The new set up was to save everything into “collections” or databases, and then to list that content out on the screen under the input fields. 

If the user needed to edit the text they would press the edit button which led them to another page that pulled in information for that specific record entry and allowed them to edit and the input boxes and save the new information. (In the future, we’d like to see Adalo have “inline editing” as a feature, as the use case could be widely applicable in many apps.)

Overall this was a great learning experience, (blog post on this coming soon) [LINK to Adalo Build experience blog post.] and we couldn’t have asked for a better client and team to work with. 

Key Learnings: 

– Create data types and collections/databases to save user input.
– Build a full-on mobile app using Adalo for the first time.
– Polish the app build process through iterations 

If you have an app idea, feel free to connect with us here or book a call directly to chat about your ideas here.