Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

Here are the outstanding features/enhancements and bugs/defenses to be implemented in the native (Appcelerator) mobile app. This document should serve as a discussion piece to determine what features/bugs are top priority, and to represent the discussion outcome in created/updated Jira tickets.

Native App in General

Bugs/Defenses

  • Handling of network/server errors in portlets.
  • COMPLETE - Quirky navigation to and from the settings window. Eg., visiting the window from a native window, "home" icon actually goes back to portlet, not home. After navigating to settings window, and trying to return to it later from a native window (like map), it doesn't open the settings window.
  • COMPLETE - Handling of portal session timeouts
  • COMPLETE - Settings window doesn't close keyboard on update or exit
  • COMPLETE - Icon text in home screen is cut off at bottom in Android.
  • COMPLETE - Increasing clickable area of icons (like settings and home) for easier navigation, and adding better press indicators (such as changing color) for better UI feedback.
  • --- Low Priority ---
  • Create failsafe in localization dictionary to fall back to English

Features/Enhancements

  • COMPLETE - Create or acquire better portlet icons.
  • COMPLETE - Enhancing design of home screen (positioning, background color, font colors, etc)
  • COMPLETE - Finalizing app icon (looks lo-res right now)
  • COMPLETE - Creating default application image
  • COMPLETE - Shorten portlet names so icon labels don't get cut off.

Native Map

Bugs/Defenses

  • COMPLETE - Handling network errors gracefully. Eg. Message: "Network unavailable, only offline data is available". Note: Need to determine if Map will plot points and show cached map images offline.
  • COMPLETE - Searching on iOS for certain single letters causes app to crash
  • Center the map on appropriate point. (will default be returned from map service?)
  • Android bug requiring user to drag map before clicking any annotations
  • If an open annotation is layered above another map point, touch events on the open annotation are ignored and the annotation of the underlying map point is displayed instead. Prevents detail view from being able to open.

Features/Enhancements

  • COMPLETE - Storing map data locally in database once retrieved from service.
  • COMPLETE - Improve design of map pins in Android

Native Directory

Bugs/Defenses

  • Android skinning of default view needs work.

Features/Enhancements

  • Better transitions to detail view
  • COMPLETE - Account for no data available in contact detail
  • COMPLETE - Account for no emergency contact
  • Improve search to account for mis-spellings, to include all fields
  • COMPLETE (arguably) - Better Design Treatment
  • No labels