AppWarp Introduction

Multiplayer games and applications are hugely popular and form a significant category of applications in most app stores. The backend for such applications is critical as it provides support for real time data transfer between the user clients and is the fundamental building block for such applications. The problem is that such server side pieces are often error-prone and extremely time consuming to develop. Challenges include developing a high availability architecture, managing multiple client socket sessions and finally the server side business logic required for virtual rooms and lobbies where users interact.

AppWarp is designed to help developers building such multiplayer games and applications by offloading the heavy lifting of developing and deploying the backend. AppWarp client SDKs provides advanced features such as matchmaking, managing intermittent client connection errors, reducing latency by picking a geo location of choice etc. There is a comprehensive development center which offers developers complete guides, tutorials and samples to understand and bootstrap easily.

Developers can concentrate on building their application logic and writing client side code on top of the powerful APIs provided by AppWarp to connect and interact with the backend. Client side SDKs are available for all the popular platforms.

In conjunction with AppWarp, developers can also use the powerful App42 cloud APIs for incorporating other common application requirements such as user authentication, session management and persistent cloud storage to build a complete application through our ecosystem. This is of course optional and developers can use AppWarp independently of App42 cloud APIs as well.

AppWarp Concepts

The diagram below illustrates the high level constructs available to the developer to build virtual world games and applications. A description of all the terms used in the diagram follows.

USER

This represents a client who is connected to the virtual game.
A user’s name must be unique amongst all connected users. It can have different roles such as observer and joined user. Note that while a user can observe multiple rooms, it can join only join a single room at a time.
Developers are also given APIs to set and retrieve custom information for the user to build application specific logic. For example, this could include links to a profile picture or a status message.

Virtual Lobby

This is a special virtual room as it is automatically created by AppWarp backend for you when the application is created. Users can join it if no room exists or if they are unable to join any of the existing rooms.

Lobby Observer

This is a special kind of room observer in that it also has eyes on all the other rooms.
So in addition to the chat and update messages from the lobby, lobby observer also receives join/leave notifications from all other rooms.

Virtual Room

This represents a virtual location where a user can interact with the other joined users.
Developers are given APIs to query all the other joined users and to set and retrieve custom information on the room.
This custom information can be used to build application specific logic. For example as a JSON representation of the current state of a board game being played inside the room.

Joined User

This is a user role which allows the user to interact with other users inside the room.
Such users have the ability to send chat messages and custom notifications to the observers of the room.
Custom update APIs can be used to build application specific logic for example to inform another joined user that it’s her turn to move now in a board game.

Room Observer

Room observer is a user role which receives notifications from the Room.
It gives the user both eyes and ears in to the room. This includes chat messages and custom updates sent by the joined users of the room as well as join/leave notifications.
A user can observe multiple rooms at the same time. This can be used to build spectator like functionality to your application.

AppWarp Architecture

AppWarp server has been developed in a clean and efficient NIO (non blocking I/O) manner. It manages concurrent client connections for the server and provides abstractions for our server side business logic. Below is a high level view of the product design. A brief description follows.