Nas | No-Code Platform

A no-code platform for developing mobile apps, web apps, and landing pages easily without require coding skills.

Overview

This is a project exploration of a No-Code platform where users can easily create mobile apps, web apps, or websites without knowing or having less experience in how to code. As a user of no-code tools for several years now, in this project I created my own version of no-code, which I imagine will help me use no-code and build websites or apps easily. So, the ideas, assumptions and design solutions I present here are my own personal preferences. Because this project is a way to practice and improve my research skills, validate my ideas and design a good interface.

Background

As a user, I have used several no-code platforms to help me build multiple websites and landing pages for some of my clients or for myself. No-code platforms let people who aren't developers make apps without having to learn how to code first. Evidently, many of the no-code tools that are available today are still very complicated and hard to use. Some are even very technical and require basic knowledge or experience with html, css, and javascript.

I think that the growth of no-code platforms today will cause no-code platform players to change and make their products easier to use by giving them a short learning curve and a simple user interface (UI). Some platforms have simple user interfaces, but they don't have many features. A platform with all the features you could want takes a long time to learn, and you might be told to just hire "experts" instead.

So, the challenge is to make a no-code product that meets users' needs with limited knowledge, time, effort, and cost. Where users or businesses can solve problems on their own and improve day-to-day operations without having to wait for engineers to do it. Low-code platforms, on the other hand, do require some coding, but they try to make the process easier by using drag-and-drop interfaces and prebuilt components.

Hypothesis

Building trust with people is essential, and we can do that with a well designed web app. An effective web app design can also aid in maintaining contact with potential clients and bringing in more business. Still, the fact that it simplifies navigation and use for the end user is of greater significance.

The app's profitability is directly tied to the quality of the user interface and user experience. To compete with the myriad items presently available, the one I'm creating will have to be exceptional. My approach is to simplify the entire user experience, from onboarding to product launch, in order to maximize satisfaction.

Research & Discovery

The first thing I had to do was conduct a competitive analysis to find out what other no-code tools were available. My inspirations are FlutterFlow and Webflow. For my exploratory project, these two platforms are the benchmark for the design that I will create in this project. I looked into topics like features and design style. Understanding the purpose of no/low-code allowed me to draw my own conclusions and spot potential areas where I may gain an edge.

From some findings, then I make assumptions to be converted into features.

1. A good product walkthrough is required to take users through the first time they use the product.

2. When users wish to start constructing, they can use pre-built templates or a blank canvas.

3. Apps are constructed with a variety of conditions and interaction logic, it's useful to have a "Issue Detector/Finder" capability to audit the project and determine whether there are any flaws and how to resolve them.

4. A straightforward and "common" interface for designers/developers.

Design Exploration

After determining the feature requirements and scenarios, I began experimenting with the design in a gray wireframe to identify the best layout. After decide the best layout, then I move on to the refining step (hi-fidelity) with numerous iterations to tailor the design to the needs of the scenario/requirements.

A. Page for Onboarding

The onboarding page is the most critical page for me in determining whether or not users will continue to use the product. The onboarding page can be used to educate consumers on how to use the product and highlight key features that users can access. Here, I develop two sections: getting started and exploring the product, so that users may begin building the app immediately.

B. Pre-designed Templates

The template feature will make it easy for users to launch having similar app based on their requirements. Aside from that, the template will save users time so they can focus on other important topics.

c. Issues Finder/Detector

This functionality is really critical. This tool will greatly assist users in determining what went wrong with their project and how to correct it. I also believe that if this functionality can enhance the percentage of users that complete a project.