Welcome fellow NoCoder!

Sept 30th Discover NoCode issue #12

• Tool - FlutterFlow

• Leader Spotlight - Andrew Daniels & Alim Charaniya

• Community & Resources - FlutterFlow’s BetterMode Community

• Story - How FlutterFlow is making it possible for traditional development teams and UI/UX developers to work in the same environment.

• Training Video - Learn more about FlutterFlow 5.0 from their FFDC 2024 NYC event!

Tool

FlutterFlow

Strengths:

• Drag-and-Drop Interface for UI/UX Designers: For your UI/UX teams FlutterFlow finally makes it possible for these teams to collaboratively build in the same software as the development team — with real time collaboration.

• Custom Code & Libraries: FlutterFlow lets you build your own custom widgets when the built-in ones don’t cover your use cases. This also means you can export your entire code base and host the platform on your own as your company and users scale. You can also publish your own libraries for your team and soon make them public on a marketplace!

• Backend Platforms: FlutterFlow is a front-end builder but they have taken the time to make it easy for you to connect to scalable DBs such as Firebase and Supabase.

• Environments & Branching Updates: For the first time on a NoCode platform you can now have environments where you can fully test your product before you deploy it. Save different secrets and keys for each environment and do end-to-end testing before going to production.

• Branching Updates: Create new features in a separate branch and merge that branch back into the main branch when you are ready with a comprehensive app diff comparison tool to help you check dependencies.

Weaknesses:

• It’s Not Perfect: FlutterFlow has it’s own set of bugs and quirks that you will have to deal with. Since it’s based on Flutter as a codebase as Flutter changes and updates their software FlutterFlow may lag behind or you’ll need to find other ways to compensate.

• Dependencies: FlutterFlow is real code so there are many dependencies that they use and will likely not be on the most up-to-date version of each dependency so the newest cutting edge features of each dependency likely will not be available to you.

• Hosting Limitations: FlutterFlow hosts the web-driven side of their software on Google Cloud. For better of worse Flutter is a Google-backed platform and building in FlutterFlow puts most of your infrastructure into the Google Cloud right from the start which could impact the level of effort it may take to migrate out of the Google Cloud should you ever need to.

Leader Spotlight

Andrew Daniels ↗ and Alim Charaniya ↗

Andrew Daniels is the previous head of design at FlutterFlow. After his departure in April he has begun to put time into Kaleo and NoCodeUI. He has begun building software for other companies using FlutterFlow through Kaleo and began hosting trainings for people to learn more about good UI/UX through NoCodeUI. If you haven’t followed him on LinkedIn yet, you should definitely check him out. His designs are amazing.

Alim Charaniya (often called Ambitious Alim) runs Ambitious Labs, one of the coolest NoCode agencies and bootcamps out there. They focus on teaching people how to build software using NoCode tools. FlutterFlow and BuildShip are the foundational platforms his bootcamp trains on. He also hosts a podcast where he interviews people who have built really amazing things on FlutterFlow to hear about how they got started.

Community & Resources

FlutterFlow’s BetterMode Community

The BetterMode community it FlutterFlow’s official community. There are many Discord servers you can join as well and often in different regions with communities focused on supporting one another in different hemispheres.

With the leaderboard it’s easy to get noticed in this community if you work hard to help others.

Story

How FlutterFlow is making it possible for traditional development teams and UI/UX developers to work in the same environment.

Potentially for the first time in NoCode product of this scale, dev teams officially have the ability to have different environments to develop, test, and sent apps into production.

This was the biggest missing-link in the NoCode space for dynamic teams of developers and UI/UX app builders. In almost every NoCode tool these two teams can collaborate but at the cost of the devs not having a traditional set of tools to develop and deploy software in separate spaces.

FlutterFlow 5.0 has bridged the gap. Even as apps begin to scale and stability becomes the focus of an app, they can stay (if they wish) inside of the FlutterFlow development environment. Where before companies may have opted to leave and start hosting the code on their own as stability becomes more important than shipping fast.

These new features extend the runway for companies building in FlutterFlow allowing them to continue using the platform beyond initial MVPs.

Training Video

Learn more about FlutterFlow 5.0 from their FFDC 2024 NYC event!

SmartSuite hosts monthly feature release webinars that you can join and see what they are working on! These are live with their team demoing the new features and taking questions at the end of the webinar so be sure to join this one tomorrow morning at 8AM PT! It’s going to be their biggest release yet!

Have a stellar week and keep on Discovering NoCode!

Have a tool or other idea you think we should highlight?
Submit it here: https://www.discover-nocode.com/submit-a-tool

Welcome fellow NoCoder!

Sept 17th Discover NoCode issue #11

• Tool - SmartSuite

• Leader Spotlight - Jon & Tara Darbyshire + Emma Montgomery

• Community & Resources - SmartSuite’s BetterMode and Discord Communities

• Story - How SmartSuite is beating the odds building the next generation of productivity software.

• Training Video - Learn more about the most recent features being released in SmartSuite and the next big release on Sept 18th! (Tomorrow!)

Tool

SmartSuite

SmartSuite is a project and workflow management platform designed to help teams organize, track, and automate their tasks across a variety of industries. It offers customizable templates, real-time collaboration, and automated workflows to streamline both simple and complex processes. With a user-friendly drag-and-drop interface, SmartSuite’s UX makes it easy for teams to adopt and a joy to use. It is becoming popular in areas like GRC, product development, construction, HR, and marketing.

Strengths:

• Easy to Understand Relational Database: SmartSuite makes it trivial to build tables of data and connect them to one another in one-to-many or many-to-many relationships.

• Comprehensive Workflow Automation: SmartSuite excels in automating both simple and complex workflows, which helps users save time by reducing manual tasks.

• User-Friendly Interface: Each part of SmartSuite and it’s UI has been thought out for how a user would want interact with the data naturally. It is refreshing to use a software that works intuitively in the way that I expected it to.

• Real-Time Collaboration: Each record in SmartSuite has a communication panel that lets you chat with your team and @ mention specific members. Work on the same records together and watch reports update without page refreshes.

• Strong Integrations: Integrate with nearly any tool under the sun via platforms like Softr, Zapier, Make, Noloco and more.

Weaknesses:

• Limited Customization for Forms: While the platform provides great forms there are limited options for customizing the layout, flow, field visibility, and design of a form which may not meet all user needs.

