Retail Engagement ProgramMarch 19th, 2014 (updated February 14th, 2017)
The Retail Engagement Program is a mobile workforce solution. The combination of client applications and server programs, provide companies with a complete paperless form handling system.
My project involved an initial porting of a minimal Java/Android app to the Windows Phone platform followed by extensive development of new features and a port from the Windows Phone platform to the Windows Store platform.
Windows Phone App Main Page
The Windows Phone 8 app is written in C# and XAML and uses many of the phone’s features, some of which are:
Camera and Picture Library Access
GPS and Location Services
Bar Code Reading (using the ZXing library)
Web Services Client
The app is multi-threaded, and uses web service posts requests to handle incoming content updates and outgoing form uploads.
Various Form Pages
In the images above, you can see two form pages with a variety of controls. There is also a picture of the verification page seen before any form is sent to the server. Forms can be configured on the server to have panorama/pivot sections. They can also be configured to have separate pages and utilize navigation buttons to move from one page to another. In addition to having a conditional visibility logic for pages, individual controls within a form can be conditionally displayed based on the data entered in other controls. For example, whole pages can be hidden if they don’t apply to the selection within an earlier list.
There are a variety of form controls available including, but not limited to controls for:
Text and Large Text
Email Address – used to send a copy of the form to someone upon submission
Checkbox, Yes/No Checkboxes, Yes/No Text Selection
Single Selection List
Multiple Selection List
List controls can display different sets of selections based on selections within earlier lists. One form can even affect the contents of another form that is opened at the same time.
The Windows Store app has a superset of the functionality available in the phone app, while displaying forms horizontally. It is designed for tablet devices but works fine on any Windows 8.1 computer.
In addition to all of the same form controls, the Windows Store app also provides a more useful interface for accessing data files that have been downloaded from the server. It also can display news items, thus providing more than a simple form entry platform.
Form Page with List
The pictures above show various pages in the app. The form pages, here and in the phone app, have content that is designed on the server. These are just a small example of the variety of controls and formatting available to administrators and users.
The app is written, like the phone app, in C# and XAML.
The Windows Phone and Windows Store environments present many interesting programming challenges. Both environments require that any manipulation of the user interface be done in an existing user interface thread. This adds significant complexity to the apps because many operations are performed asynchronously by the OS.
In addition to the complexity added by having only a single UI thread capable of UI manipulation, the Windows Store app environment provides all file system access asynchronously. Even in the context of a background thread, the code to open, read, write, or even close a file, cannot be blocked until completion. In the UI thread, a user could navigate away from a page while at the same time completing some I/O operation that relies on that page. These programming requirements enforce a responsive user interface but also then require large amounts of error handling to be added to the code.
Another interesting programming issue is the lack of built-in database support in Windows Store apps. The Windows phone provides SQL and Linq capabilities built-in, while Windows 8.1 does not. This causes there to be even larger amounts of C# code that is almost identical but not usable on both systems.
Work on these apps, and on the whole system, continues.