Landing Pages: What they are and Why they're Important

If you haven't heard of landing pages before, they're pretty much just what it sound like - the first or "landing" page users see when they open your app. Are they important? Well, take a look at the dozens of templates available on Bubble.io and count how many are landing page templates. Your landing page is where you sell potential customers on buying your app. It's where you explain what your app does, how it can help them or solve a problem for them, and why your app can do it better than its competitors.

In addition to being involved in no-code, I also write books and there are a few cardinal rules to making your book stand out. You need to have a title, cover, and description that grabs the attention of potential readers and you need to make use of the proper keywords to attract readers in the first place. The same thing applies to apps. You have to employ keywords and other methods to get them to find your app and then you have to convince them to buy it.

To help customers find your app requires a little knowledge of SEO (Search Engine Optimization) if it's a web app or ASO (App Store Optimization) if it's a native app. Whether you have a web or native app, there are certain search optimization factors that apply to both. Here are a few of the more important ones:

• Keyword use in the HTML title, subtitle, and app description of your landing page (keywords identify the subject of your app such as "project management").
• Use of keywords in the alt text portion of any image tags.
• The app description should be just long enough to provide an in-depth summary of the application's features.
• Page loading speed - a slow loading landing page can turn off potential customers.
• Avoid duplicate content. Don't repeat a keyword string just to try to bump up your keyword count.
• Include an email or push notification sign-up form so you can keep contact with the user, even if they don't immediately buy your app. Also you might include a link to a 3rd party payment service in case the prospect does decide to buy your app.
• If you've made an update to your app, make sure to update your landing page too.
• Check the spelling and grammar on your landing page for accuracy.
• If you have a web app with a URL, have a custom domain that's easy to remember and not overly long.

If you're not sure how to put together your landing page, there are a number of no-code websites that can generate a custom landing page for you including:

• Carrd - The free version allows you to create a landing page from one of their multitude of templates. With their paid version you can have your own custom domain, remove the Carrd branding, and add input forms as well as integrations to third party services like MailChimp, PayPal and Stripe.
• Unicorn Platform - Similar to Carrd, you can create a landing page on the free version or pay to include a custom domain and various integration services.
• Google Sites - Lets you make a landing page for free. Designs are limited but the editor is easy to work with and you can quickly add the basic items you need.
• Bubble.io - Has lots of free and paid templates with a wide variety of designs (bubble.io/templates). This is also a great place to preview a few of the landing page templates to see what type of things you can include in your own landing page.

No-Code Podcasts