• No Role-Based Permissions: SmartSuite has a static permission system that leverages user assignment fields in tandem with a set of predefined users types and their purposes in the system. This can become a limitation when you need to make a highly customized visual experience for a specific group of users.

• Business Logic Processes After Save: Formulas on Forms in SmartSuite don’t act like calculators changing in real time as you enter values, to see the formulas update you have to commit the data to the database and view the results.

Leader Spotlight

Tara Darbyshire ↗, Jon Darbyshire ↗ and Emma Montgomery ↗

Tara and Jon are co-founders of SmartSuite and Emma is one of the start consultants that helps build and demo solutions to interested clients. Jon and Tara are both exceptionally sharp with Jon working as the CEO and Tara leading their partnerships. Emma is a lead consultant helping clients see demos and solutions materialize before fully committing to the platform.

Having followed each of them for quite some time they are each exceptional at what they do and I can’t wait to continue learning more from them!

Learn more about them individually in the links above or check out their company’s LinkedIn page below!

Community & Resources

SmartSuite’s BetterMode and Discord Communities

These communities are the best place to find out more about SmartSuite, get answers about their tool and see what other people in the community are building with their tool as well! Bettermode is an exceptional forum and interactive space. Discord is a real-time communication.

Bettermode is great for forum-type discussions and Discord is amazing for it’s real-time communication with peers in the community and in some cases even the SmartSuite team! We love that they decided to use these platforms to stay in touch with their communities.

Story

SmartSuite is beating the odds building the next generation of productivity software.

SmartSuite might be a little bit later to the NoCode space but when you use their software it’s clear they’ve thought about not just the backend but also the user experience as well. The efforts they have made to marry a robust backend with a wonderful front-end experience is obvious. They aren’t just trying to build a database, they are trying to give the end users interacting with it a great experience.

While other productivity tools completely abstract away the relational database side of things, SmartSuite brings together the relational database in a great, simplified way. Allowing for many-to-many or one-to-many relationships to be easily made.

Formula fields use dot notation allowing you to access data across tables through the relationships you make.

All-in-all they have done an exceptional job at building a user experience that gives you all the same ease-of-use that you get in tools like Monday with the robust relational DB experience of Airtables.

They post their roadmap publicly using canny.io. Feel free to check it out and see what they’ve got cooking!

Training Video

Learn more about the most recent features being released in SmartSuite and the next big release on Sept 18th! (Tomorrow!)

SmartSuite hosts monthly feature release webinars that you can join and see what they are working on! These are live with their team demoing the new features and taking questions at the end of the webinar so be sure to join this one tomorrow morning at 8AM PT! It’s going to be their biggest release yet!

If you’re looking to learn how to use SmartSuite feel free to check out their training resources as well at the SmartSuite Academy!

Have a stellar week and keep on Discovering NoCode!

Have a tool or other idea you think we should highlight?
Email us at: inquiry@discover-nocode.com

Welcome fellow NoCoder!

Aug 26th Discover NoCode issue #10

• Tool - Toddle

• Leader Spotlight - Andreas Møller & Kasper Svenning

• Community & Resources - Toddle Discord

• Story - Toddle is going Open Source!

• Training Video - Learn more about Toddle and how to use it!

Tool

Toddle

Toddle is a next-generation visual development platform. It offers a visual interface where developers and designers can collaborate seamlessly, making it easier to build, test, and deploy applications quickly. Toddle is particularly noted for its flexibility, performance, and ability to handle complex app functionalities, similar to traditional coding environments. It supports features like GIT-style version control, real-time collaboration, and the ability to export web components to any codebase.

Strengths:

• Visual Development Interface: Toddle’s drag-and-drop interface makes it accessible to both technical and non-technical users, allowing for rapid app development.

• Seamless Collaboration: The platform facilitates real-time collaboration, and GIT-style version control making it easier for teams to work together and streamline the development process.

• High Performance: Toddle’s backend is based on React/JS and optimized for speed, ensuring fast load times and reliable performance, which is crucial for web applications.

• Flexibility and Customization: It provides extensive customization options, including the ability to add custom code and connect to any API, making it suitable for building highly tailored applications.

• Open Source: Avoid vendor lock-in knowing that you can host your own project/site at any time.

Weaknesses:

• Learning Curve: While it’s user-friendly, there is still a learning curve, especially for users unfamiliar with visual development tools or those transitioning from traditional coding.

• Limited Database Functionality: Toddle does not have a built-in database, requiring users to integrate third-party services like Supabase or Airtable, which might add complexity for some projects.

• Complexity: While pricing is no longer a weakness for Toddle compared to their competitors but the complexity of hosting your own site using the open sourced version of their platform brings it well outside the realm of NoCode at this level.

Leader Spotlight

Andreas Møller ↗ and Kasper Svenning ↗

These two set out to build Toddle back in ~2022 and have been the foundational Co-Founders of the platform. Having followed them both for a while now I am extremely impressed by their expertise and the quality of their work.

Learn more about them on LinkedIn in the links above or check out their company’s LinkedIn page below!

Community & Resources

Toddle Discord Community

This community is the best place to find out more about Toddle and get answers about their tool and see what other people in the community are doing with their tool as well!

Discord is one of the best places to have real-time communication with the people in the community and even the Toddle team. We love that they decided to use this platform to connect with their community.

Story

Toddle is going Open Source!

Toddle is going open-source by late 2024. The transition will occur in phases, starting with enabling self-hosting, followed by releasing the toddle editor. This move aims to give developers freedom from vendor lock-in, allowing them to host and run toddle applications independently. The company emphasizes the importance of community involvement in this process and aims to empower users to contribute and innovate within the toddle ecosystem.

This is huge for the NoCode community and it is amazing to see a company making waves in this space allowing people to build amazing tools without any kind of vendor lock-in.

Training Video

This 10 video playlist will bring you up to speed on what Toddle is and how to use it.

Andreas takes you through what toddle is, creating your first website, dynamic sites using APIs, Interactive Apps, and more regarding how to use Toddle.

The way Andreas breaks down how to use Toddle makes it easy to see whether this NoCode tool is the right choice for you!

Have a stellar week and keep on Discovering NoCode!

Have a tool or other idea you think we should highlight?
Email us at: inquiry@discover-nocode.com

Welcome fellow NoCoder!

July 15th Discover NoCode issue #09 has:

• Tool - Quickbase

• Leader Spotlight - Doc Williams

• Community & Resources - No Code Founders

• Story - How to start learning to build with NoCode

• Hackathon - Join the Discover NoCode Hackathon starting on Aug 5th!

