Ideas for the Mobility Strategy

Know the audiences (plural)

Apps that work well for alerting first responders, apps that work well for collecting information, apps that work well for citizens requesting services all have specific and even unique requirements in their supporting infrastructures. Acquisition, governance, and other strategies for common application across agencies need to reflect those differences intelligently to maximize benefits of standardization while minimizing incompatibilities with agency goals.


Submitted by

Stage: Active

Feedback Score

17 votes
Voting Disabled

Idea Details

Vote Activity

  1. Upvoted
  2. Upvoted
  3. Upvoted
  4. Upvoted
  5. Upvoted
  6. Downvoted
  7. Upvoted
  8. Upvoted
  9. Upvoted
  10. Upvoted
  11. Upvoted
  12. Upvoted
  13. Upvoted
  14. Upvoted
  15. Upvoted
  16. Upvoted
  17. Upvoted
  18. Upvoted
  19. Upvoted


  1. The idea was posted


  1. Comment

    Knowing the audience is critical, and I think the Federal CIO's post alluded to it, that mobile applies to citizen's expectations of Gov AND Gov employees, but not strongly enough.

    I'd like to see the mobile strategy be sectioned off to discuss these two perspectives so each group (i.e. audience) can be attended to appropriately.

  2. Comment

    Essential to developing for all auidences is knowing that Federal agencies are required to develop for people who have disabilities. If the Federal Mobility Strategy does not support government accessibility requirements, individual agencies will be at risk, productive employees may be marginalized, and online access to public services will be more difficult for people with disabilities. Mobile platform operating systems and developer tools must support accessibility, fully functional and inexpensive assistive technologies need to be available to federal employees, and agency application developers (and their contractors) need to follow best practices to ensure a richer and more inclusive strategy.