Appery.io Blog

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

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

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 AP

Platform Architecture of appery.io API Express environment

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

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

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.

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

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