! Tor Mobile Development Kit Roadmap

0-30 days

  • gather all existing library impl and promote on a page "Tor isn't just an app, Tor is infrastructure for truly private cloud communications"
  • Orbot v15 release and OONI iOS libight

30-90 days

  • define common API usage model
  • Tor on Jolla/Sailfish device as daemon?
  • TB "Mini" first release
  • OONI Android

90-120 days

  • start integrated library w/ device specific implementations
  • move from "hack" to new clear modular, shared library approach (possibly... research if better to keep tor in own process)

120-180 days

  • Tor Dev Kit 1.0 release
  • research next-gen tor mobile optimizations

Who is our audience?

  • Tech companies who need secure cloud infrastructure for device-to-device
  • microsoft, google, apple

Empower device companies with a Tor daemon/service built-in available for devs to activate

  • Jolla, CyanogenMOD, ??

Support existing "freedom" projects with the infrastructure they need

  • OONI, ChatSecure, Onion Browser, Courier, Briar, and beyond

What does Tor Dev Kit look like?

  • cross platform API that wraps control port
  • platform-specific implementation for each device, context
  • docs, design info, best practices for developers
  • support for platforms and frameworks like phonegap (web app platforms)
  • prebuilt binaries / aars/ gradle for devs who trust us to build tor from source
  • widgets/UI configurators to make integration with app easier
  • support for PLUTO (pluggable transports library/manager)

Little-t tor next-gen mobile research needs

  • reduce data usage of clients and HSes
  • optimize for non-x86 architectures or mobile arch/cpu specific capabilities
  • crypto tuning for mobile device hardware capabilities
  • resiliency to network outtage, latency, switching
  • support multipath TCP?? TCP keep alive between different networks, or Tor UDP, etc
Last modified 4 years ago Last modified on Mar 4, 2015, 5:16:26 PM