Open Source Mobile Augmented Reality<br />
Open source AR in the wild<br />Stats<br />Google Code: 104<br />SourceForge: 37<br />GitHub: ~75<br />Mostly sketches, AR...
Factors hindering development<br />Platform<br />Content<br />UI<br />
Platform problem<br />
Native Apps vs. Web Apps<br />
Native Apps<br />
Barriers to open source<br />Walled gardens/silos<br />Fragmentation<br />Android <br />1.5, 1.6, 2.0, 2.1,2.2<br />apps v...
Web Apps<br />
Kamra<br />https://research.cc.gatech.edu/polaris/<br />
Content Problem<br />
The UI Problem<br />“In different apps, touching a picture could produce any of the following 5 results: <br />Nothing hap...
Standards are a growth medium<br />
So many to choose from!<br />HTML5<br />X3D<br />ARML<br />KARML<br />KML<br />GeoRSS<br />Wave Federation Protocol<br />W...
Unintended and unexpected outcomes<br />
Going forward<br />Use existing standards, extend when necessary<br />Use existing projects, extend - don’t reinvent<br />...
Contact<br />Sophia Parafina, OpenGeo (opengeo.org)<br />Email: sophia@locativemedia.org<br />Twitter: @spara<br />Blog: l...
Upcoming SlideShare
Loading in …5
×

Open Source Mobile Augmented Reality

10,127 views

Published on

presentation for the 2010 Augmented Reality Event

Published in: Technology, News & Politics
2 Comments
14 Likes
Statistics
Notes
  • galaxy garden
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Notes don't seem to be working, so here they are

    Slide 1

    * Sophia Parafina, locativemedia.org

    Slide 2

    * Stats were gathered from searches on repositories using the term “augmented reality”
    * A quick survey of major code repositories reveal few complete AR browser clients

    Slide 3

    Slide 4

    Slide 5

    * As with other mobile applications there is a tension between native applications for mobile devices and web applications

    Slide 6

    * Currently native apps dominate the AR browser space: Layar, Junaio, Wikitude, and open source browser Mixare
    * Native apps offer the benefits of access to sensors (compass, gps, accelerometer, and video) on the mobile device
    * Developers can build a custom and tailored experience for users

    Slide 7

    * Directly sharing data streams/channels (content) between native applications is not possible
    * While many AR providers provide an API for authoring content, this is not an open ecosystem
    * The problem of fragmentation affects both major mobile smart phone devices, software must be tweaked for each version of the OS or device

    Slide 8

    * Web apps can currently access geolocation through HTML5, but they can not access the phone’s sensors
    * A dev version of Android demoed at Google I/O 2010 showed the browser accessing the accelerometer, but these features could take several years to be implemented in a production version

    Slide 9

    * currently AR Browsers based on a web application does not exist

    Slide 10

    * however, the Kamra system (possible release summer 2010) is an AR browser using HTML5 and KML

    Slide 11

    * AR content varies widely from POI annotation, virtual objects representing real word objects, and completely virtually objects

    Slide 12

    * Excerpt from Jakob Nielsen’s report in iPad usability testing, AR applications face the same hurdles

    Slide 13

    * Standards provide a way forward for developers
    * they act as a growth medium for emerging industries

    Slide 14

    * There are many standards to choose from that cover several domains
    * these domains include data transport, 3D object formats, geo location, as well as methods for transactions

    Slide 15

    * Even with standards, AR experiences, especially if they are web based, will lead to unexpected outcomes
    * expect dancing baby avatars in the streets


    Slide 16

    * Development patterns for moving forward include reuse of standards and code, rapid iteration, and mindfulness towards current information infrastructure (bandwidth, battery life) and being open to future architectures
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
10,127
On SlideShare
0
From Embeds
0
Number of Embeds
287
Actions
Shares
0
Downloads
220
Comments
2
Likes
14
Embeds 0
No embeds