Quick Note: If you're looking for more information on no-code try the Visual Developers' podcasts (https://visualdev.fm/listen). With over 60 episodes these podcasts, hosted by Ben Parker, Lacey Kessler, and Matt Varughese, cover topics ranging from "How to Price No-Code Projects" to "The Most Underrated Webflow Features" to "How No-Code will Replace Developers". 

Business Process Automation

There are literally a dozen new "no-code" platforms popping up almost every week - and a good many of them are emphasizing that they can help with "Business Process Automation". So what is Business Process Automation? Basically, BPA is the act of computerizing one of the normal functions or "workflows" in a business (such as Accounts Payable, Accounts Receivable, purchasing, or new employee onboarding) that are currently being done as a series of separate steps. In order to automate one of those processes you have to start by defining the entire chain of events that are involved, including which employees are responsible for which tasks and what each person's options are at a given point in the process. For example, new employee onboarding can be complex, requiring the cooperation of many different people in the organization. Typical steps in the process include:

• Prepare a workplace for the new employee, equipped with a phone, computer, office supplies, and any other items the person may need.
• Set up the new person's internal email and messaging systems.
• Make sure the new hire's supervisor and fellow workers are notified about when the person will be starting work and what duties he or she will be performing.
• Explain the terms of the employment contract to the new hire and secure the person's signature.
• HR will need to have the new hire fill out a Form W-4 for income tax withholding and a Form I-9 to verify the person's identity and right to work in the United States. In addition, if the new hire wants to be paid by direct deposit HR will need to gather that information along with an acceptance form for any voluntary deductions the person elects to have deducted from his or her pay. 
• Set up a training plan and a schedule for training sessions.
•  Present the new hire with a copy of the employee handbook.
• List any equipment, tools or inventory items given to the new employee and obtain the person's signed agreement as to what items were issued.
• Schedule any previously agreed on drug testing.
• Have the person sign any non-disclosure or non-compete forms required by the company.
• (Additional onboarding tasks)

This is only a partial list of the items that may be included in bringing in a new employee, so you can see why doing all this manually can be difficult to manage. Encapsulating everything into an app can streamline the process by ensuring all steps are followed and documented and all persons that need to be involved are notified automatically when there's a task they need to perform. The app can also be designed to allow for alternatives if a particular person is missing or if there's an unusual circumstance, such as the person is being brought on as a freelancer.

Integrating a workflow automation procedure with other systems can also be a big help in keeping track of things. For instance, I did some work a few years ago for a large company that had a dozen tire stores with several mechanics at each store. The company issued certain tools and equipment to each mechanic and employees were required to return those items when they left. Since there was a high turnover, making sure of what had been issued and what had been returned was a time-consuming process. Integrating the inventory function into automated onboarding and exit processes would have simplified the record-keeping required by making it a standard part of the handling of new hires and terminated employees.

If you need to create a BPA system you can definitely do that with a no-code app. With the recent surge in interest in process automation you can build BPA apps on almost any no-code platform these days. Just do a little research to see what options each platform offers  - and to give yourself a head start, look to see if a particular platform has a template that fits your needs. I'll also be doing more posts about automation apps here on the blog in the near future.

No-Code Websites and Mobile Apps

Of course apps aren't the only thing users can create without knowing how to code. There are a number of popular website hosting platforms like Squarespace, Shopify and Wix that allow you to build a website without doing any coding. You can create an attractive, responsive and feature-rich website with any of them, but your're limited in how you can interact with your users.

With a website, your users have to remember your URL and navigate to it using a web browser. How can you increase your engagement with them? The simplest way is to build a mobile app from your website. Mobile apps have several advantages over websites – they're right there on the user's home page where one click opens up the app, plus you can send them push notifications occasionally to keep them informed about your business.

You can't create a mobile app from your website directly, but there are a number of no-code platforms like Appy Pie or PandaSuite that can do the job for you. They can convert your website into an Android and iOS app which includes features like push notifications, coupons, and the ability to receive in-app payments.

Even if you don't have an app you want to create, no-code platforms can help you to connect with your audience and extend your reach beyond your website. That's another good reason to learn more about the “no-code movement”.

Coming Soon - A New No-Code Book

Coming soon on Amazon - a new guide to no-code app development: Learn “No Code” App Building (Be Your Own Programmer). 

Types of No-Code Applications

There's a wide range of applications that can be built using no-code platforms, but they all fall into the following categories: web apps, mobile web apps, native apps, hybrid apps, and progressive web apps. So, how do you decide which type of app to build? It depends primarily on your target audience and the features you need. In order to give you an idea of how the different categories compare, here a few basic facts about each type of app:

Web Apps

• Web apps are intended primarily for use on desktop computers. They're normally constructed using a combination of HTML, HTML5, CSS, and JavaScript elements and often work in conjunction with an online database.

• The app (and its data) are stored on a web server so you need a browser and an active network connection to access the application. To provide offline access you have to use an SQL-based database API to store data locally and an offline application HTTP cache to make the application available even when the user isn't online. 

• Web apps can be accessed from a mobile device just by directing the device's browser to the app's URL. How the app appears on a particular device and operating system (Android or iOS) depends on how "responsive" the app is - that is, whether it automatically adjusts for different screen sizes and layouts. In some cases a website may provide two versions of a web app - one for desktop viewing and one specially designed for viewing on a mobile device.

• You don't need to worry about whether or not you have the latest version of a web app, since they reside on a web server and everyone accessing the application is automatically using the latest (and only) version of the program.

• If you access a web app from a mobile device, the app isn't going to load and operate as quickly and efficiently as a true mobile version that's installed directly on the device. 

• Web apps don't have to be approved by an app store, so you can launch them faster than mobile apps. However, your app may be harder for potential customers to find since it's not on display in a store.

Native Mobile Apps

• Native apps are built for a specific operating system (Android, iOS or Windows) and are optimized to run as efficiently as possible on that operating system. No-code platforms such as AppyPie, Adalo, GoodBarber, Thunkable, and others let you build mobile apps for Android or Apple and get them into Apple App Store or Google Play Store.

• Because they're installed directly from an app store onto a particular mobile device, mobile apps can access any of that device's built-in functions: GPS, accelerometer, camera, etc.).