Tool

Quickbase

Quickbase is how Sterling and I got into NoCode! It was founded in 1999 and was originally made and owned by Intuit before they spun off on their own.

Strengths:

• Robust roles and permissions.

• Very robust form builder.

• Table sizes are based on total storage without a set row limit.

• Built in automations that mitigate the need for Make/Zapier.

• External API access lets you integrate other platforms you may be using.

Weaknesses:

• Clunky for anything but raw data management.

• Difficult and time consuming to set up relevant user notifications.

• Mobile app is difficult to use.

• Built on ASCII backend. — UTF-8 character support is only visually rendered, the data is always stored in ASCII.

• Clunky for any kind of internal communications. Expensive file storage.

Leader Spotlight

Doc Williams LinkedIn ↗

Doc Williams is a content creator largely on Twitter and YouTube in the NoCode space. His content ranges from the mobile and web-app builder space all the way to how to support your SaaS products and communities with NoCode tools. Examples of the platforms he educates people on in live webinars are: FlutterFlow, WeWeb, Softr, Adalo, bubble, & toddle.

His live-webinar approach to helping people interested in these platforms gives you a very personalized feel to to his content. If you’re ever watching one of his live-streams be sure to say hi in the chat and ask questions!

Be sure to check out his YT channel where he continues to empower founders and companies on their NoCode journeys.

Community & Resources

No Code Founders

One of the earliest communities in the NoCode space founded in 2019 (you may have stumbled on them before) is No Code Founders. Joshua ↗ and Keanu ↗ Tiernan started NCF and run both their community and Humbl Studio. Mainly focused on bubble development, these two brothers kick some serious butt and have built one of the coolest NoCode communities and consultancies out there.

Along with their community they offer hourly assistance and they have one of the most comprehensive lists of NoCode tools out there. The cherry on top is they show how many people are actively using those tools!

All of that along with weekly webinars and other resources makes it one of the best places to start your journey when you’re looking to connect with other No Code Founders and developers.

Story

How to start learning to build with NoCode.

When I first got into NoCode it was hard to learn these platforms without having a plan or a project with a defined scope to focus on. I would constantly get lost in the sauce thinking about how cool an idea was along with all of its bells and whistles and end up not learning the NoCode platform.

Here’s how I fixed that:

• Choose an industry/skill/hobby that you have great knowledge in.

• Define the scope of an app that tracks something within that space.

• Stick to your scope and force yourself to learn how to use the software.

By selecting a space that you already understand, instead of worrying about how something should work you focus on learning to use the NoCode tool.

Examples:

My first app was a Purchase Order tracker in Quickbase for clients I was managing while in Procurement and Supply Chain Management. I knew the industry, I knew my role, the app I built streamlined what I was doing and gave my boss and clients up-to-date information on their purchases that they could access whenever they wanted to.

Another app made by one of our employees was a Pokédex that tracked all the details and information on each Pokémon like types and attacks! They also tracked the Pokémon that they had captured.

Pokédex App built in Quickbase.

So, when learning a new NoCode platform build something in a space that you are familiar with so you can focus on mastering the platform and not the space.

Hackathon

Join the Discover NoCode Hackathon starting on Aug 5th!

We are hosting our next Hackathon in August! After getting feedback from the wonderful participants of our last hackathon we think we have found some magically fun stuff and we’re excited to host our next hackathon!

If you were part of our first Hackathon you are welcome to join us again!

If you’re new to it all in our Hackathons we help you evaluate and build a NoCode software from scratch in just 2 weeks! Here’s a breakdown below of each day.

Day 1

Identify:

• The 1 person (or company) you are solving a problem for

• The 1 problem you are solving, and

• The 1 specific way you are solving that problem (which will determine the software you create)

Day 2

Create a plan for your software stack that will

• Solve the problem,

• For your target,

• In the way you've decided to do it.

You will end this day with a plan and the list of softwares you'll tie together to build you NoCode application!

Days 3-7

Dive into each of the softwares in your stack and learn them.
Play with them.
Focus on the ones you know very little about.

We will be here to support you as best we can!

Days 8-13

Build the software MVP (Minimum Viable Product) using your newfound skills!
We will be available to help you get unstuck in our Discord server.

Day 14

Reach out to the person(s) you built the software for.

• Let them know you have a software for their problem.

• Get on a call with them, show off the software.

• Ask questions, get feedback.

• If possible, get their buy in! $$

• Iterate on your product to make it better.

Have a stellar week and keep on Discovering NoCode!

Have a tool or other idea you think we should highlight?
Email us at: inquiry@discover-nocode.com

Hello Adventurers!

We’ve got some cool things to show off from the NoCode space this week and some of the newest tools that will may be game changers for you!

Tool

Fireview

I recently ran across this tool that will be game changer for anyone using Firebase for your FlutterFlow or other backend. Firebase wasn’t designed for you to view or easily interact with your data. Fireview fixes that and gives you an easy way to view and interact with the data in a more natural way.

The closest competitor would likely be rowy.io which is the same company that developed BuildShip.com if you haven’t tried BuildShip yet, it’s definitely the star of building API endpoints with NoCode.

Leader Spotlight

Christian Peverelli ↗

Christian leads WeAreNoCode and creates most of their content! He has some of the best YouTube content out there from guides to helping you know how to set up your company with NoCode.

His custom approach to helping non-technical founders build software for their company has helped many companies use NoCode tools to get their feet under themselves and operations running smoothly.

Be sure to check out his channel and his site where he continues to empower founders and companies NoCode journeys.

Community

NoCode Academy by GAP Consulting

No Code Academy Logo

You may know Gareth Pronovost ↗ from YouTube or LinkedIn. He and his team at GAP Consulting recently founded a new platform called NoCode Academy and they just announced it on July 1st!

They offer hourly assistance and help along with courses on many of the most popular NoCode platforms. In addition to weekly onboarding, they are also starting to host weekly webinars with a wide variety of people and educational presentations including AMAs with Gareth himself!

Story

Rebuilding the Discover NoCode website

Over these last 5 weeks Sterling and I began reviewing the tech stack that we had going on with Discover NoCode. There were many issues with the initial tech stack with chose (Softr and others). The tools simply weren’t designed for prospects or monitoring website traffic and where it was coming from.

So without further adieu, we have rebuilt the Discover NoCode webpage using the following tech stack!

• DB & Forms: SmartSuite

• Consultant Scheduling: Zoom

