Skip to content
Jun Matsushita edited this page Nov 27, 2015 · 18 revisions

Background

Mobile Tor Browser Capabilities

Orweb

JS is disabled by default. When enabled, the following HTML5/modern browser features definitely don't work:

  • pointer events
  • web notifications
  • WebRTC (or anything peer-to-peer)
  • Drag and drop
  • Clipboard access
  • Web Cryptography API
  • CSP 1.1 (1.0 is understood)
  • Seamless iframes
  • Any video other than H.264 or WebM with VP8
  • Web Audio API
  • HTML5 picture/srcset
  • Service workers
  • Content & Scheme handlers
  • Local Storage (Session storage works appears to work though)

CSS3 Selectors appear to be fully supported, as are Media Queries. Background/element clipping appear to have some issues, but otherwise styling appears to be fully-capable as tested by loading the Bootstrap 3 page and browsing the documentation.

Orfox

Direct feature tests were more difficult than in the other two browsers because of errors, but documentation and some brief usage seem to indicate that Orfox is close in capabilities to the desktop Tor browser.

Desktop Tor Browser Capabilities

Tor Browser

JS is enabled by default, although NoScript is easy to enable and often used. When JS is enabled, the following HTML5/modern browser features definitely don't work:

  • pointer events
  • WebRTC (or anything peer-to-peer)
  • Drag and drop
  • CSP 1.1 (1.0 is understood)
  • Seamless iframes
  • Any video other than H.264, WebM, or Ogg Theora
  • Service workers
  • LocalStorage persists across windows and tabs, but resets on browser restart

CSS3 Selectors appear to be fully supported, as are Media Queries. Styling appears to be fully-capable as tested by loading the Bootstrap 3 page and browsing the documentation.

Android Development Frameworks/Toolkits

Cordova-based Solution

Supports Android 4.0.3 or above: Yes, although many frameworks depend on higher versions React Native: requires 4.1 or higher Reapp: ???? Ionic: 4.0 or higher

NativeScript

Supports Android 4.0.3 or above: Not currently(requires 4.2 or above). FAQ says Support for lower version of Android and Windows are coming soon. See our roadmap. Also see this issue

Appcelerator

Supports Android 4.0.3 or above: Yes, including latest version of Titanium

Fully Native Development

Supports Android 4.0.3 or above: Yes

Potential App Capabilities

Content Search

Client-side Web Options

Saving Site Browsing History & Offline Content

None of the tested browsers offer a reliable way to persist data between browser sessions. This leaves a native app as the only way to accomplish offline content and client-side storage of content consumption information (to make it easy to see what has been read and what hasn't).

For Cordova apps, this is a promising solution for saving content for offline use, and it even handles unzipping retrieved content.

For fully-native apps, a sync adapter could be used tutorial.

Content Module Formats

See the Content Model documentation for more about the content structure and metadata. Also see Content Ecosystem wiki page for suggestions on format.

Content Sharing

Content linking (email, browser) https://github.com/Telerik-Verified-Plugins/Custom-URL-scheme

Also see Content Ecosystem wiki page for suggestions on sharing.

Content Editing

See Content Ecosystem wiki page for suggestions on editing/authoring.

Bootstrapping

F-Droid already supports peer to peer app sharing via Bluetooth

  • Share F-Droid by NFC/Bluetooth
  • Swap apps

Would need creating an iilab F-Droid repo.