>> Mobile Content Manager




This solution exemplifies rapid application development in C#, targeted application features, process automation, and budget responsibility.

We at JBCG are proud to present some screen shots of the Mobile Content Management we built for Middlemind Games. Below is a list of features and screen shots.

Features:

  • MSSQL 2008 database on the backend.
  • Automated management of images including water marking.
  • One click backup capability.
  • Automatic order processing including image resizing and format conversion.
  • Automatic package compression and XML profile generation.
  • Form based content addition.
  • Image preview including previews of all image sizes.
  • Application is 99% data driven.
  • Built in ability to keep track of image status in different publication channels.

Screen Shots:

The screen shot depicts the content viewing page. Users have the ability to update any aspect of their content including selecting multiple categories depending on carrier support.

The screen shot depicts the content addition page. Users have the ability to add new content to the "content repository" all content is validated for the correct dimensions. This form also provides a level of quality control requiring that the repository "foundation" be satisfied before any new content is added to the repository. This basically means that all the required image sizes must be present before new content can be added. Users have the ability to name the new content and suggest associated categories for the different publication channels and carriers.

The screen shot depicts the fill order page. Users have the ability to select the images from the repository that need to be packaged for the current order. A spreadsheet is provided that tells the application what image sizes are needed, their name, and the image format as well as the maximum allowable size. The software automatically resizes images from the repository to match the required image dimensions based on the closest matching aspect ratio. Images are tested to make sure that they meet the maximum file size constraint and are slightly lowered in quality until they do. All images are renamed using the tags in place in the seed spreadsheet. Final packages are compressed and include an XML identifier sheet to aid in submission processing.