• Consultant Billing: Stripe (connected to Zoom)

• Website: Wix Studio (Formerly Editor X)

• Testimonials: Senja

• Funnels & Nurture for Hackathons: HighLevel

• Newsletter: Beehiiv

With Wix Studio we are now able to monitor website traffic and see where people are visiting from and how many there are along with what pages they are spending time on!

Wix Studio New Highlights Analytics Page

With this new setup we are able to clearly monitor our site traffic and with SmartSuite we are able to see submissions for new tools and gather feedback.

The cherry on top in my opinion though is Senja’s approach to having social proof on your website. Their platform makes it so convenient to collect testimonials and display them on your website site with convenient embeds.

How-to Video

How to Start a $1M SAAS With No Code + AI

Christian Peverelli has been on a role recently and just dropped one of the coolest videos about starting a SaaS with NoCode platforms and AI. Admittedly over the last ~3 years I have been looking to build something fun or SaaS-like for B2B.

The way Christian breaks down the process of finding product-market-fit is so awesome. If you’re brainstorming what you want to do in the NoCode space or how you could build something valuable in your spare time, regardless of whether you’re technical or non-technical, this recent video is sure to leave you thinking about what you could build with NoCode.

Happy 4th of July for those in the US!

Have a stellar week and keep on Discovering NoCode!

Have a tool or other idea you think we should highlight?

Email us at: inquiry@discover-nocode.com

Hello friends!

Last week got more than a little bit hectic around here and we missed the ship on sending this out! We apologize for this!

We are also striving to build towards a newsletter structure that

1. Actually gives you what you want

2. In the most efficient format

3. Without taking a massive amount of time

To that end, we have decided that each of these newsletters will have 5 sections:

1. Tool: A no code tool, and a short description of it

2. Leader: Someone in the space who is making waves (CEO, creator, builder, etc.)

3. New Features: A cool feature released by some no code platform this week!

4. Story: An amazing story someone shared this week when working with no code.

5. How To Video: A video we found useful or insightful.

Let’s jump in!

Tool: BuildShip

BuildShip is my new favorite tool for building my backend.

Having used Zapier and Make, I say the above with a great degree of honesty. BuildShip makes it possible for me to do many of the things I have struggled to do with other low code automation tools. They also integrate directly with so many of my other favorite no code tools (FlutterFlow anyone?).

Not only that, but they are far cheaper than other no code, automation alternatives.

Next, BuildShip is insanely easy to use.

I was able to build an entire backend for my PlayBook project in one night. And I had never even used BuildShip before. Authentication, logic, and more, all completed in less than 4 hours.

Having built backends in the past, that’s a 100X increase in production speed.

Lastly, BuildShip is fast, and they ship even faster.

I get an email almost every week from Harini (BuildShip CEO) telling me that some new feature is released and ready for me to use on BuildShip.

Leader: Harini Janakiraman

If you haven’t connected with Harini yet on LinkedIn, and you’re in the low-code no-code space, I encourage you to do so.

As I said above: BuildShip ships fast (likely because they use BuildShip to build BuildShip…). When ChatGPT announced GPT-4o, BuildShip had integrated it into their system in less than 24 hours. Harini communicated it like a boss, with a video tutorial and everything.

She also collaborates with dozens of people across multiple sectors.

BuildShip lets her and her team spin up almost any kind of tool in less than 24 hours.

This means that whether she wants to do a Web3 hackathon, a FlutterFlow showcase, or a website chatbot integration, she can have it off the ground in under a week.

Those speeds were unheard of last year.

All things said: Harini and the entire BuildShip team are moving faster than almost anyone else in the space.

Features

Since I’m on a BuildShip rampage I’ll stick to it.

In the past two months they have released multiple features including:

1. AI Assistant Builder, with a prebuilt widget that you can embed on any website. Use any model, and give the assistant access to any node inside of BuildShip. This is godlike.

2. A FlutterFlow template tied into their AI Assistant Builder. Stream responses or other using Firebase as well.

3. New triggers. Lemon Squeezy, RevenueCat, email triggers, and scheduled interval trigger.

Every week BuildShip is releasing a new feature, or running a hackathon to use new features to build amazing things.

Story

Dan built a web3 app in 5 hours one evening using FlutterFlow, BuildShip, and

I was a solo freelance blockchain developer for a year and I can tell you, that is absolutely insane.

When I was building, putting together a legit backend and frontend for a web3 app took far, far, longer than 5 hours.

Low code tools are making it possible for one individual to bring a dream to life in a record breaking amount of time.

Dan was spotlighted by BuildShip for what he build (in 5 hours).

I encourage you to give it a read.

How To Video of the week

The video BuildShip put together when they released their AI Assistant builder was awesome. There aren’t many tools that let you build a custom AI assistant for any app in under 7 minutes. Check it out below:

I suggest you give the BuildShip Youtube channel a subscribe.

All of their videos are short, sweet, and to the point.

If you like this new format, please let us know!

Rosson and I truly want to bring you the most value, as efficiently as possible.

We can only do that with your feedback.

So if you enjoyed this, respond to this email and let us know what was great about it (or what sucked)!

Your no-code gurus,

Rosson and Sterling Long

Happy fetching Memorial Day!

If you’re in the United States, let us celebrate the soldiers who have fought to ensure we have the freedoms we enjoy today.

Rosson and I are grateful for them, for you for reading this, and for the technology and freedom that makes it possible to express ourselves in this way.

Let’s get into it.

I’ve been programming since I was 11 years old.

My first memories of a computer are of playing games and making them. This meant that the majority of my programming ability was self taught. While this isn’t a bad thing, it meant I didn’t always have a mentor to help me learn solid code development.

It wasn’t until I was 23 that I started to double down on writing SOLID, modular code.

Luckily for me, this makes me a powerhouse when using low code and no code.

The reason: I know how to design my software so that I don’t ever have to touch it again. Not needing to rewrite code or pieces of software lets you move much, much faster. It’s also far easier to find where a problem exists if what you’ve built isn’t a spiderweb of confusion.

SOLID is an acronym that describes the 5 core principles you need to know when writing good code.

The acronym uses funny names, but the first one is where I’d like you to focus your attention, as the other 4 are less applicable in low/no code environments (which is why I avoided low/no code until recently… it just couldn’t do what I wanted it to).

Behold, the first principle: Single Responsibility Principle.

Single Responsibility Principle

I feel that this one is the most straightforward of the 5 (which is good, because it’s the one we are talking about).