• Native apps can work offline since the app lives on the mobile device and doesn't need to connect to a network in order to function.

• Users can feel secure using native apps since the apps have to be checked and approved by the Apple or Google app store before they're made available for download. 

• There is a cost involved in doing business through the app stores.  Google Play Store has a one-time charge of $25 to upload your apps to the store, and they take 30% of whatever price a customer pays for your app as a commission. To use the Apple App Store you have to pay a $99 fee each year, and Apple also takes a commission of 30% of the price the customer pays to buy your app. Note: Apple recently announced that they're cutting their commission rate to 15% for small developers.

Hybrid Apps

• Hybrid apps are basically web apps enclosed in a wrapper that allows them to be installed on mobile devices through an app store, the same as native apps. You can create hybrid mobile apps on no-code and low-code platforms like Appery, AppyPie, and Mendix. 

• Unlike native apps, hybrid apps can run on both Android and Apple operating systems, so you only need to create one version that can be uploaded into both Android and Apple stores.

• Since hybrid apps are actually web apps they generally run slightly slower on mobile devices than native apps.

• While there are a few no-code/low-code platforms that allow you to build hybrid apps, Progressive Web Apps (PWAs) are the becoming the alternative to native mobile apps on many no-code platforms.

Progressive Web Apps

• PWAs, like web apps, are built using elements like HTML, CSS, and JavaScript. More and more no-code development platforms are providing users with the ability to create PWAs.

• Progressive web apps look like native apps but, like regular web applications, they live on web servers rather than being installed directly on a mobile device. PWAs can be installed on your device's home screen by linking the app's icon to its web address.

• Again, like regular web apps, PWAs require a network connection in order to reach the website where they're stored. However, unlike regular web apps, PWAs can operate offline by using a technology called "Service Workers". Service Workers caches data from the website, saves it on your device and displays an icon marking the location where the data is stored.

• Although PWAs share many of the characteristics of a native app, they can only make use of those functions on the mobile device that are supported by web browsers (such as video or audio recording).

Push Notifications: Using Them in Your No-Code App

To be clear, push notifications are messages that pop up on a mobile device. They look like SMS text messages and mobile alerts, but they only go out to users who have installed your app. Push notifications differ from in-app messages in that the user sees push notifications even if your app isn't open on their device (they typically pop up on the user's lock screen), while users only see in-app messages once they open your app.

Why use them in your app? For a couple of reasons. If you're a developer looking to sell your apps, push notifications give you a chance to communicate directly with your customers. Let them know about special features in your app, upcoming events, or new products and thank them for choosing your app. Or if you're part of a development team or you're using the app in a company setting and you need to send and receive messages from other team members or other people in the company, push notifications can handle that too. 

So, what do the notifications sent to customers or other users look like? Web push notifications normally include these elements:

• Title (such as your company or app name).
• Message (brief text).
• An icon, emoji, or image (often used to supplement the message).
• A Call To Action (such as a clickable link or button).

