Before we jump into what you can build with the Betty Blocks platform, let’s discuss what Betty Blocks is. Betty Blocks is a no-code application development platform hosted in the cloud, so you can access it from anywhere you have internet access.

This means that you can develop applications in your favorite browser from anywhere in the world. Betty Blocks provides you with an all-inclusive tool that allows you to store data, design pages, create workflows, and interact with external services such as APIs, OData, and OpenAPI. All of these form an intuitive user interface that mostly works with drag and drop.

The platform is made for all kinds of developers. Betty Blocks identifies three specific types, namely the citizen developer, the no-coder, and the pro-coder. All of them have something to add to the process of developing an application and need to collaborate with each other to produce the full application. We’ll dive deeper into how this collaboration works between the roles and who can do what.

Because the platform is aimed at citizen developers, you might be wondering whether this mean there is no learning curve? Well… of course there is! Think about people using Excel, for example. Anyone can start inputting data into Excel, but to properly use a lot of its functions, some training might be required. The same goes for Betty Blocks: you might be able to do a lot of basic things already, but to understand all the functions that you can add to an application, it helps to go through a course. This is likely why you are reading this book.

Do no-code and drag and drop mean that you’ll be restricted in terms of what you can do with the platform? The answer to that is no. We’ll dive deeper into this later, but what it comes down to is that the platform allows experienced developers to add code to the platform as well, which increases the capabilities of the platform and thus also the options citizen developers have within the platform.

The main goal for Betty Blocks is to enable business users to build their own applications with the platform. But within that group of business users, there are different levels of developers, namely the citizen developer, the no-coder, and the pro-coder. So, what’s the difference between these three personas?

All personas are business users. The citizen developer is someone who hasn’t got any or much no-code development experience, but it’s someone who wants to innovate and is tech-savvy.

A no-coder is someone who has more experience developing without code and knows all about the functionalities of the platform. They can basically build any application with the platform’s features.

The pro-coder is a developer who normally codes. They assist the other two personas by answering questions, working on security, and maybe adding some extra functionalities to the platform if their use case calls for some code.

The citizen developer

The citizen developer is a user who wants to innovate or make their job easier by creating an application but has no experience in software development. This could be a business analyst or a project manager, for example. The most important thing is that you are interested in using a new technology to empower your workflow.

So, without any experience in software development, what can these people do? Since they are users with specialist knowledge of the process that they would like to digitize, they are very important for the development of the application. In traditional development, these business users have no role in application development. They basically provide the parameters, and after the programming team has done their work they might do some testing, but that’s about it. In no-code development, they become an active part of the application’s development cycle.

What would an employee of a company normally do when they have an idea for an application they need for their work? They can usually do two things. The first is using a tool that can help them build an application. In many cases, you see people using Excel to create tools to help them make their work easier or faster. Is this a bad thing? No, but it does create what we call shadow IT. Shadow IT is something that usually occurs in larger organizations with a lot of employees, when people start creating, for example, a lot of small systems in Excel or Access. The data in these systems is usually stored on the computer or personal workspace of that user, and this involves some risks: for example, when the person who is maintaining an Excel file leaves the company and nobody else knows about that file, all that data is basically lost. Shadow IT can also easily lead to breaches of data, because everyone can start emailing the Excel file around. These are just some of the examples of what can happen with shadow IT.

Then there is the second option that our employees have. They can go to the IT department and request them to build the software they need. In most cases, it will be put on a backlog and hopefully be picked up as soon as the development team has time for it and the priority is high enough. This often means that employees will be waiting a long time before they get their software and usually are not very involved in the development process. So, they might not get exactly what they need.

When using Betty Blocks, all the apps are created in the company’s Betty Blocks environment, which means the IT department knows where it resides and can be a part of the development and maintenance process. This increases the security of the data in the application, and when a developer leaves the company, the application will be easy for the IT department to keep track of.

Betty Blocks allows citizen developers to start creating their own application from the moment they need it. They can start creating wireframes by dragging and dropping a user interface together. Once that is done, they can create the fields that the application will need so that the first prototype will already feel like a first version of the actual application.

The citizen developer will have an active role throughout the development process as well, and they’ll learn new skills by taking part in the development cycle. We’ll talk about what else they can contribute to the development at a later stage – for now let’s move on to the next persona.

To find more information on citizen developers, visit the following URL: https://www.bettyblocks.com/citizen-developer.

The no-coder