No notes for slide
  • Sophia Parafina, locativemedia.org
  • Stats were gathered from searches on repositories using the term “augmented reality” A quick survey of major code repositories reveal few complete AR browser clients
  • As with other mobile applications there is a tension between native applications for mobile devices and web applications
  • Currently native apps dominate the AR browser space: Layar, Junaio, Wikitude, and open source browser Mixare Native apps offer the benefits of access to sensors (compass, gps, accelerometer, and video) on the mobile device Developers can build a custom and tailored experience for users
  • Directly sharing data streams/channels (content) between native applications is not possible While many AR providers provide an API for authoring content, this is not an open ecosystem The problem of fragmentation affects both major mobile smart phone devices, software must be tweaked for each version of the OS or device
  • Web apps can currently access geolocation through HTML5, but they can not access the phone’s sensors A dev version of Android demoed at Google I/O 2010 showed the browser accessing the accelerometer, but these features could take several years to be implemented in a production version
  • currently AR Browsers based on a web application does not exist
  • however, the Kamra system (possible release summer 2010) is an AR browser using HTML5 and KML
  • AR content varies widely from POI annotation, virtual objects representing real word objects, and completely virtually objects
  • Excerpt from Jakob Nielsen’s report iniPad usability testing, AR applications face the same hurdles
  • Standards provide a way forward for developers they act as a growth medium for emerging industries
  • There are many standards to choose from that cover several domains these domains include data transport, 3D object formats, geo location, as well as methods for transactions
  • Even with standards, AR experiences, especially if they are web based, will lead to unexpected outcomes expect dancing baby avatars in the streets
  • Development patterns for moving forward include reuse of standards and code, rapid iteration, and mindfulness towards current information infrastructure (bandwidth, battery life) and being open to future architectures
  • Open Source Mobile Augmented Reality

    1. Open Source Mobile Augmented Reality<br />
    2. Open source AR in the wild<br />Stats<br />Google Code: 104<br />SourceForge: 37<br />GitHub: ~75<br />Mostly sketches, ARToolkit projects, libs and utilities<br />Not seeing many full clients<br />
    3. Factors hindering development<br />Platform<br />Content<br />UI<br />
    4. Platform problem<br />
    5. Native Apps vs. Web Apps<br />
    6. Native Apps<br />
    7. Barriers to open source<br />Walled gardens/silos<br />Fragmentation<br />Android <br />1.5, 1.6, 2.0, 2.1,2.2<br />apps vary across carriers<br />Apple<br />iPhone, iPod Touch, iPad<br />iPad video out, determined by application<br />
    8. Web Apps<br />
    9. Kamra<br />https://research.cc.gatech.edu/polaris/<br />
    10. Content Problem<br />
    11. The UI Problem<br />“In different apps, touching a picture could produce any of the following 5 results: <br />Nothing happens <br />Enlarging the picture <br />Hyperlinking to a more detailed page about that item <br />Flipping the image to reveal additional pictures in the same place (metaphorically, these new pictures are "on the back side" of the original picture) <br />Popping up a set of navigation choices” <br />from Jakob Nielsen,iPad Usability: First Findings From User Testing (http://www.useit.com/alertbox/ipad.html)<br />
    12. Standards are a growth medium<br />
    13. So many to choose from!<br />HTML5<br />X3D<br />ARML<br />KARML<br />KML<br />GeoRSS<br />Wave Federation Protocol<br />W3C<br />
    14. Unintended and unexpected outcomes<br />
    15. Going forward<br />Use existing standards, extend when necessary<br />Use existing projects, extend - don’t reinvent<br />Iterate quickly, make lots of prototypes<br />Respect today’s architectures, plan for the future architectures<br />
    16. Contact<br />Sophia Parafina, OpenGeo (opengeo.org)<br />Email: sophia@locativemedia.org<br />Twitter: @spara<br />Blog: locativemedia.org<br />Blog twitter: @locatively<br />

    ×