Features/Platform/OfflineApps

Please use "Edit with form" above to edit this page.

Status

Support for Offline Apps
Stage	Feature Inbox
Status	`
Release target	`
Health	OK
Status note	Many of these are in progress, some still need to be staffed or scoped.

{{#set:Feature name=Support for Offline Apps

|Feature stage=Feature Inbox |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Many of these are in progress, some still need to be staffed or scoped. }}

Team

Product manager	Chris Blizzard
Directly Responsible Individual	Jonas Sicking / Johnny Stenback
Lead engineer	`
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	`
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	`

{{#set:Feature product manager=Chris Blizzard

|Feature feature manager=Jonas Sicking / Johnny Stenback |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

This is actually a collection of bugs that we need to fix in order to effectively support a class of offline applications.

2. Users & use cases

We want to enable a developer to write an application that can:

1. Be used on airplanes. That is, the entire application is cached and can be used.

2. To be able to store and process large amounts of data. This includes both data that's the size of smallish jason blobs (measured in kilobytes) but also large images or even videos (megabytes.)

3. To give users decent feedback about progress and important state changes. This means guidance on app changes (when it's updated), excellent responsiveness and startup time.

4. To be able to use the network when required, with decent fallback.

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

Must-have bugs:

• HTML5 App Cache: We do not fire the onupdateready event - needs investigation & a test
• IndexedDB: Set Version API will change
• IndexedDB: Can't delete a database - do this with Set Version
• IndexedDB: Enable storing files See also: [Features/Platform/LargeFilesForIndexedDB feature page for this bug] - Jan is working on this

Waiting on specs from Jonas & Robert:

• Need an API for querying permission to make a Database
• Need an API for revoking permission to make a Database (shared computer use case.)

Nice-to-have bugs:

• IndexedDB: Can only create simple key types
• IndexedDB: Can only create indexes on the root object
• API to trigger asking for the data storage permission dialog (HTML5 App Cache) or stop asking
• There's no easy way to know if you're getting the offline/cached version of a file or the one off the network. (Nice to have for testing.)

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=This is actually a collection of bugs that we need to fix in order to effectively support a class of offline applications. |Feature users and use cases=We want to enable a developer to write an application that can:

1. Be used on airplanes. That is, the entire application is cached and can be used.

2. To be able to store and process large amounts of data. This includes both data that's the size of smallish jason blobs (measured in kilobytes) but also large images or even videos (megabytes.)

3. To give users decent feedback about progress and important state changes. This means guidance on app changes (when it's updated), excellent responsiveness and startup time.

4. To be able to use the network when required, with decent fallback. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=Must-have bugs:

• HTML5 App Cache: We do not fire the onupdateready event - needs investigation & a test
• IndexedDB: Set Version API will change
• IndexedDB: Can't delete a database - do this with Set Version
• IndexedDB: Enable storing files See also: [Features/Platform/LargeFilesForIndexedDB feature page for this bug] - Jan is working on this

Waiting on specs from Jonas & Robert:

• Need an API for querying permission to make a Database
• Need an API for revoking permission to make a Database (shared computer use case.)

Nice-to-have bugs:

• IndexedDB: Can only create simple key types
• IndexedDB: Can only create indexes on the root object
• API to trigger asking for the data storage permission dialog (HTML5 App Cache) or stop asking
• There's no easy way to know if you're getting the offline/cached version of a file or the one off the network. (Nice to have for testing.)

|Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority	P1
Rank	999
Theme / Goal	Experience
Roadmap	Platform
Secondary roadmap	`
Feature list	`
Project	`
Engineering team	DOM

{{#set:Feature priority=P1

|Feature rank=999 |Feature theme=Experience |Feature roadmap=Platform |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=DOM }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}