ASP.NET Web Based ‘Controller’ to replicate Android app behavior

Cancelled Posted Jul 12, 2013 Paid on delivery
Cancelled

Web Based ‘Controller’ to replicate Android app behavior:

Android App Background

We need to build a web based method to replicate the same behavior we already have in an existing Android App built in MIT App Inventor. In the Android App, instead of using native controls for the user to interact with, it has no UI other than a web viewer control it loads a series of html pages in. The loaded pages are built on jquery mobile to provide UI for the app. The Android app has a ‘controller’ mechanism where:

• looks up a table record in the database so it dynamically knows which page to load next;

• when a UI page is loaded, data is passed into it via the query string. This query string data is dynamically generated by the controller by looking up values in the database.

• Data is passed back to the controller from the page by that page modifying its own page title DOM element (i.e [login to view URL]) with one or more sql statements for the controller to run on its behalf.

• After loading a page, the controller waits on a timer and checks periodically to see if the loaded page’s title has changed. If it has changed, it runs the sql statements the page outputted via the page title change, then looks up a database table to check for what page to load next.

• One of the sql statements that the page wants the controller to run will put an entry in the table in the db for what page to load next. If no entry is found by the controller for where to go next, it will just load the default home page instead.

• This is repeated until a page sends a special ‘exit program’ command.

Replicate Android App behaviour on the web:

We want to replicate this functionality on the web and at the same time use the same set of html pages used in the Android app for the UI. This way we can offer the same functionality as an offline Android app or provide it directly on the web via this new approach.

The proposed approach is to use a single scripted aspx page that will act as the controller. For UI, the page will contain an iframe with 100% width and height. This iframe element will play the role of the web viewer control. All other aspects of how the controller manages page loading etc are the same as what is described above for the Android app. There are some additional web based specifics:

• The controller knows what app deployment it is running by a DeploymentID parameter passed in on the query string. If the parameter is missing, it must get the value via presenting a jquery mobile modal dialog to the user requesting the Deployment Code. It then looks up the DeploymentID in the database based on the Deployment Code.

• Because there are potentially multiple devices associated with a single deployment, when starting, before loading the default home page, the controller must present an interface to the user to select the Device ID from a list of available web devices associated with the Deployment and provide the device password. Once authentication is complete, the first ‘home’ page of the application is loaded.

• The backend database is SQL Server.

Functional Specification

Please see attachments for the database schema and a process flow chart for more detail. To get most benefit from viewing the flow chart, it should be viewed in Internet Explorer.

.NET ASP SQL

Project ID: #4717230

About the project

17 proposals Remote project Active Jul 13, 2013