When you’re building something in software, you want that thing to have exactly one responsibility.

What does this look like in reality?

• An endpoint in BuildShip that only creates an account in Firebase (and doesn’t also log them in).

• A component in FlutterFlow that only displays a single piece of information (like the username).

• A table in SmartSuite that only contains information correlated with the object it represents (create another table man. It’s worth it).

What gets people confused is that this “Single Responsibility” looks different depending on your distance from it.

What does that mean?

Let’s use an example from a backend I built for an app called PlayBook (not yet released) with BuildShip a couple of months ago.

I have dozens of endpoints in PlayBook. Each of the endpoints has a single responsibility: Login, Authenticate, Purchase Book, etc.

So at the endpoint level, I have a single endpoint for each responsibility.

If we go a bit lower though and look at the nodes that make up each endpoint, we have another layer of responsibilities. Each node (ideally) handles exactly one task: modify the database, delete this object, transform the information, authenticate the user token. Dozens and dozens of tiny responsibilities that make up the whole of the endpoint.

Sadly, I don’t have a hard and fast rule for determining the level of responsibility you’re looking at in an application.

This is because each application will be different, and I could write a whole book on it.

I will say: the application (especially in no code!) builds in the separation of responsibilities! This is incredibly nice!

Let’s use BuildShip as an example again:

• We create an endpoint (Responsibility Level 1, let’s say)

• We add nodes to that endpoint (Responsibility Level 2)

• We might add custom functions to a node (Responsibility Level 3)

And so on.

The higher levels of responsibility are satisfied by the composition of lower level responsibilities.

This composition lets you reuse code! Each time you plug in a node, you’re reusing code, and composing a higher level of function. This is one of the main reasons I have loved working with BuildShip: They have clearly separated responsibilities and made it easy to reuse things as needed.

There are two core ways to reuse your code in BuildShip:

1. Create your own node and save it (good for simple responsibilities).

2. Create a workflow with a BuildShip trigger and call it from another workflow (good for a more complex responsibility that requires multiple nodes).

A good example of when you might want a BuildShip Trigger might be authenticating a token received from Google. All of your endpoints (that are private) will need this. And it’s got multiple steps you need to work with.

Here’s an example of my simple Google authentication workflow for PlayBook:

The PlayBook BuildShip Trigger to validate Google authentication

While any good no code tool worth its salt will always create a separation of responsibilities for you, there’s always a gray area.

And how well you master that gray area will determine how quickly you move.

Because it will determine how much time you spend rebuilding, testing, etc.

The last amazing use case for the single responsibility principle is that it enables straightforward and easy testing.

Since we are composing functionality from lots of little pieces, once we have tests for all of the little pieces, we can safely ignore them as the cause for any of our problems and focus on the whole. Debugging gets a lot easier. And you eliminate hours of work and confusion. Trust me.

Your clients (or your boss) will love you.

So, mastering the art of the single responsibility will help you:

1. Reduce time building (because you’re reusing code) and

2. Squash bugs faster (because you eliminate dozens of areas where the bug could exist).

The last benefit I’ll share: as you start to build out your own repository of reusable projects, you’ll be able to deliver amazing projects to your clients (or your boss) in a fraction of the time.

You’ll begin to recognize different responsibilities and say “Hey, I already built something that solves that.”

And once you get there… it feels so good just to plug and play the things you’ve already created. Like a kid playing with legos all over again. But making massive waves in the industry while you’re at it. =)

Your friend and AI coach,
Sterling Long!

Regardless of your NoCode stack or even if you’re building in an all-in-one you’ve probably felt the common:

• “What if any of this breaks?”

• “How is anyone going to know where to go to fix a problem?”

• “How will anyone know that this is generated by this automation?”

• “Who will be able to fix problems later if our staff changes?”

Home grown NoCode solutions present tribal knowledge situations that can leave you in a bit of a pickle when the person who built it is unavailable. Even when it’s all within a single platform NoCode can still be a web of information.

Map out your workflows/user stories and data models.

Mapping out your process flow by documenting when and where you are running automations will become fundamentally necessary for your company. Whether it’s in Miro, Lucid, diagrams.net or some other white-boarding platform, always be sure to create a high level mapping of how all of your different systems are connected.

Each NoCode platform will have strengths and weaknesses. Some weaknesses will force you to build certain parts of your workflow on different platforms. Include links to the workflows on your whiteboard and create shared passwords with a password manager tool like 1Password or LastPass.

Below is an example workflow I recently made.

User Story/Workflow Diagram.

And here is the data model that resulted from that workflow.

Data Model based on the User Story.

Automations bring everything together.

In the examples above the software platforms have not yet been decided. Once selected we will organizing the workflow and data model to show their correlated platform along with any interconnectivity between different platforms will become your high level documentation.

When selecting your NoCode Stack consider what automation platforms are compatible with each platform you have selected. Popular platforms you may want to consider are Make, Zapier, & n8n. They become the glue connecting your workflows and data model together within your NoCode Stack.

Complex Formulas and Logic — Black Boxes.

Often times when you adopt NoCode you bring all the complex formulas and logic you currently have from Excel into your new platforms. It is very easy to create a complicated black box where people aren’t sure whether what is going in is coming out correctly on the other side.

Each time you make a formula take the time to explain what the formula is doing and how it is important in the flow of the data. You may find it easiest to document this in-line or in the help-text area that is usually available in NoCode.

Things to avoid in formulas:

• Magic Numbers.

• Calculations that will change over the life of your software/company.

Rather than using magic numbers or formulas that may change over time, store this information in a parent table and give the records in that table start/end dates. Later on when you update this information you can plan how you want to retire certain calculations and move on to new ones.

Bonus: Using this method will also let you run discounts if you are building a quoting system. You can issue temporary pricing with a planned start/end date that make things cheaper when your sales people are entering quotes for their customers.

Recap.

Defeat Tribal Knowledge and resolve issues quickly with documentation.

Top level: How does each platform connect to one another?
Mid level: Data model/schema & Automations.
Low level: Complex Formulas and Logic. How/why it is being done?

Document your workflows and data model before choosing a platform.

Clarity will come when you outline what you want your software do be doing. The right platform is so much more obvious when you start to see what your day-to-day is going to be like.

Plan your formulas according to the lifespan of your software/company.

Building resilient software that will grow with your company can be challenging but it’s always worth it. As your company changes and grows you want your software to empower that growth and change, not stifle or limit it.