For example, the title might be "Mastering No-Code", with a message "Check out our new universal mobile app template", an image of a cell phone screen with an app running, and a CTA consisting of a link to this blog. 

How you create and manage push notifications depends on the platform you're using and the process can be fairly complicated. In most cases, implementing push notifications is going to require using a plug-in (or "add-on") specifically designed for the job. For example, if you built your app on Bubble you can use the "Firebase Cloud Messaging" plug-in (which costs $12 per application). Most other no-code platforms will have one or more similar plug-ins available and a few may even have push notifications integrated into the platform.

Caspio's Free Patient Portal Template

If you have a need for a comprehensive online patient management app, Caspio has a no-code template that could be your answer. The free template includes a public view, a patient view, and a physician view, and a customizable database that can be stored on Caspio's platform, which is HIPAA (Health Insurance Portability and Accountability Act) compliant. 

Features include:

• New patients can fill out a medical history form online.
• Patients are able to view a list of their prior visits to the facility, along with the results of that visit.
• Patients are able to view messages sent by their doctor or the medical staff.
• Patients are also able to update their profile information at any time.
• Physicians and staff can view a list of the patients (active or inactive) by doctor, including their medical status, insurance carrier and policy number,  and email address, along with details of their medical history, previous visits, and vital signs taken during each visit.
• Physicians and staff members can leave messages for patients, regarding scheduled appointments, medication, advice on treatment, or other information relating to patient care. 

Caspio even suggests some enhancements you could add to the template,  such as email alerts to patients (regarding test results, changes in medicine, etc.) and an appointment calendar that would allow patients to sign up for an appointment on their own. 

One other thing I like about this template is its flexibility. With a few changes you could make this work for a number of situations where you have visitors, members, and administrators. For example, if you need an app to manage a volunteer organization, you could modify the template to handle visitors who might be interested in volunteering, actual volunteers, and supervisors or project managers. Messages could be sent to specific volunteers regarding the projects they're working on, and you could keep a history of which projects each volunteer has worked on and how many hours each one has contributed.

If you're interested, there's a six part tutorial on building the template available on YouTube:

https://www.youtube.com/results?search_query=caspio+patient+portal 

Building a Simple Mobile App on Glide

Glide (www.glideapps.com) specializes in providing users with a quick and easy way to turn their Google Sheets spreadsheet into a mobile app. I should mention that Glide has now added the option to use their internal data tables instead of Sheets, but I decided to go ahead and build my app with Google Sheets as my data source. The app itself is a basic reminder application, to keep track of appointments, projects, articles, or anything that I might want to explore further. Creating the app went like this: 

• I went to my Google Sheets account, created a blank spreadsheet, and added six fields: Keywords, date added, target date, description, location/source, and image. The "keywords" field contains words that relate to specific types of items in the database: blog posts, no-code platforms and tools, sports, space exploration, medical technology, volunteer projects, animal rescue, and so on. The "date added" is self-explanatory, "target date" refers to something like a deadline date or the date of an appointment, "location/source" could be a URL, business address, or the name of a contact, and the "image" field could be a picture of a product, a map, or a screenshot of an app.
• Once the spreadsheet was set up, I entered several sample records in order to have some data for Glide to work with: 
  
  
  
• Next, I signed up for a free account on Glide. A free account allows you to create mobile apps, but you're limited to 500 rows of data and 1,000 sheet updates (changes to your Google Sheets spreadsheet), plus your app is public (open to everyone).
• After I signed up the "new app" screen displayed (you can either click the "+" sign to start from scratch or you can choose to start from a template): 
  
  
  
• I clicked the plus sign, which brought up the option to use Google Sheets as my data source or use Glide's new internal tables: 

• Next, I selected "Google Sheets" as my data source, clicked "Continue", and chose "ReminderDB" as the spreadsheet I wanted to use. Glide connected to my spreadsheet, formatted my app to fit the sample data, and displayed the  result on the design canvas: 
  
  
  
