Skip to content

FGX Globe Mission Objectives Goals

theo-armour edited this page Mar 1, 2013 · 1 revision

FGX Globe Mission Objectives Goals

Primary Mission

The primary mission of FGx Globe is to enable you to:

  • See who is in the air right now, with what equipment and where they are right now - faster and more easily than any other app out there
  • See relevant aspects of what is on the ground underneath you now
  • Track the flights of a small number of planes

Secondary Mission

The secondary mission is to offer paradigms that may eventually useful to:

  • A MMORPG FlightGear
  • The development of 3D user experience
  • The display of real-time big-data

Objectives

  • Deal with crowded air spaces such as around KSFO and Western Europe
  • Maintain 25/30 FPS
  • Keep the number of objects on-screen at any time to within the readily perceivable range of 200 to 2,000

Thinking out loud

###Display Cache The browser can download and maintain in RAM dozens and even hundreds of megabytes of data in seconds. A WebGL enabled browser can readily manipulate thousands of objects, but not tens of thousands of objects in near real-time.

Effective use of both these capabilities requires nothing more than a good pipeline between objects in RAM and objects on display. The RAM becomes the cache for the objects in the display. The decision to make is: Out of all the things currently available which the most appropriate ones for me to display now

###Folders and Files / Planes and Places You have so many blobs of data in your hard disks that you need to tag them with identifiers that help group the blobs. Normal people call these folders and files.

Your planes and places will need a similar organization/ontology/hierarchy.

Some blobs of data are for pictures and so you use a viewer for these. Other blobs contain numbers and so you have a spreadsheet for these.

Planes in the air and planes on the ground require different viewers too. In the air the planes are miles apart. On the ground the wings almost touch. Some areas have mountains and tall buildings. Others don't. These are require very different paradigms, a very different user experience. And we need to switch between all these experiences effortlessly.

Use cases to think about

  • Your browser is on: computer/tablet/phone
  • You have touchpad/mouse/touchscreen/keyboard/console
  • You are a pilot/not a pilot.
  • You are experienced app user/inexperienced
  • You are happier in more 2D/more 3D interaction
  • You are here just to check for a few minutes or you'll leave the app up all night
  • You are looking for something specific / You are just browsing