What’s new in NoCode?!

This week we discovered a new platform called Frontly! I got to speak with the Founder Patrick Kelly (you can find his LinkedIn here) and was really impressed at how far along their front-end website builder is coming!

While currently the only fully supported backend is Google Sheets, their Supabase integration is currently in beta and moving along quickly!

Patrick is a quick on his feet and listens to his user base to help direct what he should make next focusing on word-of-mouth growth. He also just released a referral program for those who may be interested!

Check out this video here to see the product in action with it’s newest update, a drag-and-drop builder! (The current pricing also wont last long so get in while you still can!)

Happy Mother’s Day (1 day late)!

Yesterday I gave my 10 month old daughter all of my attention so my wifey could have a day off (and play Harry Potter Legacy).

This sacrifice has brought you this post 1 day late, but it’s a great one. Let’s dive in…

A month ago, I set off on an adventure to build a voice and chat bot capable of

1. Interacting with customers,

2. Scheduling appointments, and

3. Delivering essential business information.

To commit myself to creating this, I ran a 5 day challenge where I went live every day and taught others how to do this.

What was fun was that going into that challenge I knew almost nothing about building these chatbots. In fact, I had done very little research on the available tools. All I had was a plan:

• First 3 days, focus on chatbots on websites,

• Last 2 days build a voice bot that could call people.

During those 5 days I was in crunch mode (which is what I wanted).

Every day I was researching and finding new tools. Then I would (try to) train myself on those new tools. Many of the voice bot tools were new, the user experience was iffy, and the implementation was incomplete.

Some of the chatbot tools were far more advanced than what I was looking for.

Ultimately, I found the tools I was looking for, I built the thing I needed, and I was able to teach people how to replicate what I did during those 5 days.

What I ended up with was an executive assistant that could provide general information about me, and book appointments on my behalf.

I called her Chatii.

You can test her out here:

My goal in this post is to show you the exact tools I used to build my AI executive assistant without writing a single line of code, and all of the tools I looked at so you can make an informed decision if you decide this is something you want.

Stack Breakdown

GoHighLevel

The foundation of my project was GoHighLevel, an all encompassing tool that has website building, customer relationship management (CRM), automation tools, calendars, courses, communities, socials, and more.

This platform is the core of my operation.

The CRM feature is amazing because it lets me track all of the conversations people have with my executive assistant.

GHL also comes with the AI chatbot built into the service. It is by far the simplest chatbot setup I have been able to find. The best part is it can function through Facebook, Instagram, Text (SMS), and the live chat widget on a website (You can experience the SMS or live chat on my website when you visit Chatii).

You can easily train the chatbot with general QA, or you can feed it websites with the information you want it to know about.

Chatii for example has been trained on the major informational pages of my website (like my 30 Day AI Accelerator for Beginners) along with multiple QA questions.

Lastly, because GHL offers a calendar integration, the chatbot you build can instantly schedule appointments on your behalf.

But it doesn’t stop there: since GHL has dozens of integrated system, the AI chatbot can schedule appointments for you by guiding people through a series of qualifying questions and then sharing your calendar link.

It’s really fetching awesome!

Synthflow

To add a voice to the digital presence, Synthflow was the go-to choice due to its direct integration with GoHighLevel.

This tool enabled the creation of a voicebot that could not only engage customers over calls but also handle complex tasks such as scheduling via HighLevel's calendar, extracting important information from call transcripts, and even transferring calls!

The setup was also the simplest among the 10+ tools I tested.

If you know how to prompt ChatGPT to get high quality output, then you’ll know how to write the instructions for your Synthflow voice bot!

Due to the tight integration between GHL and Synthflow, once I had my voicebot setup, I could trigger phone calls directly from within GHL. No code necessary.

This doesn’t mean that you need GHL to make Synthflow work though, it can function as a standalone product if all you want is the voicebot portion of things.

Attempted Integrations

Throughout my 5 day challenge adventure, I experimented with several other NoCode platforms that, for various reasons, didn't make the cut:

1. Botpress: This platform was highly flexible but ultimately too complex for my immediate needs.

2. Zappy Chat: While it could integrate with HighLevel, the user experience was poor, complicating the creation of an effective chatbot (I couldn’t figure out how to build a chatbot after 30 minutes or so… I highly recommend you stay away from this one).

3. Zapier Chatbots: At the time of my research, it lacked the capability to be embedded in websites and did not support the automations I needed.

4. Thoughtly: Although user-friendly, it fell short on the integration front, which was crucial for creating a unified system. Can’t use a tool that can’t send data to other platforms.

5. Air: The setup and scripting were more complicated than expected, and integration aspects were lacking.

6. Bland: While it worked, it was functional but buggy, giving the impression of being a neglected platform.

7. Vapi: This software was fetching amazing, and I actually used it to build a voice RoastBot for RoastMe (not implemented) in 5 minutes or so, but it is way low level and would have required a lot of code to get working.

8. ChatHQ: Offered a wealth of features but was overkill for my needs, which centered around simple conversational capabilities.

9. Buildship: This platform was ideal for integrating chatbots with various services, however, my requirement was for a straightforward conversational bot at that stage.

There were others that I ran into as well, but there are so many of these that I am not mentioning them all. The ones above are the ones I actively tried to use and train myself on.

Future Plans

The project doesn't stop here. There are exciting developments on the horizon for the tools used in my stack:

1. Synthflow Knowledge Base: The recent announcement of a knowledge base feature by Synthflow is particularly exciting. This will let the voice bot to handle queries and deviations from my script more effectively.

2. GoHighLevel Chat Widget Enhancements: During the 5 day challenge, HighLevel released updates that allowed edits to the chat prompts. This capability is something I look forward to exploring further, both for my projects and for my clients.

Conclusion

Creating this voice and chatbot application using GoHighLevel and Synthflow was an enlightening experience, demonstrating the power and potential of NoCode tools.

From conception to launch, the project spanned just 5 days.

But most of that was me colliding with different tools.

Ideally, with just this post (and a little bit of gumption on your part) you can have your own chatbot or voicebot setup in less than a couple of hours.

For those intrigued by the possibilities of NoCode platforms, I encourage you to dive in and explore the potential for yourselves. Visit Discover NoCode to:

1. Discover more tech stacks that can help you build applications without coding.

2. Join a community of NoCode enthusiasts and experts.

3. Schedule a free consultation to kickstart your own NoCode journey.

I’m excited to see what you build!

Sterling Long!