The second persona is the no-coder. They are usually business users as well, but they can also be dedicated no-coders who work for the IT department. The big difference between the two is that these users are usually very tech-savvy. These people usually learn new computer skills quickly. So, what is the difference between citizen developers and no-coders in the context of the platform? A no-coder can build an application using the platform from start to finish. They have the knowledge to use all parts of the platform to create a fully functional application. Basically, they will do the heavy lifting for the citizen developer when it comes to designing the workflows within the application and help the citizen developer to make their prototype fully functional, taking the citizen developer on this journey while building the application so they fully understand what, and most importantly how, it’s built. Since there is no coding involved in the creation of the application, it should be easy for the citizen developer to follow the development and even participate in it.

Does this mean that you don’t need any real developers anymore to create applications? Well, we all know that there is a huge need for developers and the business usually needs more from its developers than they can produce in a specific time. This is where no-coder comes in – they can help to create applications faster without the specific need for code-based developers. However, code-based developers should still be involved in the project of creating an application, since they have knowledge the other two personas don’t. So, what can they bring to the table?

The pro-coder

Professional coders, or pro-coders, still have an important role within the creation of an application, but unlike normal development, they don’t have to be involved full time in this cycle. Pro-coders don’t need to have full knowledge of the platform itself. They will need to know the basics and how to add functionality to the platform, but it’s the no-coders that are the experts on the platform itself.

Pro-coders can add code to the platform, which will allow citizen developers and no-coders to do more with the platform. What does this mean exactly? The whole Betty Blocks platform is made up of a lot of small blocks. Our business users use these to build applications in a no-code way, by selecting or dragging and dropping them. But what if they want to do something with the platform that isn’t supported by these standard blocks?

Well, that’s where the pro-coder comes in. They can add code to the platform to create or modify existing blocks, which will allow the business users to do more with the platform. For example, imagine that a business user works with a calendar on their web page, but they need this calendar to have an extra functionality for excluding weekends. The pro-coder can modify the existing calendar to support this and then the business user simply drags and drops the no-code calendar block onto their page to gain the new functionality. This is just a simple example, but this can go much deeper.

Also, a pro-coder can help to go over the application before it goes live to check permissions and some specific security requirements that business users might not be aware of.

So essentially, the business users build the whole application, but the pro-coders help them out along the way with some specific use cases. This saves the pro-coder a lot of time, allowing them to focus on other development tasks.

The following diagram shows how the three developer personas can work together within the platform:

Figure 1.1 – Betty Blocks developer personas

So, let’s recap what the different personas bring to the development of an application in Betty Blocks.

Citizen developers:

• Innovation
• Wireframing
• Adding basic functionalities
• Designing the workflow
• Testing the application
• Collaborating with no-coders

No-coders:

• Data modeling
• Creating fully functional pages
• Creating workflows
• Connecting to external services (APIs)
• Collaborating with citizen developers
• Testing the application

Pro-coders:

• Adding missing functionality
• Checking security
• Checking permissions
• Testing the application from a developer’s perspective
• Assisting with access to external data

Now that we know how the different developer personas can develop using Betty Blocks, let’s have a look at what you can actually build with the platform.

Now we know a little about the different developer personas, but what can you actually build with the Betty Blocks platform? As mentioned before, the platform is cloud based, so it runs on any modern browser. As you might have guessed, you can develop web applications with the Betty Blocks platform. But what kind of web applications, you might ask?

Let’s start with the basics of web applications. A web application can be either public or private, which means that you can develop pages that are publicly accessible through the internet with Betty Blocks, but also private pages that require some form of authentication to be able to access them. By default, everything in the platform is set to private, so you don’t accidentally expose any private information to the public web.

Also, there is the option in Betty Blocks to build Back Office applications. The Back Office is a part of Betty Blocks and allows you to really quickly set up a basic application with full Create, Read, Update, Delete (CRUD) functionality. The interface is fixed, so you can’t change the layout, but you do have some options for sorting by columns and fields. Back Office apps are focused on internal use only. The users are different than the ones accessing the frontend – they are basically the same as the builder users, just without the builder permissions. We’ll talk about this in more detail later.

All web applications that you create with Betty Blocks are responsive by default, meaning they are accessible from a computer, tablet, or smartphone. This feature comes out of the box with the platform and requires minimal action on the part of the developer to make this happen.

Lastly, what types of applications can you build with Betty Blocks? Let me give some examples:

