Ibeyonde - Create and Launch

Welcome To Ibeyonde ΔApp Builder

A exciting world of delta apps await you !

This document covers the creation, hosting and distribution of your responsive html 5 apps (referred here as Delta Apps of ΔPP) . If you have any questions that are beyond the scope of this document, feel free to email at info@ibeyonde.com Thank you so much!

ΔPP Features

  • Clean & Simple Design
  • Fully Responsive Design
  • Flexible Data format
  • Require no-installation
  • Remember Me Enabled
  • Extensive Documentation

Ibeyonde - Create and Launch


The platform provides tools to create documents that can do interaction with knowledgebase to render content that is contextual and relevant to the audience. The documents/app are responsive and allow sophisticated data collection. The communication does not end with the document but continues from the platform that leverages text and email messages to keep the user posted. The platform also provides tools that can pull user information, using contactless method, say form example on the registration desk.

Following are the ΔPP differentiators.

  1. Flexible format: ΔPP platform has a flexible self-service content platform. This allows you to focus on what you want to communicate with the customer. You focus on your flow of such conversation and use ΔPP to put that in place.
  2. Lightweight and require no-installation: These do not require any installation by the user. These are delivered as minified links. Although these are lightweight they have inbuild user authentication, by user email or mobile OTP. There are many skins to choose from.
  3. Conversational: ΔPPs are build for having dialogues with your customers. The dialogue can happen within the ΔPP or outside it. The conversational SMS and email are built into these apps. You can reach out to the customer on his choice of the medium.
  4. Multiple Formats: ΔPPs can be delivered in multiple formats. They are delieverd as reactive web-pages, which can run on mobile, tablet or laptops. They can also be delieverd a chatbots that can be embedded in a web-page. You can also design a text only ΔPP that can be activated as a text-bot say over mobile SMS. This gives the flexibility of design once and run everywhere.
  5. Flexible Database Schemas: Since the ΔPP is capable enough to capture various pieces of information over text or over web-form, these specialize in massaging, and validating the data. This free-format data can be arranged in schemas, where it is easy to order and arrange the columns. A suite of online database mangement tools help you manage you instance of the database. Your db instance is physically iscolated for security. The existing data can be edited online or downloaded as CSV file.
  6. Installation/Validation: ΔPPs can be saved as bookmark on the device of interest. ΔPP calculate the signature or user and device to avoid asking for unnecessary validations. This model is as powerful as any of the installable native Apps.

Getting Started

ΔPP is the platform to create and host your delta mobile, web and text apps. Delta apps encapsulate a conversation that you want to have with your customer. It could be a simple one like a survey, i.e., set of questions. It could be an appointment making system. It could be an e-commerce app with payment included. Bottomline, it gives you the power to reach out to your customer with a micro-website without the need to worry about domain-name, databases or hosting. You bring in your idea of what you want your customer to see and respond and rest is taken care of by the ΔPP platform.

Graph and Nodes

At the heart of the ΔPP is an intelligent engine that breaks down the typical conversation into fundamental elements - 1. a message and 2. the actions on users response. A graph lets you visualize the conversation flow. Each node of the graph captures a particular interaction. So a node could post a message and look for acknowledgement, or a node could offer choices like in a multiple-choice question, or a node can ask for email id. Depending on user action/inputs, the conversation moves to the next node.

Knowledge Base(KB)

The conversation is embellished by the Knowledge Base(KB). The KB is uploaded as CSV file. The KB console lets you view and maintain the KB. For an appointment system for a healtcare org, the KB is list of branches, departments, speciliaties and doctors that are part of KB.

User Data(Data)

The Data console shows information captured as the conversation proceeds. A transaction id or mobile number or an email id acts as the key to the customer data. The ΔPP uses Data and KB to make conversation more insightful and interesting. The Data is free format, it is created and organized as user data comes in. You can add comments to the Data or use the email or mobile to communicate with the user from the Data console. Many a times it becomes important to be able to quickly narrow down on user information. For this purpose we provide Data Scanner App.

App Branding(Images)

To make the app look nice, use the Image store to upload the images. These images available in your Image store can be dropped in appropriate nodes to make the message conform to your brand or to convey the message more effectively.

Payment Processor

Provide your razor pay credentails to enable pay button on the apps.


A ΔPP encapsulates a conversation that you want to have with your customer. Each customer interaction is a conversation of some sort. You may be planning to sell your goods, or you may be just soliciting some information from somebody. These conversations are represented as a graph. A node on the graph, consists of a message and the actions. For example, you may present a catalogue of your product to the customer, and as a response, the user selects one item. You may then ask the user whether he is interested in buying it, and so on.

Figure showing the visualization of a conversation, in this case The Montblanc Catalog

