Building an idea whilst simultaneously learning how use tools is time consuming but the experience gained is valuable for better revisions and new projects. The future is NoCode!
Learn how to build in no-code and become a freelancer, build your own startup or change your career into no-code web development.Check it out
What's interesting about this stack is that Maker Marc Fletcher found it easier to implement and more robust to use Glide than Adalo for this particular use case.
One negative of using Glide is it does not provide a good landing page experience. Because Marc's app is B2B, you're landing page is your sell page and will make or break converting a potential client. Using the mobile responsive view glide provides is too restricting.
I've not seen many B2B apps using Glide but this is a good example and smart way to overcome the limitations of Glide. What he is able to do is use a subdomain url for the actual app app.measuredwork.com. This is something new that I learned and is helpful for any Maker who is faced with wanting to use Glide for the app, but also creating a streamlined experience without having different domain names for the landing page and Glide app.
Marc also smartly laid out creating a terms and conditions for privacy by linking to a page on his main domain and providing a checkbox on Glide sign in allowing the user to opt in. There was little friction in this process.
Wow. Once you get into the app I am really impressed with how thorough of an experience it is with organizing data for house building trade. I don't know much about the house building trade but I could easily see how this would help organize a book of business. If I can see that, I would imagine a professional could easily use this to help them This is a great app to explore how deep of an experience you can create with allowing you to add detailed documentation. I did not think that it would be possible to create this deep of a nested experience within each book of business. This has opened my eyes to seeing the flexibility of using Glide for breadth of use.
Read more about my interview with Marc Fletcher and what he shared as a independent niche Maker:
Maker: Marc Best Place to Find Him: Twitter or at through his product built Measured Work.
Marc goes in depth about making and building his project Measured Work. What’s interesting is that product development is not his background. He is a Surveyor by trade and was able to use no-code tools to build a working application.
Additionally, he goes through how can you decide between when to use Glide or to use Adalo. What are the positives of both and what are the limitations of each? Find out in this short read.
MF: I’m an experienced Quantity Surveyor working for volume house building contractors in the UK. After years of comfortable work, I want to expand my skills into developing business solutions using software.
MF: Like most ideas, it arose from the obvious need for better collection and use of data within the businesses I work for. The construction industry is traditionally late to exploit tech solutions and I want to see this changed. NoCode is a great compromise to build software with no risk or software development experience and the thriving tools are testament to the broad adoption of this new movement. I wanted a mobile-first solution and chose Adalo for the relational database and logical build process; the canvas and linked screens provide a nice UI (User Interface) for visual development. Adalo also has some great video tutorials and a helpful support forum.
3. Can you break down for us the limitations you found with Adalo and why it wasn’t the best option for you?
A key feature of Measured Work is capturing granular data of a project as it progresses and I found myself becoming frustrated by not being able to build everything I wanted. I also managed to irreversibly break a database relation which caused me to abandon an entire build.
Glide has a data limit of 25’000 rows of data which would be insufficient to use in a ‘production-ready’ build for paying users. Measured Work records a time stamp value when certain parts of a project are marked as complete. A time stamp isn’t available with Glide so I used a Google Script instead. An unfortunate consequence of using Google Scripts is a time-delay of several seconds before the time stamp value is displayed in the app. This delay would be unacceptable in real life use. I also want to produce reports for users but Glide is incapable of this. Finally, the PWA (Progressive Web App) build that Glide produces is not widely adopted and lacks some features of a traditional app so may be treated with some scepticism by my potential users.
They are both very similar tools in that they build mobile-first tools with great UI’s. Adalo has an integrated database, although their API allows connection to external data sources whereas Glide uses a Google Sheet. I have experience with Microsoft Excel so found the use of Google Sheets a natural step to take. Adalo have recently opened up a component market place which is getting wide approval and Glide are continuously rolling out upgrades. Glide is a cheaper option to upgrade from the free plan than Adalo and there will also be extra expense if you launch on the Google or Apple App stores. I would say if you have some spreadsheet experience, then Gilde will have a shallower learning curve that Adalo
I think there’s a lot of tools, services and newsletters being built for the NoCode community by the NoCode community when the real audience and customers are to be found outside of our comfort zone.
FOLLOW UP QUESTION:
Reasons listed by Marc:
1. No-code awareness in general. People don’t know about it.
2. Education more niche experts need to learn how to make something
3. Guide, because these types of niche makers don’t know how to do product development, talking to users and product marketing to launch something.
Perhaps it’s mostly matters of experience and confidence that drive a maker to progress and build for wider markets. Experience in tool capabilities, limitations, costs, risk and marketing and confidence that comes with experience but also by being inspired by other successful makers.
7. Are there any automation tools like Zapier/Integromat/Parabola that you have dabbled with. Can you give your opinion on this tool?
I love using Integromat and am learning everything I can about it. The potential to automate any number of tasks is so exciting. When tools like Integromat can assure users of their data security, we’ll see an explosion of activity in automation tools.
8. When building anything there is always something unexpected that occured. What parts did you get stuck and learn most from?
I find that sometimes there are so many unanswerable questions that the only way to move forward is to build and expect to have to restart several times. Each new start will include the lessons you learnt from the previous build. I learnt that when dealing with lots of data and especially lots of similar data it’s essential to prevent ‘technical debt’ This means taking the time to avoid shortcuts that may cause problems when you are further along in your build. Use logical labels, be consistent and take the time to do things properly. You’ll thank yourself in the future.
9. What has helped you learn the most. Learning by doing? Should Makers just start making?
I enjoy searching Google for solutions and watching tutorials. If a tool has a mature documentation then take some time to read through it. Yes, start building and try everything. I think that even though you may not achieve what you set out to do then experience gained will serve you well.
10. Please provide what links to your project website, your twitter, where can people return the love?
11. Is there anything else you would like to share or some feedback/request/action that you’d like to ask the Side Project Stack Audience to do for you?
Measured Work is a prototype which is being used for demonstration and validation. If you know anyone who is a house building subcontractor in the UK that would be interested in helping test this software, please email email@example.com. Thank you.
Once a week, valuable and actionable insights, no bs -- promised.