Synchro allows you to create feature-rich, robust, and secure cross-platform mobile apps that look and feel native on mobile devices, but run on the server, and are updateble in real-time. And it allows you to do this in a fraction of the amount of code required by other mobile application development platforms.
To the user a Synchro-built app presents as a no-compromise native mobile app, and to developers and administrators it presents as a web app. It's really the best of both worlds.
The short answer is that we do this by rendering your mobile client user interface on the mobile device, but running all of your mobile client code, including user interaction logic, on the server. You provide a small amount of platform-neutral UX code that we run on the server, and the Synchro platform provides the native mobile code and server framework to make it all work.
In this pattern, each page or screen is represented by a View that defines the presentation of the user interface, including controls and their layout, and a ViewModel that contains the data represented in the View, as well as commands to process user interactions with the View. The View definition also contains declarative bindings that describe the relationship between the View and the ViewModel (for example, which ViewModel elements are used to populate which View controls, and which ViewModel commands are launched when users interact with various controls in different ways, etc).
These declarative bindings allow us to fully automate the View, meaning that there is no need for you to write any procedural code to get or set View contents or state, and this is what allows us to render and run the View on the other site of a network connection from the ViewModel. Also, unlike many other MVVM or similar systems, we don't require you to do anything in your ViewModel implementation to make this happen (you don't have to notify anyone when you make a data change, and you don't have to tell us which data elements we need to observe - we just figure it out and handle it automatically).
The diagram above shows how we implement our client-server MVVM solution. Your Synchro app will consist of a View and ViewModel implementation on the server. The Synchro platform provides the native mobile client apps and the server infrastructure to make the magic happen.
For more details, including implementation examples, visit our Documentation site.
The code that runs on the mobile client is created and provided by us, and is not specific to your application. We offer that code, packaged for you, linked to your server endpoint, and branded as your app, on Android, iOS, Windows, and Windows Phone platforms via the Synchro App Builder. Your code runs on the server and is the same regardless of the client OS your user is running. You do have the ability to tweak and tune your app based on the mobile client OS (or other device metrics), but that's usually not necessary.
We were frustrated in our own efforts writing enterprise mobile clients by the amount of code required that was not core to the focus of the application. Most of this code fell into one of two categories: UX babysitting (setting up the UX and populating it, writing various handlers, notifiers, etc), and the client side of network client-server functions (typically talking to our own servers, usually via a REST API or some third-party tool that was supposed to make it easier). In Synchro, we have dramatically reduced, and in many cases completely elimiated, the code required in both of those categories.
In one popular cross platform benchmark, the PropertyCross application, the Synchro implementation was done in 1/20th the amount of code of the native implementation, 1/10th the amount of code of the Xamarin implementation, and 1/4 the amout of code of the Appcelerator Titanium implementation. And our version stands up to all of them in terms of native look-and-feel, functionality, and responsiveness.
The Synchro implementation of PropertyCross is 242 lines of code, and that includes the view templates that define the page layouts. Another Synchro app, Synchro Civics, was implemented in under 200 lines of code. To install Synchro Civics on your mobile device and see what can be done in 200 lines of code, see Get Started.
Most enterprise mobile applications are client-server applications that revolve around the mobile client application interacting with one or more existing enterprise resources (services, data sources, etc). Implementing the client side of these interactions introduces many challenges, including authentication, access-control, connection/network management, state management, caching, and more.
Consider a simple example: You have customer data stored in a SQL database, and the mobile application needs to be able to search that database and display that customer data. If you implement something like this as a web app, your web app will simply authenticate to the database (as an application), perform a query, and populate the response with the data. But you can't very well let a mobile app talk directly to a SQL database for a number of reasons. You can't distribute application-level access credentials to the mobile app (that it stores and uses for access). Since the mobile app has its own release schedule, you can't have it rely on a specific database schema. For these and other reasons, you will typically end up building some kind of front-end to the database for your mobile app to use (either building a custom REST API, or perhaps by using some third-party tool to help). And that creates its own set of issues, including per-user access control, API versioning, network/connection management, etc.
With Synchro, because your mobile client application logic is running in a server environment, much like a web application, that code can talk directly to your enterprise resources without that extra layer of client-server logic. Your mobile app code will look a lot more like the clean, simple web app version of that application.
In the Synchro model, the mobile client communicates with a single Synchro endpoint over a secure connection (in fact, the mobile client device cannot communicate with any other server or network endpoint). Other than a session token, the mobile client does not maintain any local state (no local data storage, no cached data, etc). None of your data is exposed on device storage or over the connection. And since Synchro apps are running on the server, you can monitor usage and even revoke the ability for any or all users to access the application, in real time.