• Clicking on any of the 3 reminders on this screen (the "List" screen), automatically displayed the "Details" screen for that reminder: 
  
  
  
• Glide added basic navigation automatically (note the back arrow on the details screen), along with a search box. And by checking a couple of boxes you can allow users to edit and/or delete entries. Clicking the pencil icon on the details screen brings up the "edit" screen, which also has a button that lets you delete the item being edited: 
  
  
  
• In addition, there were some other options that could be added easily, such as grouping the list items by a particular data field. 
• You can also add various "actions" to the app, such as composing an email, opening a hyperlink, playing a sound, and so on.

Overall, it was easy to build a simple app with Glide, and there were a number of other things I could have done with it. However, I stopped at this point for two reasons: 

•  One, the responsiveness of the app isn't great at times (which is understandable since it's constantly accessing an outside source in Google Sheets).
• Two, using Glide's internal tables would avoid the responsiveness problem, but if you have a considerable amount of existing data there's no straight-forward way (at least that I could find) to import that data into Glide's tables.

I did like working with Glide though, and once they address the import problem it would be one of my top choices for building mobile apps.

How to Market Your App in the App Stores

Once you've placed your new application in the Google Play Store or the Apple App Store, it's time to concentrate on developing your ASO (App Store Optimization) plan. The basic purpose of your ASO is simple - draw as many buyers as possible to your app page. OK, but how do you accomplish that? 

The answer involves a number of factors, including:

• Keywords. Google estimates that 40 percent of apps are discovered through app store searches - which tells you how important it is to make use of the particular keywords that turn up in searches for your type of app. 