Building Discover NoCode — with NoCode!

Written by Rosson Long
Reviewed by Sterling Long

In this Newsletter

• 🚀 Updates to Discover NoCode that should help you!

• 💭 What’s coming for Discover NoCode.

• 🧐 How we built it and how long it took.

🚀 Updates _{^{— Publishing Tomorrow!}}

We just updated our tools section!
Each tool now has a description along with the following categories.

Builder Types:

• App (Can build the front-end that your users will interact with)

• Backend (Can host your data for you)

• Automation (Can automate actions/functions on your data)

Cost Limiters:

• Hosting

• Seats/Connections

• Records

• File Storage

• Reads (API/In Software)

• Writes (API/In Software)

• Automations

Awards:

• SaaS Certified - When a platform earns this award from DNC it means the pricing and scalability would allow you to easily build a profitable SaaS platform on their platform.

• Editors Choice - This award is given to platforms who are leaders in their space. Many NoCode platforms exist in the same spaces, we want to make sure that you can find the best-of-the-best in that space.

💭 What’s Coming

In the next month we will be building new resources for you to access for free!

Leaders — Release: May~June

We are compiling a list of every leader in the NoCode space who is making waves and helping people discover specific platforms!

These individuals are often entrenched in a specific industry making them more difficult to find, but they also are using and leveraging NoCode tools to build their platforms and are leaders in the space.

Why? — Learning, Content & Courses.

Learning
When I first started exploring NoCode platforms it was often difficult to learn the platform. The newer/more niche they are the more difficult it can be to find leaders and content in that space. This will give you resources for these platforms that are exceptional.

Content
There is some amazing free content out there that these leaders have made available on platforms like Youtube and Vimeo. We hope to help you speed up your search for the perfect tutorials and we’re excited to build this list up over time.

Courses
Many leaders in NoCode have made courses and certifications. A great example of a platform where many of these courses have been made is Bubble. There are security courses, app-building courses, and even custom courses for how to build systems for specific industries.

These courses often cost money, but I have found that they give examples and specific use-cases that help you learn how to use the platform in real world scenarios and are well worth the cost.

Stacks — Release: June~July

Stacks are groups of NoCode platforms with exceptional synergy.

Stacks will help you and your team make better decisions by learning which platforms go well with each other and which you will need to connect manually via platforms like Zapier.

NoCode platforms are working each day to improve compatibility with other platforms, we will do our best to keep things up to date and we appreciate any updates to our team when documentation on a platforms compatibility has fallen behind.

🧐 Building Discover NoCode and how long it took.

Why

During my journey of researching NoCode platforms I found so many tools it actually became more difficult to make a choice. I felt as though I had to learn each one before I could make a confident decision.

After 8 months of researching different platforms it occurred to me that they frequently had different and unique purposes. Depending on your industry and needs, the exact NoCode platform you need may have already been created and you just don’t know it because it’s either new, or niche.

When I attempted to prepare a LinkedIn post nearly 3 weeks ago covering and highlighting all these tools, there was just too much content to cover and thus, the idea for Discover NoCode (DNC) was born.

How

Discover NoCode is a love letter to NoCode platforms all around the world. The underlying goal is to only use NoCode platforms to build this repository of information.

So, I first started by deciding on a Stack with a high number of synergies:

• Softr (website) — 3 hours*

• SmartSuite (data center) — 20 minutes

• Zapier (subscription automation Softr ←→ beehiiv) — 1.5 hours*

• beehiiv (newsletter) — 1.5 hours

• Fillout (scheduler) — 45 minutes*

• Discord (community) — 15 minutes

• MEE6 (discord bot) — 2 hours

*I learned this platform for the first time while I was building DNC’s NoCode stack.

Softr — 3 hours
A simple frontend designed for a high influx of visitors that makes it easy to share lists of data from SmartSuite.

Softr + SmartSuite Integration

SmartSuite — 20 minutes
I recently met the team at SmartSuite and I chose to go with them because of how attentive, community driven, and kind they are. Tara and John Darbyshire along with the team they have created is one of the most impressive things I have seen. They deliver what the community is asking for fast.

Image of SmartSuite’s Grid View

SmartSuite’s data can be edited like a normal Excel sheet. Data is saved and updated as you go along and CMD/CTRL + Z functions as expected along with a recycle bin to catch yourself if you make pesky mistakes editing or updating your data.

Share your views publicly like we have on Discover NoCode or integrate your data directly into Softr and make it searchable on the site in just a few clicks!

Zapier — 1.5 hours
Their platform had the best support between Softr & Beehiiv (we initially tried to make this with Make!) Softr made it extremely straightforward to ping Zapier’s webhook and Zapier programed itself with the data being sent.

Zapier Connection with Softr

Then you map the variables consumed from Softr into the beehiiv connection!

Zapier Connection with Beehiiv

beehiiv — 1.5 hours
We selected beehiiv because of our prior experience with the platform! Sometimes familiarity trumps convenience and with Zapier you have the freedom to make those kinds of decisions!

Softr is natively compatible with: Mailchimp and Mailerlite

Softr’s native newsletter integrations.

Editing a newsletter in beehiiv.

beehiiv’s editor is straightforward and intuitive with it’s block system. They are the backbone of one of the most powerful newsletters in the world: The Morning Brew and after using it for a couple months, I understand the attraction!

Another popular platform that we like and may adopt in the future is ConvertKit.com. Their tools for interacting with your subscribers and website visitors to gather information about what people want to see and read about are really neat and intuitive!

Fillout — 45 minutes
Scheduling forms is the newest feature of their platform! Fillout’s scheduler is exceptionally simple to set up and is embeddable like the rest of their forms are!

Embeddable scheduler form preview.

Embeddable link to be copied into Softr!

Embedded into Softr’s custom code block.

Their free tier is extremely generous as well giving you 1000 submissions before you need to upgrade. — I’ll let you know if I somehow burn through all of these.

1000 free submissions!

Discord — 15 minutes
I run a few Discord communities and it’s also LZTEK’s internal operations primary communication method. Setting up the Discord community was a simple copy-paste of the other communities I manage.

Initial Template Server

Discover NoCode Server

MEE6 — 2 hours
This bot connects to Discord and allows you to add all sorts of things to the community like levels, support tickets within the community, private voice channels, moderation, and more! Their platform is extremely comprehensive and I always set up a custom bot when I endeavor to create new Discord communities.

MEE6 Dashboard and Tools for Discord Automations

