Ιnstructions

The ExpandCom manual

Version:

0.2.2

What is ExpandCom and what can you do with it?

ExpandCom is an application platform that uses only open source applications and techniques such as (IoT, Rest API, etc) so that it can ΙΤ expand - merge - create, professional processes safe - easily and quickly.

For example, in an ERP system that does not have POS and portable pricing it can be expanded with ExpandCom and use these capabilities as well.

With ExpandCom you can do:

  • Extend your already existing commercial app

  • Automate your business processes

  • Get directly (IoT) information to you and your colleagues

  • Join already existing platforms (ERP, CRM, PBX, eSHOPS)

What you need to know

  • Basic knowledge of operating systems (win, * nix, android), file system, permissions, services, etc.

  • Basic knowledge HTTP and REST API

Cost

ExpandCom only charges for what you actually use.

This is calculated from the internet and storage resources consumed by your app usage. The specific resources are calculated at the end of each day and the relevant points are deducted from the available ones. As long as there are points from cash payment the ads are disabled.

E.g. for someone who uses a ready-made platform (1st category General use) and has not had any traffic for a day, its charge would be a few points for the current needed to keep the app running.

The credit to use the service is done in points (p) and can be done through Ads (10p/ads) or with cash (100p/€1). The admin is responsible for the points and can add via cash. Users can too to put points on the platform by viewing ads.

When points are cash, no mandatory ads are displayed.

We try not to disturb the user because of the ads and if you find something annoying let us know so we can look into it.

Components

The basic components for using the platform are two (2) and they are:

  • the Node and

  • the Android client

Node

The node is actually the server that lives in the cloud. In essence, that is the "referee" of how the data will be transferred between them component of the platform (Android client, worker, etc.) Through it, rights and rules are defined. You are not required to run the clients but when there is a process controlled by him it is natural to have a connection.

The node has communication with external providers such as google for credentials users, telegram for IM between users and applications, ipfs for shared file system.

Android client

It's the user's GUI to see, change the data. To the 99% of its operation it does not require a permanent connection to the node unless there is a process you control from the node.

Administrators can directly (remote) access the client without using a third-party application simply by posting, for example:

Worker

The worker is a micro-application (java) that runs autonomously without installation. Its purpose is the interaction between the node and a device (printer, cashier, scales, etc.) or a database or what you think.

# worker's expandcom.cfg config file
# you automatically created the first time you run the worker
# with the required values
# at the site you are running the worker

device = 1c5209e4-cc85-4f77-8250-111
prefix = demo
hostname = worker_demo
host = https\://demo.expandcom.net
timeout = 100

The access_token value can easily be taken from it OAuth 2.0 Playground or with any another method you want.

User GUI [1]

It's optional in use, it just has the ability to give the user one environment exactly as he / she wants. It's an application written in any programming language it uses the library proposed by us and communicates directly with the Android client or with the node.

Extra help

Features

ExpandCom provides the following features:

  • Connectivity with any system via REST API.

  • IoT, immediacy of information.

  • Multi platform, work in an end-user environment (GUI), in any system (M$, nix*, Android, iOS, www, other?)

  • Custom procedure, at server level (for everyone) and in client (each one)

  • Standalone, use it without any obligation or commitment with cloud connectivity

  • Unlimited users for medium or large businesses will not need anything. In special cases you will contact us for better implementation.

  • Take control over the application itself to find out what's going on and give immediate solution without our intervention.

  • Now you have all the reports on any device and customized to your measure.

Created a Node

In its creation the creator of the service gets the right of the owner. This is now the first in the hierarchy that defines roles (admin, seller, etc) to users for each additional application separately.

Each additional app-plugin has its own roles and rules. All users are considered visitors until a role is assigned to an additional application, such as "admin" in the "Warehouse" in user@gmail.com.

The figure defines permissible roles, for example:

{
    "schema": {
        "username": {
            "type": "string",
            "unique": true,
        },
        "role": {
            "type": "list",
            "allowed": ["admin", "seller"],
        },
    }
}

This entails some functions specific to this user and is detailed in the instructions of each plugin.

Read more about user roles bellow.