• App descriptions (long & short). Keywords also play a part here (even though the Apple store doesn't take them into account in establishing keyword ratings) but the description for your app has to be more than keywords, it has to catch the attention of prospective buyers. Your app needs to offer to solve a problem for them, entertain them, or inform them in some way, and the description is where you need to convince buyers that your app can do that better than your competitors. You're also limited in the number of characters in your description that the potential customer will see on your page, so you need to be concise and make every word count.

Items to include in your description: 

• The purpose of your app.
• A list of the different functions available in your app.
• The types of users who could benefit from using your app.
• Screen shots/Videos.
• Note: Do not include user reviews in your description in the Apple store - they're not allowed.

• App Icon - You may not be aware of it but your app's icon can also influence potential buyers. An icon that's simple and projects the theme of your app helps reinforce the message you're presenting to anyone who lands on your app page. An effective icon can be like the road signs in Europe and elsewhere that get their message across with just a picture.

• Sales (downloads). A large number of downloads shows your app is popular and reassures viewers looking at your page that a good many other people were impressed enough to try it. 

• Reviews. Customer reviews and ratings can have a major effect on how well your app sells - poor reviews can kill your app in a hurry. There are a number of ways to go about asking for reviews:
• Ask readers while they're actually using your app (there are plugins that make it dead simple to do that).
• Offer to activate an extra feature in the app to any reader who leaves a review.
• Take the time to respond to both positive and negative reviews - let your readers know that you care about their opinions.

• Additional resources. Maintain contact with your followers on social media and continue to request reviews from websites and YouTube channels that specialize in discussing new apps.

Keywords are vitally important to getting your app noticed - so how do you include them in your ASO planning?  To begin with, the title of your app should contain the word or phrase most commonly used in searches for apps like yours, which means you need to do a little research to identify that word or phrase. The easiest way to do that is to use Google Keyword Planner (you'll need a Google Adwords account).  Go to the Keyword Planner, enter the keywords you've brainstormed, and check to see which are the most popular. You can also go to websites like Sensor Tower or App Annie, enter the names of some of your competitor's apps, then look to see which keywords they're using to draw traffic to their pages. 

Feedback from your customers can also be key to the success of your app in the Play Store or App Store. Let customers tell you what they like or don't like about the program, whether or not they had problems using it, and what they would like to see added to it. Years ago I had a shareware program on the market and customer comments allowed me to short-circuit a potential problem with a program bug and also led me to add a new feature that greatly improved the application. Listening to your customers not only avoids bad reviews, it provides you with new ideas for your app. 

In addition, along with your contact information, be sure to ask politely for users to leave a positive review if they like the app. Don't be pushy about it, just let them know how much you would appreciate their comments or rating.

That covers the main points about marketing your app on the marketplace. Be sure to spend some time planning your marketing approach (keywords, app description, etc.) before you put your application in the Apple or Android store - and be ready to make changes at any time, depending on how sales are trending.

Note: Look at How to Find Great ASO Keywords for Your App by Kimberly de Silva for more tips on how to find the best keywords for your app.

The Legal Side of No-Code App Building

You've built a really cool app, tested it thoroughly, and you're ready to market it and start making money. You've taken care of everything, right? Well, maybe. One very important detail that often gets overlooked is the legal requirements that may apply to your application.

First and foremost, if your app collects any personal information from the user you're automatically subject to a number of federal and state privacy laws. To be clear, personal information includes almost anything about the user: name, address, date of birth, email address, website login information, bank account number, prescription medications, and much more. If your application (or any third-party service it connects to) collects or has the ability to collect personal information from  its users, you're required to post a privacy policy regarding that ability and post it in a prominent place. That can be prominently displayed on the home screen of your app or anywhere that the user is sure to see it.

OK, so you need a "privacy policy", but what is that? Basically, it's a statement that lets your users know:

• Exactly what type of personal information your app will be collecting and why you need that information.
• How the app will be collecting the user's information.
• How you intend to protect their personal data (although you may want to include a statement that you're not responsible for malware that may extract that data).
• How long you may be storing their personal information and where it will be stored.
• If you use cookies in your app.
• What options the user has as far as restricting the personal information they supply.
• Who to contact if the user has questions or reservations about your privacy policy.

There are several options for creating a privacy policy. You can roll your own, you can consult with a lawyer, or there are a number of websites that can supply you with a template or generate a basic privacy policy for you. It's also a good idea to ask users to digitally sign something stating that they accept the terms of your policy. However you go about it, make sure that if your website or mobile app collects this type of information, make your users aware of it in order to avoid possible penalties or lawsuits.

Makerpad's No-Code Cheat Sheet

 Quick note: Makerpad has a brief summary of no-code terminology, providers, tools, and other information at The Ultimate No-Code Cheat Sheet. It may not be the "Ultimate" cheat sheet, but it does provide a nice overview of the no-code world.

Building a No-Code Mobile App with Adalo (Part 3)

Part 2 covered creating the screen to add new items. The final part of this app allows the user to list the records in the database and to update or delete selected records. 

Special Note: It's fairly easy to accidentally delete a component or entire screen in Adalo. You can usually back up and recover from a mistake like that by pressing the CTRL (CMD on a MAC) and "Z" keys to undo your last action (you may have to do that more than once if you don't catch the mistake right away).

After I added the "List Items" button to the home screen I needed to link it to a new screen that would list all the current records in the Items database. I added a "Link" action so that clicking the button would take the user to a new screen: 

Then I followed these steps to finish building the list and edit/delete screens:

• Once I selected to link to a new screen, Adalo displayed a pop-up with the "new screen" setup information: 
  
  
  
• You can choose different types of screens to create (blank, form, etc.). In this case, I chose a blank screen with an app bar, and added a simple list component to display the item records: 

  

  
  
• You can display two fields from each record. The first or "Title" field is the primary key for your records, which in this case is the keyword(s) field. The second or "Subtitle" field is optional, but I set mine to display the "Date added". To do that I scrolled down to "Subtitle" in the property manager, removed the placeholder text, and used the "magic text" icon (the red capital "T") to connect the subtitle line to the Date Added field in the database records. 
• Quick note: "Magic text" can be used to link fields from one screen to components on a different screen or from one database to another.
• I also wanted the user to be able to search for a certain record by entering one or more keywords, so I added a text input field just above the simple list component and named it "Search". 
• Next, I selected the list component and selected to add a new, custom filter that would display only those records where the keyword(s) contained the text entered in the input box: 

  
• Now I had a list showing the keywords and date added for each item in my database and I had the ability to search for a specific item, but I needed to be able to select a record and display it on a different screen where the user could view it, update it or delete it. 
• The easiest way to create a screen to display an item record was to copy the "Add Item" screen and modify it. To do that I clicked on the "Screens" icon on the left side of the window, selected the "Add Item" screen, and pressed the CTRL and "C" keys to copy it. Then I clicked on the open space next to the Add Items screen and pressed the CTRL and "V" keys to paste the copy onto the design area.
• Once the item detail screen had been created, I clicked on "Form" in it's properties manager and selected to "update the current item" (meaning the item record currently selected on the Item List screen): 
  
• That provides all the necessary functions for the app, except for the ability to delete a record. Rather than set up another screen to do that I placed a second button below the "Update Item" button and added two actions to take place if the button is clicked: one action to delete the record being displayed and another action to transfer control back to the "List Items" screen: 

  

  
  

The actual screens for this (very basic) app look like this: 

Home Screen

Add Item 

List Items

Item Details 

Of course, there are more features available in Adalo, but this should give you a basic idea of how to build a mobile app with Adalo. Here's the URL of the app if anyone wants to try it out:

https://previewer.adalo.com/d21385ed-2e5d-47d0-bb2b-14c4f7c1c112

Building a No-Code Mobile App with Adalo (Part 2)

Part 1  covered signing up with Adalo, creating a blank mobile native app, setting up the database, and starting to work on the different screen displays for the app. At that point there were two screens, a "Home" screen that would act as a main menu and an "Add Item" screen that was still empty. The last thing I did in Part 1 was to add a button on the home screen that transferred control to the "Add Item" screen if it was clicked.

Special Note: It's fairly easy to accidentally delete a component or entire screen in Adalo. You can usually back up and recover from a mistake like that by pressing the CTRL (CMD on a MAC) and "Z" keys to undo your last action (you may have to do that more than once if you don't catch the mistake right away).

The next step is to add the components to the "Add Item" screen so the user can enter the data for a new item: the item keyword(s), the date the record was added, a target date (if any), a description, and a reference (such as a URL). To do I went through these steps:

• First, I added an "app bar" to provide navigation and a place for a screen title. With the "Add Item" screen selected, click on "+Add Component" and drag and drop an app bar onto the screen. Note: A left icon (a left-pointing arrow) is added to the app bar automatically to allow the user to navigate back to the previous screen.
• Next, I found the "Form" component under "Forms & Fields" and added it: 

• Then I connected the "Form" component to the Items collection. Once that was done a form wiith each of the fields in the Items database record displayed on the "Add Items" screen:
  
  
  
• Each field has a label and some placeholder text inside the input box. I didn't need both the label and the input hint, so I went to the left side of the window, selected "> Fields", and selected each field in turn and removed the placeholder text. That helped "clean up" the screen a little, by removing unnecessary text (although, if you had another line or two to fit on one screen you might want to remove the labels instead and gain some vertical space).
• Each field also has an option as to whether or not it's a required field. Since the keyword(s) and the description are the only fields that are absolutely necessary, I changed the option on the others to "not required".
• A "Submit" button is also added as part of the form and you can choose whether to have the app loop back to add another item or return to the home screen after the submit button is clicked. In this case, I had the app flip back to the home screen since I wasn't going to be entering a bunch of records at one time. Note: You can also exit the screen at any time by clicking on the left arrow in the app bar.

Now I had a way to add new items to the database, so the next step was to be able to display existing records and update or delete them. I decided start by going back to the home (main menu) screen and adding another button titled "List Items" that would take the user to a new screen. 

I'll go through that process in Part 3 of this post...