Book Image

Democratizing Application Development with Betty Blocks

By : Reinier van Altena
Book Image

Democratizing Application Development with Betty Blocks

By: Reinier van Altena

Overview of this book

This practical guide on no-code development with Betty Blocks will take you through the different features, no-code functionalities, and capabilities of the Betty Blocks platform using real-world use cases. The book will equip you with the tools to develop business apps based on various data models, business processes, and more. You’ll begin with an introduction to the basic concepts of the Betty Blocks no-code platform, such as developing IT solutions on various use cases including reporting apps, data tracking apps, workflows, and business processes. After getting to grips with the basics, you’ll explore advanced concepts such as building powerful applications that impact the business straight away with no-code application development and quickly creating prototypes. The concluding chapters will help you get a solid understanding of rapid application development, building customer portals, building dynamic web apps, drag-and-drop front ends, visual modelling capabilities, and complex data models. By the end of this book, you’ll have gained a comprehensive understanding of building your own applications as a citizen developer using the Betty Blocks no-code platform.
Table of Contents (20 chapters)
1
Part 1: Citizen Development
4
Part 2: First Steps on the Betty Blocks Platform
10
Part 3: Building Your First Application
15
Part 4: The Pro-Coder

What is sandboxing?

Betty Blocks has an option called sandboxing for your application. If you have never programmed before, this won’t immediately make sense – so, what is it exactly?

Sandboxing is a way of splitting up your application into multiple applications, so to speak, which allows you to develop your application without changing the production application. Now, you might be thinking, but that’s exactly what I want to do – change my production application. Of course, that’s the goal, but if you are making a change to your production application and someone visits your application at that point, they might get a broken page, for example – and you don’t want that. You want users to be able to keep doing what they are doing while you work on your application because it might take several hours or maybe even a few days before you are done with making your changes and testing them. This is where sandboxing comes into play.

When...