Appery.io Blog

Configuring domain name and ssl certificate in Standalone version of API Express

2018-01-11T05:14:00.002-08:00

Video shows how to setup domain name and ssl certificate in API Express

API Express Standalone version in Docker container

2018-01-04T03:34:00.001-08:00

Video shows how to run Standalone version of API Express in Docker container

Appery.io Login/Logout online/offline Step by Step

2017-12-29T03:56:00.003-08:00

I will show you how to create secured mobile application on appery.io with login/logout features and ability to work in offline mode.

Let’s create Appery database with name LabelDB

Our database will be secured and user’s credentials will be saved in predefined collection Users.

In real application we would have registration page but for our demo app Let’s create predefined users with name

alex and password pass1

And

john with password pass2

Our database will be have only one custom collection with name Labels which will be store short messages.

Let’s create In collection Labels custom column with name label and type String

By analogy with Users collections let’s create two predefined labels

Label-1

label-2

Since we considered information in Labels collection as secured we have mark it as secured.

After that only authorized users will be able to work with it.

Since our application should be able to work offline we have to work with our database via API Express

Let’s create API Express project with name LabelProject

And In LabelProject let’s create generated service with with labels

From list of db connections let’s select predefined database connection with name [Appery.io] LabelDB

Then we need to select collection Labels

Let’s leave everything as it is.

And last step we have to mark our API Express project as secured

On Settings tab enable “Secure REST API” checkbox

Select Security type Security Provider

And select [Appery.io] LabelDB as Security Provider

Now let’s create ui of our application

Create blank ionic application

Rename Screen1 page to Login

And add new page Labels

Property Ng-model of username field is username

And property Ng-model of password field is password

Also we need to add button with Text Login and property ng-click login()

After successful login user will be redirected on Labels page

So here we need to add variables username and password

Application should work with API Expres project for that let’s run API Express extension and select LabelsProject and generate labels generic services.

After refreshing app corresponding API Express services should be added into our application.

Drag and drop AppClientLogin service

And map our application variables on variables of Login service

After successful login user will be redirected on Labels page otherwise he will see corresponding alert message.

On second page user will be see the list of labels

For that we add list element

And specify property ng-repeat as label in labels

And update init method here we have to invoke labels_find services and map $scope.labels variable on success

Since all App Client services are invoked asynchronously we need to invoke $scope.$apply() method manually.

And also let’s add two buttons Login which will redirect us on Login page

For that just specify navigate-to property as Login

And Logout button which also will be redirected as on Login page but before that invoke AppClientLogout method

Don’t forget to invoke $scope.$apply() manually

Application is ready for testing

First let’s test that it works properly online

We provided correct credentials alex/pass1 and were navigated on Labels page where we see the list of our labels with two labels

Let’s press Logout button

Now we are on Login screen and let’s move our application to offline mode it is very easy to do in chrome browser just enable offline checkbox on network tab

First let’s make sure that invalid credentials will not work and provide username bob and password pass3 while everything is correct

And now we provide our previous credentials alex/pass1 and go to Labels page and can see our labels

Network tab is empty and it means that all data were taken from offline storage.

Again let’s press Logout button

And try to login with as second user john/pass2.

AppClient remembers only last user for offline mode so it is impossible to login only as alex

That is it what I wanted to show. Thanks for your attention.

Platform Architecture of appery.io API Express environment

2017-12-29T03:55:00.005-08:00

Platform Architecture of appery.io API Express environment

Appery.io Login/Logout in offline mode

2017-12-29T03:54:00.003-08:00

Video shows how to create secured mobile application on appery.io with login/logout features and ability to work in offline mode.

Appery.io security in API Express

2017-12-29T03:51:00.006-08:00

Video covers the most important aspects security in API Express

- Custom Security
- Security Provider
- Using Users collection of Appery.io database
- Using LDAP component
- Integrating LDAP and appery.io databases

26 Essential Metrics for Successful Mobile Apps

2017-12-06T23:45:00.006-08:00

