Mobile Client Update Process Automation

Mobile Client Update Process Automation

Please note this feature has not been implemented in the app.

The current process of updating client mobile applications involves several manual steps, requiring staff and clients to communicate regarding multiple images of varying dimensions. This process is slow and error prone, requiring time to complete. The following document describes how the designer application may be updated to include functionality which will allow much of the asset gathering to be done without the intervention of HungerRush Staff.

Overview

The HungerRush Designer application will be updated to have a new section dedicated to the management of the basic assets required for the mobile application. This will take the form of a menu item for a site, which will take the user to a page which shows the following information:

  1. A preview of the current state of the mobile application assets. The preview will use primary and secondary colors as per the latest published designer website.
  2. A form, with an image preview, allowing users to update assets by uploading new images for each of the following types:
    • Logo
    • App Icon
    • Splash Screen
    • Featured Graphic
  3. The form will include text fields which will be used to set the app name and description.
  4. A submit button which will “publish” the current set of images, colors, app name and description.
  5. Basic Publication history, including links to images which were previously published.

Process

The high level process for a user and HungerRush staff will be as follows:

  1. The user logs into designer using their existing HungerRush credentials
  2. The user selects a site to update from the existing Site Selector
  3. The user selects the Mobile Look and Feel menu item
  4. A new page is presented to the, as described in the Overview
  5. The user sets the app’s name and description, and uses the uploaders to upload the 4 required image types
  6. When the user is ready with the appearance of the preview, the user presses the Submit button.
  7. The Designer backend receives a notification containing the details of the images, name, description and colors.
  8. The backend uses this information, in concert with a new image processing service, to create new assets of the various dimensions required
  9. The user and HungerRush staff receive an email notifying them of the request to update the user’s app. This email will contain all of the color codes, the text data, and links to the various files.

Architecture

The new functionality required for the Designer System to achieve this functionality are as follows:

architecture

  1. The Designer web application will need a new menu item, and view for managing this processes
  2. The Designer web application will need to integrate with a new GraphQL query which will allow the user to see what the current state of the form is, as well as the publication history
  3. The Designer web application will need to integration with a new GraphQL mutation which will allow the user to request an app update with the current application
  4. The Designer backend will require a new service for storing state information regarding the user’s set of assets and configuration for the mobile application. This service should also store historical data for previous publications. This will be achieved with an event-sourced approach to keep track of the current state, as well as historical data.
  5. Image Processing Service. This service is responsible for processing user images and creating all of the required assets for a mobile app update.
  6. A basic email service which will notify the user and HungerRush staff when an update is requested