User:Dria/PiCL Future Ideas - Revision history

Dria: /* Syncing additional data types */

2013-08-02T15:22:22Z

Syncing additional data types

← Older revision		Revision as of 15:22, 2 August 2013
Line 33:		Line 33:
	* Apps downloaded/purchased		* Apps downloaded/purchased
	* Messages including SMS/MMS		* Messages including SMS/MMS
	* ~~History~~		* Reading List (may be a separate service, TBD)
	* Passwords
	* Bookmarks
	* Open Tabs / Reading List
	* Tab groups		* Tab groups
	* Browser add-ons		* Browser add-ons

Dria: /* Syncing additional data types */

2013-08-02T15:21:45Z

Syncing additional data types

← Older revision		Revision as of 15:21, 2 August 2013
Line 38:		Line 38:
	* Open Tabs / Reading List		* Open Tabs / Reading List
	* Tab groups		* Tab groups
			* Browser add-ons

	We may eventually want to pull this data into other browsers and apps, and access it via a Web UI.		We may eventually want to pull this data into other browsers and apps, and access it via a Web UI.

Dria: /* Syncing additional data types (FxOS) */

2013-08-02T15:20:50Z

Syncing additional data types (FxOS)

← Older revision		Revision as of 15:20, 2 August 2013
Line 27:		Line 27:
	Could include third-party integration with alternate services the user would like to use, including a personal data store.		Could include third-party integration with alternate services the user would like to use, including a personal data store.

	=== Syncing additional data types ~~(FxOS)~~ ===		=== Syncing additional data types ===
	Provide standard sync facilities for FxOS apps ~~that matter most -- messages, calendar, contacts, downloaded apps (and app data~~)~~, etc.~~ (~~''Waiting on further input & data types here from pdol & clee''~~)		Provide standard sync facilities for additional data types (for FxOS apps & etc)
			* Contacts
			* User preferences/settings (this will need to go into a lot more detail as to what is included)
			* Apps downloaded/purchased
			* Messages including SMS/MMS
			* History
			* Passwords
			* Bookmarks
			* Open Tabs / Reading List
			* Tab groups

	We may eventually want to pull this data into other browsers and apps, and access it via a Web UI.		We may eventually want to pull this data into other browsers and apps, and access it via a Web UI.

Lloydhilaiel: /* Web access of PiCL data */

2013-07-30T16:09:31Z

Web access of PiCL data

← Older revision		Revision as of 16:09, 30 July 2013
Line 40:		Line 40:
	=== Web access of PiCL data ===		=== Web access of PiCL data ===
	Give users a web-based UI they can use to into and access all of their PiCL data in ways similar to within the browser -- bookmarks, open tabs, history; future: task lists, collections, workspaces, etc.		Give users a web-based UI they can use to into and access all of their PiCL data in ways similar to within the browser -- bookmarks, open tabs, history; future: task lists, collections, workspaces, etc.

			(lloyd) Does one holistic of all of your firefox stuff make more sense to users than more vertical features?

	=== Task list ===		=== Task list ===

Dria: /* Workspaces */

2013-07-24T13:22:27Z

Workspaces

← Older revision		Revision as of 13:22, 24 July 2013
Line 75:		Line 75:
	== Future exploration (very blue sky) ==		== Future exploration (very blue sky) ==
	=== Workspaces ===		=== Workspaces ===
	Workspaces are collaborative, shareable, and publishable places where users can store and retrieve bookmarks, collections, task lists, documents, etc. The core idea is pretty vaguely defined right now, but the idea is to make the process of researching and working on projects a lot simpler. WebRTC could probably augment this as well.		Workspaces are collaborative, shareable, and publishable places where users can work together on projects or research. They give users a central space in which to store and retrieve bookmarks, collections, task lists, documents, etc. The core idea is pretty vaguely defined right now, but the idea is to make the process of researching and working on projects a lot simpler. WebRTC could probably augment this as well.

	=== Context-awareness ===		=== Context-awareness ===

Dria: /* Collections */

2013-07-24T13:21:05Z

Collections

← Older revision		Revision as of 13:21, 24 July 2013
Line 51:		Line 51:
	Bookmarks evolved...		Bookmarks evolved...

	Collections ~~could~~:		Collections are prettily-formatted collections of urls + webclips/images. They can:
	* include any media type that's available on the web (audio, video, text, images, full pages, PDF documents, etc)		* include any media type that's available on the web (audio, video, text, images, full pages, PDF documents, etc)
	* be publishable (publicly viewable on the web)		* be publishable (publicly viewable on the web)

Dria: /* Reading List/Queue */

2013-07-24T13:18:21Z

Reading List/Queue