• An order management portal, where users can access their orders, add new ones, and modify them
• You can build your own custom CRM
• Questionnaire apps, for example, to get information from customers
• You can also build additions to your existing CRM by connecting to your existing CRM and using its data to create a portal for your customers
• You can build an inspection report tool, where people can do inspections on site and add images
• You can build a document management system with a workflow behind it
• You can integrate with almost any API out there to create even more complex applications that use data from internal and external data sources and connect to specific services such as Google Maps, for example

Let’s see an example of the ideal areas for deployment of the Betty Blocks platform. If you are planning on building applications within this space, Betty Blocks is the ideal platform to utilize.

Figure 1.2 – The ideal areas for application development with Betty Blocks

I can give a lot more examples of the kinds of applications you can build with the platform. But basically, the sky’s the limit.

So, are there things that are not possible with Betty Blocks? Of course, data visualization over millions of records is not something you would use a platform such as Betty Blocks for, nor creating native applications. Both are possible but are not easily done by citizen developers and require coding knowledge to accomplish. However, here are seven points that do make Betty Blocks stand out:

• Ease of use (no-code empowerment): Users have the tools to develop end-user functionality with their desired look and feel in a simple, fast, maintainable, and non-destructive way.
• Templates (content) and reusability: Reuse functional parts across applications to increase the speed of development. No-code is faster than coding, but if you can reuse entire functional parts, you are even faster!
• Integrations: Integrate applications with external systems. All connections are secure and based on industry standards and IT retains full control. When you need to connect with the more exotic APIs, there is always the coding escape hatch that lets you build without any restrictions.
• Builder collaboration: Applications are always built in (cross-functional) teams. Users can develop and maintain applications together. They have the ability to safely work together on one or multiple applications.
• Escape hatches for flexibility: You can build almost anything without a single line of code. But, if needed, you can add code, ensuring you never get stuck. With escape hatches, experienced developers can build any feature in no-code applications by using code.
• Governance of citizen development by IT: IT wants business users to build applications themselves, but wants to retain oversight to keep things safe and sound. They want to be able to give citizen developers the right building blocks and environment and govern the entire development and delivery process, and Betty Blocks gives them the platform they need to do this.
• Scaling citizen development in enterprises: Enable employees to build their own applications within an enterprise environment while the IT department stays in control of the development process.

But there is so much more that can be done and especially by your business users, which opens up a whole new world. Let’s dive deeper into the platform to explore this.

As mentioned before, the Betty Blocks platform is a cloud platform, which means it’s accessible from anywhere. So, when you create an application on the Betty Blocks platform, where is it hosted? Well, basically there are three different flavors of the platform:

• A public cloud (by default, Azure)
• A private cloud (any cloud operator)
• On-premises

In the public cloud, you can access Betty Blocks anywhere in the world, but can also choose specific areas of the world in which to host your application, including the EU, UK, US, Canada, and many more places. This might be necessary to comply with laws in different parts of the world governing your app and its data. When you start a new application, you can choose where you want it to be hosted. By default, this is always in the Azure cloud.

In a private-cloud setup, Betty Blocks apps are hosted on your own cloud infrastructure, which is maintained and updated by Betty Blocks but owned and operated by you. This is done, for example, if you have a specific cloud preference besides Azure.

The on-premises option means that your instance of Betty Blocks will not be accessible outside your own company. It’s also maintained and updated by your own DevOps team (with support from Betty Blocks). You might choose this option if your data is very sensitive.

In this chapter, we talked about what the Betty Blocks platform is. It’s a no-code application development platform that allows a new breed of citizen developer to take an active role in app development. Together with the no-coder and the pro-coder, they can build applications for the enterprise market. Because it’s all built in the cloud in an IT-managed environment, it’s easy to provide access to any employee in any location.

You can build any kind of web application with the platform since it’s based on the latest web standards. Now you understand who can build on this platform and what kind of applications can be built. In the next chapter, we will look at how citizen developers can work with coders on Betty Blocks.

1. Who can build applications with the Betty Blocks platform?
2. Can you add code to Betty Blocks?
3. What type of applications can you build with Betty Blocks?
4. Where are Betty Blocks applications hosted?

1. Citizen developers, no-coders, and pro-coders.
2. Yes, pro-coders can add code to the platform to add additional functionality.
3. You can build web applications. These can range from a simple CRUD interface to a whole process-based application.
4. They are hosted in the Azure cloud by default, but the platform is cloud agnostic. Also, you can host applications in almost any area in the world.