To support such conversations, you need a knowledge base (KB). A KB, in this case, is list of products with the pricing, picture and description. To create a KB you need to list it in a CSV file and upload it in the KB section of the Dashboard. The Image section for Dashboard lets you organize Images of your products. You can upload upto 100 images. The KB, Images and Data (ie, past user choices) let you frame your Messages. We can define a message as HTML content that has placeholders that are substituted from KB, Images and user Data. All the choices or inputs that the user made are captured in the Data part of the dashboard. With all this information, the tools will help you put together the Message. Once the Message is presented to the user, the user will be offered ways to respond. These are captured as Actions in the ΔPP. There are three different ways to respond:

1. Button click of some type that results in transition to some next node. For exammple, you can add a next button that takes the user to the next message or a back button or a button with a name that takes him to a specific message(node);

Figure showing a button "Listing" that takes the user to the listing node.

2. A dropdown or user selects from a set of choices, created from KB, like selecting a particular model of the product;

Figure showing a dropdown for various models. On selecting the choice is saved in Data and the node moves to the item node.

3. An input text from which email, name, address, phone number or DateTime is extracted and stored in Data console.

Figure showing a the input text field to take contact information. The inputs text is massaged and validated and stored in Data.


A message is what you want your customer to see and respond to. The message editor lets you put together a message that is constructed from HTML that you provide and information that is already available. The available information includes the KB, the Data and the Images. The Online editor lets you modify the message and see it as it will appear to the app viewer. You will need basic understanding of HTML to work with the editor.

Figure below shows the editor section of the online workbench

Figure showing the online html editor

The second thing you need to deal with at this time is a placeholder. There are two types of placeholders:

User Data

User data is massaged responses that are captured, for example, like his name, email etc. If you have asked the user for his name, then maybe at some point you want to address him by name. To do that, you will add a "name" placeholder which is replaced at runtime.

You can type the name of the data item and click add. This will add the data placeholder in the message. A placeholder is a pattern surrounded by {{}} for example {{mydb/user_data/value/item4/}} . This particular placeholder will look for the value of item4 in Data and replace it in the message. See how this value is captured in Actions.

KB Data

A placeholder that represents data in the KB. You will need to place this when you want to list down items from the catalogue that you have uploaded in the KB. It can be conditional, for example; you want to display the category that the user has picked in a previous step.

For example, this pattern {{db/catalogue/desc/name=:item/}} , represents the description of items whose name matches the choice that user made in the previous step this choice is stored in Data as "item". In the wizard pick up the schema that you want queried. Then click on the relevant column. Optinally you can add a condition that checks the KB against the data collected. For example name=:item will look for items under the condition that name of such item is same as the one the user specified when he selected item .


You can upload images and then add them to your message to make it more expressive. From the top menu goto Images and upload images that highlight your brand and messages. You can upload upto 100 images of upto 1MB each.

The image tool accessible form the Message editor lets images that you have uploaded to be added to the message. The image by name "logo.png" "logo.jpg" is picked up and displayed as a logo in the ΔPP header.

The work bench lets you customize the Message in ways that the it reflects your brand truely. We are also in the process of adding HTML WYSIWYG editor so that the user need not deal with raw HTML


Actions are put in place to guide the user's response. So when an item is shown to the user, that he wishes to own. The actions that are put in place guide him to make that decision. Few well-designed primitives give the flexibility to create such actions. The user may decide to navigate to some other view, or he may provide keyboard input, or he may pick up one from a set of choices. Multiple such actions are put together in a message. For example, a user may want to just cancel the whole process and go back to revewing other items or he may decide to go ahead with purchasing the item.
Finally, it boils down to these actions.


A simple unconditional transition to the next state. This will add a button that takes the user to next message/screen. The message on the button says "Next".


An Extract is used to derive information from user's input. An extract action gives you a text input box. It is primarily used to get free-form information from user for example, email, name, comments, date-time etc. The extract action is associated with a extract type pattern. The wizard will help you in filling up the type you want. You may want to extract an email from user response, then you choose extract type as "email" from the right extraction wizard. On clicking add a relevant pattern will be added to the extraction field. A extraction pattern form email will look like {{ex/email/string/email/}}. This value can be addressed in the Message.


A Choice is repsented by a list of items. You can type that comma seprated list in the Choice List field OR the choice can also come from KB. In second case the Choice wizard on the right will help you create that pattern. The second part of the Choice action is the data extraction. The wizard let you provide that variable that will take the choice from user and save it in Data. If the choice list is less than three items then it is converted to equivalent search. For example if the choice is just yes or no then it will be converted to buttons intead of a dropdown.


A upload is an action that can ask user to take a picture or a file and upload it to.

We have left Intents out. Intent requires setting them up. If you want to explore Intents then please get in touch with us. The Intents lets you filter user responses to understand the significance of their text and accordingly direct them to right direction. The Hospital appointment system uses intent to understand the department the user needs to be directed in order to get the right appointment. Intents are backed by Machine Learning.
The actions cover all the possibilities. They are backed by machine learning and AI in order to extract meanigful formatted information from user actions.