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

Answers

  1. Interactions are used to add dynamic changes to your page without having to reload the page.
  2. Click, Change, and OnActionSuccess triggers.

Click triggers activate when you click on the given component. Change triggers work when someone types in a field, for example. Of course, there are a lot more interactions available beyond just these three.

  1. Interactions can target almost any component. Usually, the target type has been defined already by default, so you don’t accidentally target something that would be invalid.
  2. We need to set permissions so data is retrieved securely. If a specific role isn’t allowed to view some data, then that data will not be retrieved and an error will be shown in the component.