← Older revision		Revision as of 13:18, 24 July 2013
Line 20:		Line 20:
	Future evolutions would allow users to do things like use their phone to auto-play all of their Queued videos on their TV and to further interact with those in the process (rating them on the origin site, adding comments to the original blog post, adding them to a Collection (see below), sharing them, etc.).		Future evolutions would allow users to do things like use their phone to auto-play all of their Queued videos on their TV and to further interact with those in the process (rating them on the origin site, adding comments to the original blog post, adding them to a Collection (see below), sharing them, etc.).

	~~This~~ should also allow users to either augment or replace this feature completely with a third-party service.		We should also allow users to either augment or replace this feature completely with a third-party service.

	=== Backup/Restore ===		=== Backup/Restore ===

Dria: /* What is this? */

2013-07-24T13:08:57Z

What is this?

← Older revision		Revision as of 13:08, 24 July 2013
Line 2:		Line 2:
	This is a (probably incomplete) list of the various feature & service ideas that have been discussed over the past few years that could somehow involve user data in the cloud. It includes some of the specific features we've been talking about more recently, but also includes some much farther-reaching bluesky areas for possible exploration.		This is a (probably incomplete) list of the various feature & service ideas that have been discussed over the past few years that could somehow involve user data in the cloud. It includes some of the specific features we've been talking about more recently, but also includes some much farther-reaching bluesky areas for possible exploration.

	I've put this together largely as a discussion piece, and to help engineers understand some possible future feature & service requirements to aid with early stage service planning.		I've put this together largely as a discussion piece, and to help engineers understand some possible future feature & service requirements to aid with early-stage service planning.

	It should be assumed that any features and services we do create should support the entire Mozilla product line -- Firefox Desktop, Firefox Android, Firefox Metro, and Firefox OS.		NOTE: It should be assumed that any features and services we do create should support the entire Mozilla product line -- Firefox Desktop, Firefox Android, Firefox Metro, and Firefox OS.

	I expect this list will evolve over time, and should be considered a living document. If you think there are things missing from this list, or if you have any questions, ping Deb (dria on IRC).		I expect this list will evolve over time, and should be considered a living document. If you think there are things missing from this list, or if you have any questions, ping Deb (dria on IRC).

Dria: /* What is this? */

2013-07-24T12:36:15Z

What is this?

← Older revision		Revision as of 12:36, 24 July 2013
Line 1:		Line 1:
	== What is this? ==		== What is this? ==
	This is a (probably incomplete) list of the various feature/service ideas that have been discussed over the past few years that could somehow involve user data in the cloud. It includes some of the specific features we've been talking about more recently, but also includes some much farther-reaching bluesky areas for possible exploration.		This is a (probably incomplete) list of the various feature & service ideas that have been discussed over the past few years that could somehow involve user data in the cloud. It includes some of the specific features we've been talking about more recently, but also includes some much farther-reaching bluesky areas for possible exploration.

	I've put this together largely as a discussion piece, and to help engineers understand some possible future ~~features/~~service requirements to aid with early stage service planning.		I've put this together largely as a discussion piece, and to help engineers understand some possible future feature & service requirements to aid with early stage service planning.

	It should be assumed that any features/services we do create should support the entire Mozilla product line -- Firefox Desktop, Firefox Android, Firefox Metro, and Firefox OS.		It should be assumed that any features and services we do create should support the entire Mozilla product line -- Firefox Desktop, Firefox Android, Firefox Metro, and Firefox OS.

	I expect this list will evolve over time, and should be considered a living document. If you think there are things missing from this list, or if you have any questions, ping Deb (dria on IRC).		I expect this list will evolve over time, and should be considered a living document. If you think there are things missing from this list, or if you have any questions, ping Deb (dria on IRC).

Dria: /* What is this? */

2013-07-24T12:35:34Z

What is this?

← Older revision		Revision as of 12:35, 24 July 2013
Line 1:		Line 1:
	== What is this? ==		== What is this? ==
	This is a (probably incomplete) list of the various ideas that have been discussed over the past few years that could somehow involve user data in the cloud. It includes some of the specific features we've been talking about more recently, but also includes some much farther-reaching bluesky areas for possible exploration.		This is a (probably incomplete) list of the various feature/service ideas that have been discussed over the past few years that could somehow involve user data in the cloud. It includes some of the specific features we've been talking about more recently, but also includes some much farther-reaching bluesky areas for possible exploration.

	I've put this together largely as a discussion piece, and to help engineers understand some possible future features/service requirements to aid with early stage service planning.		I've put this together largely as a discussion piece, and to help engineers understand some possible future features/service requirements to aid with early stage service planning.