Book Image

Build Customized Apps with Amazon Honeycode

By : Aniruddha Loya
Book Image

Build Customized Apps with Amazon Honeycode

By: Aniruddha Loya

Overview of this book

Amazon Honeycode enables you to build fully managed, customizable, and scalable mobile and web applications for personal or professional use with little to no code. With this practical guide to Amazon Honeycode, you’ll be able to bring your app ideas to life, improving your and your team’s/organization’s productivity. You’ll begin by creating your very first app from the get-go and use it as a means to explore the Honeycode development environment and concepts. Next, you’ll learn how to set up and organize the data to build and bind an app on Honeycode as well as deconstruct different templates to understand the common structures and patterns that can be used. Finally, you’ll build a few apps from scratch and discover how to apply the concepts you’ve learned. By the end of this app development book, you’ll have gained the knowledge you need to be able to build and deploy your own mobile and web applications. You’ll also be able to invite and share your app with people you want to collaborate with.
Table of Contents (20 chapters)
1
Part 1: Introduction to Honeycode
7
Part 2: Deep-Dive into Honeycode Templates
13
Part 3: Let's Build Some Apps

Reviewing the data model

With the template workbook created, we are now ready to review how the Honeycode team set up the data model for the Inventory Management app. However, before we dive into that, let's take a couple of minutes to think about the data that is required for such an app.

From the requirements, as listed earlier, we would need to have categories defined for the consumables supply versus the asset for tagging the items. Furthermore, we would require sub-categorizations for each of those types. For each asset, we would need to maintain its category and sub-category, along with its status regarding whether it's available, has been requested (and who requested it), has been assigned (and to whom), and more. We would also like to maintain a record of the following:

  • Who all the assets were assigned to
  • When it was assigned
  • When it was returned for auditing and usage purposes

Now that we have an idea of what data we need, let's explore...