Wrapping Up.

Creating ecosystems on NoCode SaaS platforms is now so easy that you can create the bedrock of your entire operations in a single afternoon. Even when you may not fully know or understand the tool!

As you approach your own business idea and back-office operations there is likely a NoCode platform or a combination of them that will match your needs and save you time as you run your business.

We’re excited to keep building apps and systems in public and we’ll keep you up-to-date on our new additions to Discover NoCode as we go!

Roasted

The story of RoastMe, the beginning of our NoCode experience.
Written by Sterling and reviewed by Rosson.

“I want to build an app called Roast Me”
Rosson said on the phone.

After talking about it, the idea seemed straightforward, and a great opportunity for me to learn a couple new tools: FlutterFlow and BuildShip.

And my brother was serious.
The next day he sent me a picture of all the domains he bought for the project.

Purchased Domains.

He kicked it off by duplicating some of the work he had already done for another FlutterFlow project.

By the time I got involved on the second weekend (my job was to focus on the backend and AI generation) Rosson already had an entire UI working. He just needed help with actions, payment processing, and integrations with BuildShip.

It took us 4 weekends to put it all together from first call to final MVP.

And I will say, Rosson did the majority of the work making it look good, building the logos, making sure the UI transitioned smoothly. Rosson has an insane eye for an amazing user experience and he brought it all to bear on this project (just as he does with everything he pours his heart into).

Roast Me Landing Page

Now, we’d like to introduce you to the NoCode stack that made it all possible.

The NoCode Stack

• FlutterFlow (frontend)

• Firebase (auth and db)

• BuildShip (automations)

• Stripe (payment processing)

• OpenAI (custom GPT roast bot)

FlutterFlow

FlutterFlow was the cornerstone for our UI/UX and action flows and allowed us to build an app that could quickly deploy to web, iOS, and Android which was important for the big picture of the kind of viral idea we wanted to build.

FlutterFlow also has great integrated database support for Firebase and Supabase which simplifies the process of setting up your DB down to a few clicks.

Using FlutterFlow we had Firebase set up and handling authentication, user management, and data storage in about 45 minutes. FlutterFlow’s built-in database builder automatically updated all of our permissions on Firebase documents. This. Was. LIFE CHANGING!

Highly recommend using Firebase as the go to FlutterFlow authenticator and database, especially if you’re looking for speed.

Firebase

Firebase served as our authentication and storage solution.

Its integration with FlutterFlow and BuildShip streamlined our backend configurations, making it an essential part of our stack. It was also insanely easy to set it up to function. FlutterFlow and BuildShip let you use a pre-generated project or provide your own.

We opted to providing our own (so we could use the same project between FlutterFlow and BuildShip).

BuildShip

BuildShip managed all backend operations.

This included secret key management and secure database updates. We used it to generate roasts securely, maintaining the privacy of our OpenAI key. It also managed user authentication and token updates, integrating smoothly with Stripe to handle transactions. The prebuilt triggers for Stripe purchases and the ability to generate nodes completely from AI made BuildShip an obvious choice for not writing any code.

Ultimately, I was able to build out the backend in a couple of hours using this beautiful tool.

Behold:

A section of our BuildShip RoastMe automation.

Stripe

We integrated Stripe directly into FlutterFlow for handling payments.

This setup allowed users to easily make purchases within the app. The tight integration between FlutterFlow and Stripe made payments easy, and the purchase flow incredibly simple.

BuildShip and Stripe made it possible to pass the UUID of whoever made the payment and then fulfill that purchase to the end user’s personal account and provide them with tokens (or in our case marshmallows).

For simplicity we decided to rely on the transactions stored in Stripe to validate whether a given user has the correct number of marshmallows if there were ever inconsistencies.

Rosson is still working to get Apple Pay and Google Pay set up. He showed me the forms he was filling out to make it work. I applaud his patience.

OpenAI

OpenAI’s powerful AI models were used to generate the witty roasts.

I built a Roast Bot GPT that we used to quickly test things. After a couple of iterations, it was destroying us properly (see it roast me below). Then I used the same prompt inside of BuildShip with a prebuilt script they provide (see “Text Generator” node above). Once I had everything prepared, copy and pasting the prompt and adding in the inputs from the user was a piece of cake.

OpenAI brought the creative concept to life.

Here’s some of our initial testing. The Roast Bot thoroughly destroyed my ego with just a few lines:

Initial Roast Bot Testing — did it Roast Me?

Attempted Integrations

Supabase

Initially, we considered Supabase for its appealing SQL table storage, which is cost-effective at scale.

However, integrating it proved to be complex, particularly in terms of implementing custom getters, setters, and permissions with our BuildShip backend.

Ultimately, we decided to stick with Firebase, as FlutterFlow offered out-of-the-box support that accelerated our development process.

Firebase Functions

While I thought about Firebase functions at the beginning, I didn’t even consider them for what we were trying to do because they would require me to write code.

And we are in the NoCode space.

So this had to be avoided like the plague.

Future Plans

Next planned steps for RoastMe (that we’ll share the how in future newsletters!)

1. Roasting Behemoths — Publicly roast big companies and comedians on X/Twitter (like Ryan Reynolds, Matt Rife, McDonalds, and Wendy’s) using the software.

2. Roast of the Day — Let people share roasts and vote on a roast each day that gets published to Twitter.

3. Roast to Voice — build in voice to the app and have your roasts read out to you, or call your friend and roast them. (We’re looking for a sassy AI voice! If you know of one, send it our way!)

4. Donations — 20% of the proceeds from RoastMe are designed to go towards anti-bullying, mental health, and roast victims! We are in the process of finding charities with these focuses to donate to.

5. HypeMe — If RoastMe takes off we may pursue making HypeMe, the inverse of RoastMe. Perfect for right before big moments where you need to get in the zone.

Conclusion

The RoastMe project was an awesome test of what NoCode platforms are capable of, resulting in a fully functional app developed in just four weekends.

Explore the RoastMe app here, get a personal dose of humility, and see how we used various NoCode tools to bring this fun idea to life.

Visit Discover NoCode to:

1. Discover more NoCode tech stacks.

2. Join the Discover NoCode community.

3. Schedule a free consultation to start building your dream app today!

NoCode tools make it possible to build anything you want, without writing a single line of code and combining them with AI (like BuildShip) let’s you still build completely custom solutions.

It’s fetching awesome!

Your NoCode enthusiasts,

Sterling Long
Rosson Long

What will you build?