Get Started

1. Start the tutorial to get a first quick overview of MAX
2. Download the free Upvise Simulator to your desktop and the MAX samples to try it yourself
3. Read the Basics section
4. Dive into the API Reference to get complete documentation

Upvise is an Open Platform

Upvise is not only a useful set of mobile applications for your mobile phone it is also an open mobile platform. All of the apps you are using with Upvise actually run on top of this platform. What are the components of the platform?

• The Upvise client is a mobile native application. It acts like a web browser, but provides much more advanced capabilities, such as offline mode, embedded local storage, native RSS, web services support,.....
• Upvise Web Services (UWS), provides the server infrastructure for: storing application data, deploying application updates, providing user authentication,.....
• The Upvise MAX Language, a simple XML file which describes completely a mobile application

Upvise works virtually on all mobile phones

Upvise applications run inside the Upvise client, which is available on virtually all mobile phones and smartphones available today. It works with any Java (J2ME) or Windows Mobile phone.

The Upvise client ensures that the user experience, layout, fonts and storage work the same on a variety of different phones, so you can focus on making a great mobile application for your users, and not spend time adapting to each phone.

If you ever tried to make a Java mobile application or even a .NET Compact framework Windows Mobile application, you know how painful it is to ensure your application works smoothly on 100+ different kinds of mobile phones. This is all what Upvise is about : making mobile application development as easy as making a web site.

Upvise MAX Language: Mobile Application Xml

If you know HTML, XML and web site development, you will find MAX, Upvise's XML language for writing apps super simple yet very powerful.

An Upvise mobile application is basically just one XML file, which describes:

• all the pages or screens in your application
• the navigation between these pages and actions to be performed in response to user action
• the data structure for the persistant data your application, both locally and on the server
• the queries performed (select, update, insert, delete) on these data
• the data binding between the queries and your page