Lessons for no-code from code

I spent the second week of September at Render ATL  which is a conference primarily about react and inclusion that is based in the southeast.  At Lunch Pail Labs, we primarily run no-code projects and like to think of ourselves as no-code evangelists.  That being said we love taking what we know from code and seeing how it might apply to no-code.

So if you're a developer or entrepreneur looking for some opportunities in this space, here are some places that I think no-code falls a little short especially as it runs in the enterprise.

Accessibility

Accessibility on the web is a huge deal. 15% of the population has a disability and spend a combined $490 billion. Blind people spend 10.3 Billion on eCommerce alone. And accessibility on the web isn't just good practice, lawsuits for inaccessible software have been on the rise so it's increasingly the expectation. In traditional code, you can have a lot of impact over the accessibility of your product, in no-code you are limited to the extent of the platform. I think this is where tools have some big opportunities to be opinionated and help enforce good practices and teach users (ie Webflow's accessibility checker that lets you know when there are issues). But, there could be some opportunities for more platform agnostic tool that speaks to non-technical users in the same way that no-code does.

Testing

At Lunch Pail, we have a dedicated person who goes through user flows manually but in the much broader world of software you have automated testing, unit tests, integration testing etc etc etc. A lot of these tools don't yet speak to no-code platforms but the space is evolving fast. Apps like preflight,  QA wolf and ghost inspector provide a no-code interface for testing but there is still a ton of opportunity in the space.

Collaboration

I've worked on no-code projects with 3-4 developers and whew, it's not always pretty.  Things like version-control, branching, merging are not very well supported across most no-code platforms. Documentation practices aren't well formed and we don't yet have a set of standards that we can apply (think prettier or ESLINT in javascript) which can make collaboration consistent. What would a documentation product specifically suited for visual development look like? Or what standards might be applied to working in teams? I think there's a ton we can learn from the code that could make good business here for mature organizations using no-code.

And those were the major takeaways! What do you think? Any other lessons that no-code can learn from code? Feel free to tweet us with your thoughts!

For more Lunch Pail Labs articles, thoughts and ideas
subscribe to our  newsletter.