Skip to content

Obital Framework

Obital is an end-to-end framework for eye tracking on regular devices. By using the sensors already available, it enables high-quality software-based eye tracking data capture, interaction and analytics with a few lines of code.

Do you want to learn more about eye tracking? Go to our Learning Base β†’

Core Principles

Obital is built on three core principles:

  • Privacy: We do, under no circumstances, collect sensitive data from applications using the framework. Even though it's a GDPR gray area, we classify eye data as highly sensitive, and treat it as such. Check out our privacy policy for more information.
  • Efficiency: The framework draws on sensors and software technologies already available in the devices. This ensures that everyting is optimized for each platform, and makes everything easier to support. Our goal is to refine the data to achieve higher-level insights, than what's already available.
  • Ease-of-use: You should not need a Ph.D. in Computer Science to start using eye tracking. Obital will let you start using eye tracking with a few lines of code, and we'll take care of the hard stuff.

Our goal is to improve ambitious software products by broadening creator’s insights of human perspective through a single line of code.

Architecture

This is an overview of the Framework, it's current state and what's coming. The Obital Stack The framework is distributed in two parts.

  1. A cross platform static library (Obital.a) containing all core functionality that does not require platform specific API's
  2. A platform specific framework (Obital_iOS.framework for iOS), that integrates the features of the static library, and the platform specific API's that are advantagerous for eye tracking.

For example, in iOS Obital.framework and Obital_iOS.framework is installed with an iOS package manager (CocoaPods). Obital_iOS is the only framework the developer interacts with, and apart from wrapping cross platform methods, it also manages ARKit sessions and UI elements specific to iOS. This ensures:

  • Recognizability - everything is implemented and managed as you would normally do on the given platform
  • Extendability - you can easily extend classes and methods to fit your own needs
  • Optimization - As fx Apple improves and fixes their code, those improvements are reflected in the framework
  • Maintainability - Less custom code means less bugs and easier support.