You have a great app idea and have created a mobile app to share your amazing idea with the world. The app made a great impact initially and marketing activities seem to be attracting downloads. But revenue is declining. What's wrong?

The answer is simple: to make your mobile app a success, you need to constantly improve it. In fact, Gartner suggests a release cycle of 1.5 - 2 months for mobile apps. So how should you identify which parts of your app to improve? For this, application analytics are a must.

Blockchain Basics

2017-12-04T04:38:00.000-08:00

RSA Example

2017-11-30T04:38:00.003-08:00

Illustration of RSA work by example

Around the encryption algorithms with an open and private key there are many misunderstandings and mystifications. Here I would like to show very briefly and clearly, with concrete numbers and minimum formulas, how this works.

I do not go into the theory (it's not very clear what level of preparation the reader should expect), but I'm sure that after reading this short illustration, it will be easier for any person to understand the formulas and strong evidence.

So. Let's say I want to get some data from you. We do not want you to be recognized by anyone other than us. And we do not have any confidence in the reliability of the data transmission channel. Let's get started.

Step one. Preparation of keys

I need to do some preliminary steps: generate a public and private key.

I choose two prime numbers. Let it be p = 3 and q = 7.
We compute the module - the product of our p and q: n = p × q = 3 × 7 = 21.
We calculate the Euler function: φ = (p-1) × (q-1) = 2 × 6 = 12.
We choose a number e that meets the following criteria: (i) it should be simple, (ii) it should be less than φ - there are options: 3, 5, 7, 11, (iii) it should be relatively prime to φ; there remain variants 5, 7, 11. We choose e = 5. This, so-called, open exponent.
Now the pair {e, n} is my public key. I send it to you so that you encrypt your message. But for me it's not all. I need to get a private key.

I need to calculate the number d, the inverse of e modulo φ. That is, the remainder of dividing modulo φ of the product d × e must be 1. We write this in the notation adopted in many programming languages: (d × e)% φ = 1. Or (d × 5)% 12 = 1. d can be equal to 5 ((5 × 5)% 12 = 25% 12 = 1), but that it does not confuse with e in the following narrative, let's take it equal to 17. You can check for yourself that (17 × 5)% 12 is actually 1 (17 × 5-12 × 7 = 1). So d = 17. The pair {d, n} is a secret key, I leave it with me. It can not be communicated to anyone. Only the owner of the private key can decrypt that which was encrypted with the public key.

Step two. Encryption

Now it's your turn to encrypt your message. Let's say your message is 19. Let's call it P = 19. In addition to it, you already have my public key: {e, n} = {5, 21}. Encryption is performed using the following algorithm:

Raise your message to the power of e modulo n. That is, calculate 19 to the power of 5 (2476099) and take the remainder of the division by 21. It turns out 10 - this is your encoded data.
Strictly speaking, you do not need to calculate a huge number of "19 to the power of 5". For each multiplication it is enough to calculate not the complete product, but only the remainder of dividing by 21. But this is the details of the implementation of calculations, let's not go into them.

Received data E = 10, you send me.

Here it should be noted that the message P = 19 should not be greater than n = 21. otherwise nothing will turn out.

Step three. Explanation

I got your data (E = 10), and I have a private key {d, n} = {17, 21}.

Please note that the public key can not decrypt the message. And I did not tell anyone the private key. This is the beauty of asymmetric encryption.

We start to decode:

I do an operation that is very similar to yours, but I use d instead of e. I'll raise E to the power of d: I get 10 to the power of 17 (let me not write a one with seventeen zeros). I calculate the remainder of dividing by 21 and get 19 - your message.

Note that no one except me (even you!) Can decrypt your message (E = 10), since no one has a private key.

What is the guarantee of encryption reliability

The reliability of encryption is ensured by the fact that it is very difficult for a third person (trying to crack the cipher) to compute a private key over an open one. Both keys are computed from one pair of primes (p and q). That is, the keys are interconnected. But to establish this connection is very difficult. The main snag is the decomposition of the module n into simple factors p and q. If the number is the product of two very large primes, it is very difficult to factor it.

I will try to show this with an example. Let's factor the number 360:

immediately clear. that it is divided into two (got 2)
the remaining 180 too, apparently even (2 more)
90 - also even (another two)
45 is not divisible by 2, but the next attempt is successful - it is divided into three (got 3)
15 is also divisible by 3
5 - simple.
We at every step, practically without busting, were getting more and more multipliers, easily obtaining a complete decomposition 360 = 2 × 2 × 2 × 3 × 3 × 5

Now let's take the number 361. Then we'll have to suffer.

it is not even
three - no, not shared
five (for example, we act smartly and only sort out simple numbers, although, in practice, the search for large prime numbers, in itself, is a difficult task) - does not fit
seven? - no.
...
and only 19 will give us the answer: 361 = 19 × 19.

When using large numbers, the task becomes very complicated. This allows us to hope that the cracker simply does not have enough computing resources to break your code in the foreseeable future.

And how does it all work in practice?

Many readers ask how all this is applied in practice. Let's look at a slightly more close to life example. We will encrypt and decipher the word "MOLE", proposed by one of the readers. And at the same time, we will quickly consider what problems are encountered and how they are solved.

First, we generate keys with slightly larger numbers. They are not so obvious, but they will allow us to encrypt not only numbers from zero to 20.

We repulse a pair of primes {p, q} = {17, 19}. Let our public key be {e, n} = {5, 323}, and closed {d, n} = {173, 323}.

We are ready for encryption. Let's translate our word into a digital representation. We can take simply the numbers of letters in the alphabet. We get a sequence of numbers: 11, 17, 15, 19.

We can encrypt each of these numbers with the public key {e, n} = {5, 323} and get the encryption 197, 272, 2, 304. These numbers can be transferred to the recipient who has the private key {d, n} = {173, 323 } and he decodes everything.

A little about the complexities

In fact, the described encryption method is very weak and never used. The reason is simple - encryption by letter. The same letter will be encrypted with the same number. If an attacker intercepts a sufficiently large message, he will be able to guess its contents. First he will pay attention to the frequent codes of spaces and will divide the cipher into words. Then he will notice one-letter words and guess how the letters "a", "and", "o", "c", "k" are coded ... Through a short search, he will compute additional letters for short words like "but", "not ", "by". And for longer words, easily restore all the remaining letters.

Thus, an attacker does not have to guess your secret keys. He will hack your message without knowing them.

To avoid this, special additional algorithms are used, the essence of which is that each previous part of the message starts to affect the next one.

Simpler, it looks like this. Before encryption, we apply a rule to the message: b: = (b + a)% n. Where a is the previous part of the message, and b is the next. That is, our message (11, 17, 15, 19) is changing. 11 remains unchanged. 17 turns into (11 + 17)% 323 = 28. 15 becomes (15 + 28)% 323 = 43. A 19 turns into 62.

The sequence (11, 28, 43, 62) turns out to be "confusing". All the letters in it are mixed, in the sense that each code is affected not by one letter, but all the previous ones.

The person who receives your message will have to do the opposite operation, with the minus sign: b: = (b - a)% n. And only then he will receive the codes of letters.

In practice, random and meaningless letters are added to the original message in the initial message. To even the first code it was impossible to understand anything. The recipient simply discards the beginning of the message.

That is, we can add a random number to the beginning and get (299, 11, 17, 15, 19). After mixing, it turns out: 299, 310, 4, 19, 38. After encryption, it will no longer be possible to guess where there was a letter.

In real life, it's still a little more complicated. Blocks for which the message is longer than one letter. Therefore, first, alignment algorithms are applied, then blocking algorithms with entanglement, and then RSA-encryption itself is applied.

The recipient does everything in the reverse order: decrypts, "unravels" the blocks and discards unnecessary information added just for alignment (so that the message can be divided into an entire number of blocks).

Details and principles of forming blocks can be read here. I in this note wanted to tell only about RSA. Here, it was possible.

A successful Git branching model

2017-10-09T05:58:00.001-07:00

Branching workflow using topic and integration branch

We will be covering the branching workflow with a simple example.

Say for instance, you are currently working on a new feature on the current branch. Suddenly, somebody finds a bug in the production and you are now tasked to fix that bug, parallel to working on the new feature earlier.

Before starting on the bug fix, you would want to create a new branch based off the integration branch. This new branch will isolate the bug fix from the new feature that you were working on.

When you ready to release the bug fix, merge the bug fix topic branch into the integration branch.

Once that is done, you can proceed to switch back to your original feature branch and continue working on the new feature.

On your feature branch, you will notice that commit "X", which is the bug fix commit, is needed in order for you to continue implementing the new feature. In other words, you will have to synchronize your current branch with the changes on the integration branch.

There are two options to go about doing this. The first is to merge the integration branch that includes commit "X" with the current branch.

The second option is to rebase the current branch to the integration branch that includes commit "X".

For this example, we will use the rebase approach which will produce a resulting history that is similar to the example below.

Now that we have commit "X" on our current branch, we can safely proceed to work on our new feature.

As you can see here, branching allows us to effectively work on multiple concurrent tasks.

Column 「A successful Git branching model」

We highly recommend that you check out the article "A successful Git branching model" at http://nvie.com/posts/a-successful-git-branching-model/. It covers one of the most popular approaches for managing Git branching workflow.

The article suggests that we maintain four types of branches, each with different roles.

Main branch
Feature branch (topic branch)
Release branch
Hot fix branch

Main branch

The main branch consists of the master and develop branches.

Master
Codebase residing in the master branch is considered to be production-ready. When it is ready for a specific release, the latest commit will be given a release tag.
Develop
Codebase residing in the develop branch is used in your team's day to day development. This is where all new features are merged to, waiting to be deployed in upcoming releases. This branch is very much like the integration branch that we have described earlier in this section.

Feature branch

The feature branch works like a topic branch which we have covered earlier.

When you plan to start working on a new feature/bug fix, you would want to create a feature branch. A feature branch would normally be created off a develop branch. This feature branch can reside in your local machine throughout the entire development lifecycle of the feature.

You should push this branch up to the remote repository whenever you are ready to merge the change set with the develop branch.

Release branch

When you plan to roll out a new release, you would want to create a release branch. A release branch helps you to prepare and ensure that the new features are running correctly.

By convention, release branch names normally start with the prefix "release-".

The release branch is typically created off the develop branch when it becomes close to being production-ready.

Only bug fix and release related issues should be addressed on this branch. Having this branch would allow other team members to continue pushing new features to the develop branch without interrupting the release workflow.

When you are ready to release, merge the release branch with the master branch and tag a release number to the newly created merge commit.

You would also want to merge the release branch into the develop branch, so that both the master and develop branches receive the latest change/bug fix from the release branch.

Hot fix branch

When you need to add an important fix to your production codebase quickly, you would want to create a Hot fix branch off the master branch.

By convention, hot fix branch names normally start with the prefix "hotfix-".

The advantage of a hot fix branch is that it allows you to quickly issue a patch and have the change merged with the master branch without having to wait for the next release.

A hot fix branch should be merged with the develop branch as well.

Original

JSONPlaceholder

2017-10-06T06:27:00.004-07:00

JSONPlaceholder is a free online REST service that you can use whenever you need some fake data.
It's great for tutorials, faking a server, sharing code examples, ...

Example

Run this code in a console or from anywhere (CORS and JSONP supported).

var root = 'https://jsonplaceholder.typicode.com';

$.ajax({
  url: root + '/posts/1',
  method: 'GET'
}).then(function(data) {
  console.log(data);
});

Response example

{
  "userId": 1,
  "id":
        1,
  "title": "sunt aut facere repellat provident occaecati excepturi optio reprehenderit",
  "body": "quia et suscipit suscipit recusandae consequuntur expedita et cum reprehenderit molestiae ut ut quas totam nostrum rerum est autem sunt rem eveniet architecto"
}
    

Resources

Inspired by common use cases.

/posts	100 items
/comments	500 items
/albums	100 items
/photos	5000 items
/todos	200 items
/users	10 items

Routes

All HTTP verbs are supported.
View usage examples.

GET	/posts
GET	/posts/1
GET	/posts/1/comments
GET	/comments?postId=1
GET	/posts?userId=1
POST	/posts
PUT	/posts/1
PATCH	/posts/1
DELETE	/posts/1

RSA

2017-10-06T03:37:00.003-07:00

RSA Key Generator

RSA (Rivest–Shamir–Adleman) is one of the first practical public-key cryptosystems and is widely used for secure data transmission.

Key Size

Generated in 24 ms

Private Key

Public Key

RSA Encryption Test

Text to encrypt:

Encrypted:

Scrum

2017-09-19T07:54:00.002-07:00

Scrum is a framework for managing software development. It is designed for teams of three to nine developers who: break their work into actions that can be completed within fixed duration cycles (called "sprints"), track progress and re-plan in daily 15-minute stand-up meetings, and collaborate to deliver workable software every sprint. Approaches to coordinating the work of multiple scrum teams in larger organizations include Large-Scale Scrum and Scrum of Scrums, among others.

Blockchain

2017-09-15T12:30:00.005-07:00

SHA256 Hash

Continuous Integration vs. Continuous Delivery vs. Continuous Deployment

2017-09-14T03:03:00.003-07:00

Continuous integration
Developers practicing continuous integration merge their changes back to the main branch as often as possible. The developer's changes are validated by creating a build and running automated tests against the build. By doing so, you avoid the integration hell that usually happens when people wait for release day to merge their changes into the release branch.

Continuous integration puts a great emphasis on testing automation to check that the application is not broken whenever new commits are integrated into the main branch.

Continuous delivery
Continuous delivery is an extension of continuous integration to make sure that you can release new changes to your customers quickly in a sustainable way. This means that on top of having automated your testing, you also have automated your release process and you can deploy your application at any point of time by clicking on a button.

In theory, with continuous delivery, you can decide to release daily, weekly, fortnightly, or whatever suits your business requirements. However, if you truly want to get the benefits of continuous delivery, you should deploy to production as early as possible to make sure that you release small batches, that are easy to troubleshoot in case of a problem.

Continuous deployment
Continuous deployment goes one step further than continuous delivery. With this practice, every change that passes all stages of your production pipeline is released to your customers. There's no human intervention, and only a failed test will prevent a new change to be deployed to production.

Continuous deployment is an excellent way to accelerate the feedback loop with your customers and take pressure off the team as there isn't a Release Day anymore. Developers can focus on building software, and they see their work go live minutes after they've finished working on it.

Appery.io Binary data in API Express (Generated services)

2017-08-30T02:59:00.001-07:00

API Express provides powerful and flexible mechanism of working with binary data.

API Express uses JSON format so to work with binary data it is used Base64 format (you can read more about that by following link https://en.wikipedia.org/wiki/Base64 )

For testing you can use Base64 Converter to convert ordinary string to string in Base64 format and vise versa.

Binary data in Generated Services

API Express provides embedded support of Binary for Generated services.

Fields with type BLOB in generated services are considered as Binary
Operations get and list will convert value of this field into Base64 String
Operations create and update will accept String in Base64 format and API Express will save converted binary into database.

To understand better how it work let’s consider example

Relational database has table files with columns id, name and content

id - unique identifier of files name - file name content - file binary content
Following DDL scripts can be used for

MySQL

CREATE TABLE files 

( id INT NOT NULL auto_increment PRIMARY KEY, name VARCHAR(64) NOT NULL, content BLOB NOT NULL )

Postgresql

CREATE TABLE files

( id SERIAL PRIMARY KEY, name VARCHAR(64) NOT NULL, content BYTEA NOT NULL )

MSSQL

CREATE TABLE files

( id INT PRIMARY KEY IDENTITY, name VARCHAR(64) NOT NULL, content VARBINARY NOT NULL )

Oracle

CREATE TABLE files ( id INT PRIMARY KEY, name VARCHAR(64) NOT NULL, content BLOB NOT NULL )

It is assumed that already exist Database Connection to Relational database.

To work with table let’s create API Express Generated service

On Test page we can check how our services are working

1. Create record in files table.

name of our file will be test.txt

file will contain only sentence test message in Base64 format it is IHRlc3QgbWVzc2FnZQ== Request payload { "name": "test.txt", "content": "IHRlc3QgbWVzc2FnZQ==" } Response of operation create { "content": "IHRlc3QgbWVzc2FnZQ==", "id": 1, "name": "test.txt" }

If to take a look on this record in database client we would see that in database sentence test message was saved

2. Get record from files table.
Operation find will return just created record if to pass file name test.txt in query { "name": "test.txt" } Response of operation find is [{ "content": "IHRlc3QgbWVzc2FnZQ==", "id": 1, "name": "test.txt" }]

Base64 Converter

2017-08-29T06:03:00.002-07:00

Base64 is a group of similar binary-to-text encoding schemes that represent binary data in an ASCII string format by translating it into a radix-64 representation. The term Base64 originates from a specific MIME content transfer encoding.

Each base64 digit represents exactly 6 bits of data.

Base64 Wikipedia

LDAP component

2017-08-28T05:35:00.001-07:00

Most apps require a user to register and login with credentials. Most often, the app requires that the user create a user/password that is specific to the app. This is a cumbersome process that requires the user to remember yet one more password. It’s also not very secure.

A much better approach is to enable the user to simply log in with existing credentials from another service that is trusted, like an LDAP directory in an enterprise

LDAP, or Lightweight Directory Access Protocol, is an internet protocol that programs use to look up information from a server. LDAP can be used to look up encryption certificates, pointers to printers and other services on a network, and provides “single sign-on,” where one password for a user is shared between many services. It’s typically used by enterprise organizations.

Appery.io offers powerful and flexible mechanism of creating secured mobile applications which use your LDAP.

To understand how it works in details let consider example

In this tutorial we use testing LDAP server http://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/

Create API Express project with name SecuredProject
Go to Settings sub tab
Enable Secure REST API
Select Security type Custom service
Came back to API sub tab
Open login service in system folder (just press edit link)
Remove default SCRIPT component from flow
Add LDAP component instead
Provide following values for properties of LDAP component

Provider type: LDAP
Host: ldap.forumsys.com
Port: 389
User DN: cn=read-only-admin,dc=example,dc=com
Admin Password: password
Username: BODY.username
Password: BODY.password
Base DN: dc=example,dc=com
Object classes: person
User login name field: uid

Press Generate button to make sure that configuration is correct
In open popup specify

Username: riemann
Password: password

Press Run LDAP button
Response field should be

{

"status": "success",

"session": {

"userId": "riemann",

"userName": "riemann"

}

Press Import Response button and Save button
Press Test button
In new opened window specify Request body payload (data).

{

"username": "riemann",

"password": "password",

"options": {}

}

The response of login service should look like

{

"sessionToken": "f735cb5d-ea48-4fca-be2e-9ebfdd98e6ca"

}

It means that we successfully logged in our project and got session token which can be used subsequently to perform rest calls to another services of this project.

i18n

2017-08-28T00:49:00.005-07:00

Example of using i18n in appery.io

Appery.io Login/Logout in offline mode

2017-07-19T00:27:00.000-07:00

Video shows how to create secure mobile application with ability to work offline.

REST concepts

2017-06-14T01:10:00.000-07:00

Representational state transfer (REST) or RESTful web services is a way of providing interoperability between computer systems on the Internet. REST-compliant Web services allow requesting systems to access and manipulate textual representations of Web resources using a uniform and predefined set of stateless operations. Other forms of Web service exist, which expose their own arbitrary sets of operations such as WSDL and SOAP.

Appery.io platform overview

2017-05-11T07:47:00.000-07:00

Appery.io is the first mobile platform that offers a cloud-based rapid development environment with integrated backend services and a rich catalog of API plug-ins.

App Builder

Appery.io is visual IDE for creating mobile applications by dragging components, selecting from pull-down menus, and «connecting the dots» between backend systems and user interface controls. Browser-based development enables real-time collaboration between developers,

designers, and business users. Developers can create reusable assets that can be in the form of API plug-ins for integration to backend systems, custom components for the user interface, or application templates.

Frameworks

Appery.io is based on industry-standard languages and frameworks. Developers can code using HTML, JavaScript, and CSS, so the applications are portable across any platform. In addition, Appery.io leverages Apache Cordova and any third-party Cordova plug-ins to create native or hybrid apps that support native device capabilities. The platform leverages the very popular jQuery Mobile framework with a rich set of UI components.

Application Security

Appery.io delivers enterprise-grade security with our optional Enterprise Mobile Safe secure container. Apps are deployed in a secure container on the device and connected to a secure server, protecting all app artifacts such as data, code, and content with AES-256 encryption. Appery.io can also integrate with third-party secure container and enterprise app store solutions.

Integration with Enterprise Systems and Cloud APIs

Appery.io integrates easily with any available REST API without the need for coding. Developers connect the dots using a visual interface to map data between the application and the backend system. The Appery.io Enterprise Integration Server offers integration with backend systems including LDAP directories; relational databases such as Oracle, Microsoft SQL server, MySQL, and PostgreSQL; and CRM systems such as Salesforce.com, REST APIs, and SOAP-based web services.

Integrated Backend Services (MBaaS)

Unlike point tools and other Mobile Backend-as-a-service (MBaaS) providers, Appery.io offers a complete platform with tools for designers and developers along with integrated backend services.
Appery.io backend-services include a cloud database (based on MongoDB) to store app data and manage users and files, a server code engine to support server-side business logic, and a push notification service to engage users even when the apps are not running.

Team Management and Real-time Collaboration

Appery.io team management capabilities enable team leaders to invite colleagues by sharing (and unsharing) user seats for the platform and by sharing (and unsharing) projects.
Because the development environment is web-based, with projects stored in the cloud, multiple users can view and mofigy applications at the same time.

Key features

Cloud-based visual development environment with optional coding using JavaScript, HTML, CSS
Integrated backend services (MBaaS) including a cloud database
Visual integration to third-party REST APIs
Prebuilt plug-ins to enterprise systems and cloud services
Real-time collaboration
Secure container for enterprise-grade security
Complete platform with support for entire app lifecycle
On-premise and cloud-based deployment options
IOS, Android and HTML5 responsive applications

Appery.io on TIBO 2017

2017-04-20T07:43:00.000-07:00

I had a chance to present Appery.io on TIBO 2017 24th International Forum on Telecommunications, Information and Banking Technologies that is to take place in Minsk, Belarus on 18 – 20 April 2017

Held since 1994, TIBO is one of the biggest exhibition events in the CIS and the Baltic states. The forum gathers the leading Belarusian and foreign producers of telecommunications equipment, computers and software, security systems and devices, suppliers of ICT services. TIBO 2016 brought together more than 100 companies from 18 countries: Belarus, Russia, Ukraine, Kazakhstan, Azerbaijan, Latvia, Lithuania, Poland, the Czech Republic, Germany, Finland, Sweden, the United Kingdom, Turkey, China, the Republic of Korea, Japan, and the United States.

Appery.io MeetingRoomCalendar app in Exadel office

2017-03-21T23:52:00.000-07:00

Finally we installed in Exadel offices MeetingRoomCalendar application which were created on appery.io

Training - Introduction into Appery.io platform

2017-03-16T08:00:00.000-07:00

I had a chance to conduct training "Introduction into Appery.io platform"

1. Appery.io intoduction (history, example of apps created on appery.io few words about team and etc)
2. Explanation of basic principles of our platform (why it is a platform, explanation what is hybrid apps pros and cons)
3. App Builder
4. Database
5. API Express
6. Security
7. Server Code
8. Push notifications
9. Autoupdate
10. Offline
11. Showing sample app from our tutorial
12. Conclusion
13. Questions and Answers