Co-Creating Action Plans Session (Responses)
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

Please select a Mozilla product (Required)Please include your ideas in the box belowMore specifically, do you have ideas on how Mozilla can grow participation and community in this part of the project?
AppmakerEstablish a area for posting questions and requests for mentors for people who want to learn to create websites with appmaker et al

- Apply gameification techniques to recognize people who help a lot of people

- Permit matching of interests ("I know graphic design but not JS", "I can code but my web pages look terrible")

- Perhaps integrate/support Generation Open?
AppmakerMake it able to track user eye movement and share it with togather.js among devices. Show a small eye icon where other user is looking
Appmaker* Remix option
* Could be good to have least possible localisation i-e- no words
* Easy component maker - have a framework for new components
* Collaboration - more than one person working on the same app
* Possible to check the source of the component e.g. x-ray goggles
* Integration with open badges.
AppmakerTurn into web-based cloud-hosted service
Different screen experiences
Code creation and attachment to events that are generated

Depending on target audience
Export source code
Give project more visibility (currently only one youtube demo!)
Better inline documentation
Widget store
Appmaker- Badges for AppMaker users so users can demonstrate their level of accomplishment, what types of apps they've made.
- Allow apps to grant badges to users (for example, a training app can grant the user a badge when they complete the training).
- View/edit source with Thimble
- Hackable templates/remix gallery
- Automatically generate privacy policy for app based on types of data used by the widgets composing the app and where those widgets store their data - privacy icons on widgets to let developers know what kind of privacy implications use of a given widget will have.
- Design challenges "Make an app that does _____" and complete it however you want as long as it reaches the end result.
- Together.js integration
- More tools for feature phones (text based apps?)
- Make a "not dumbed down" version (difficulty gradient?) so once a user becomes an expert they can still feel comfortable using it - retain users
- Widget marketplace?
- Inspiration Gallery/App idea board "I don't have time to work on it but I'd love an app that does ________"
- Safe space for publishing "not ready for consumer" apps for testing without going to a full marketplace
- Possibly tied to above, have a comment system so people can critique your app
- "WidgetMaker" let experts build/import widgets to include in AppMaker
Appmaker- collaborative (pair programming-like) app making
- getting analytics-like insights into how your app is being used (for motivation, understanding use cases, figuring out usage patterns)
- view-source-like insight into more involved apps (transition from inspecting simple apps to visualizing complex apps)
- apply to various target groups (ages, leves of experience)
- where is this tool targeted at? children? beginners? everyone?
- can we make the transition from this simple tool to more involved one more seamless? can we make this a continuum?
- storage widgets that persist data into the cloud (cozy cloud, google, amazon)
- showcase apps or widgets (like a marketplace) for exchanging ideas and curating the best of them
- follow the links of people/apps using your widgets to get new ideas about posible use cases
- get appmaker export the app's architecture to a 3d printer so a live model could be created that kids would play with
- badges for app/widget creation
- make contests, hackfests in order to generate interest
- create youtube videos as a way to get kids interested in appmaker and start to use it
- a game where everyone takes the app up to a certain point and the next one goes on from there, leading to a collaborative project that nobody - knows how will look like in the end
- have a way to raise your hand online to identify the areas you need help or can help other people with
Appmakeras a tool for developers/designers:

rapid prototyping tool for developers and designers - what are guidelines and best
starting templates
styling delivery

solving problems for teaching devs to build apps
using appmaker with different tool chains

starting to library maintainers.

challenge for appmaker --

how to do data - if it's a global tool for hyperlocal apps we need to figure out where the data goes.

does app maker -- adding and editing data

instructions for non-programmers - how to create an experience of learning

routing different types of user experience at the start
tutorial run through

appmaker like webmaker

starter makes - like webmaker - if you can share apps a la yahoo pipes

record some kind of tutorial over demo

screencast tutorial - sitting on top of demo

20 components

component building API available
make more components

offer the hosting, backend data,

how do you get inspiration for app maker

ecosystem of communication channels

how does the system get distributed - webmaker remix concept -

make it possible to build appmaker app on a phone - not yet ready

where does the source code go for appmaker - could it live on github
within app maker - using github

use case for building offline

can't run on iOS - how do we solve that? what's iOS runtime stratgy - phonegap, standalone

custom components -

using persona as permissioning for access / auth/ sharing

system like google drive

geolcation - local relevance using geolocation - open street map

places to promote:
- webmaker
- giving phones

1 million -

get operators to give out

Gamification of app-making as learning device / open badge system - widget unlocking as pathway to learning

appmaker to marketplace

cc licensing for app maker

crowdsource app making model - teams for collaborative apps

training schools to create a local team

creating app genres for local use

places to promote:
- webmaker
- giving phones

Gamification of app-making as learning device / open badge system - widget unlocking as pathway to learning

custom components - a system of

appmaker to marketplace

cc licensing for app maker

crowdsource app making model - teams for collaborative apps

plugging output streams into each other's apps - custom snapchat . bespoke apps.

should we be worried about publishing that to the marketplace -

- it's not marketplace it's hypercard.
- kids building apps get their own phone

my birthday party app

lots of thinking about privacy and safety - use badging

screening for to get in marketplace - issue of app review

reach out to retail - app affiliates
have operators give away appmaker


how do you get inspiration for app maker

ecosystem of communication channels

how does the system get distributed - webmaker remix concept -

where does the source code go for appmaker - could it live on github
within app maker - using github

use case for building offline

can't run on iOS - how do we solve that? what's iOS runtime stratgy - phonegap, standalone

places to promote:
- webmaker
- giving phones

1 million -

make it possible to build appmaker app on a phone - not yet ready

get operators to give out

Gamification of app-making as learning device / open badge system - widget unlocking as pathway to learning

custom components - a system of

appmaker to marketplace

cc licensing for app maker

crowdsource app making model - teams for collaborative apps

plugging output streams into each other's apps - custom snapchat . bespoke apps.

should we be worried about publishing that to the marketplace -

- it's not marketplace it's hypercard.
- kids building apps get their own

my birthday party app

lots of thinking about privacy and safety - use badging

screening for to get in marketplace - issue of app review

Appmaker- Hackable
- Getting started documentation
- Tour guide
- Collaborate with together.js
- Integration with social media (FB, Twitter, etc)
- App templates
- Import component
- Add RSS feed component
More hackathon and discussion about these ideas on mailing lists and let the community joins on prototype making
AppmakerMake it easy via the right tooling to create widgets, and create a marketpkace of widgets for the appmaker so thay advanced developers have sn incentive to create eidgets. Make it a social experience, abiliry yo share widgets, and instantly publish apps and share via social networks
Appmaker1. Work with the source. For people to learn from appmaker they will need to see the source code and how it builds the apps.

2. Web Components for everything. Drag and drop a web component onto the page.

3. Accessibility and Localization built into Appmaker so localizing apps is simple.

4. Push to phone button to send the app onto the phone for testing.

5. 3D Tilt view for inspecting the scene graph

6. Responsive design so it works on Phones and Tablets.

7. Add layouts to apps such as column views/cards
1. Hold app days and give prizes and incentives to create apps with appmaker.
Appmaker1. Split screen window to work on source code when we drag and drop a widget.
2. An option to add new custom widgets.
3. Limiting the number of widgets that can be added to one card.
Evangelize app maker project.
Appmaker* Every component should be a web component in brick.
* Could you make the Summit App with Appmaker?
* View generated source code to learn app development.
* Make it accessible.
* 3D
* Font styles
* Localization
* Responsive layouts
* Big library of components that are subject / genre specific
* Tile Editor View (landscape / portrait)
* Appmaker badges (for developers, for users)
* Enabled joint editing both realtime (like together.js) or asynchronous
* Badges to acknowledge community activity
* Build it into FFOS (the editor)
* Easy to add and share widgets
* Employ Web Components for advaned users
* Badges for your first app, 10th app, etc.
* Badges for number of downloads
* Be able to author appmaker components with waterbear
* Bugmaker
* Badges for most used components
* Offline appmaker
* Enable remixing of other apps
* Collaborate + together.js
* Tough screen focused
* Open Badges (use more widgets in one app, or build more apps which can pass marketplace review)
* Basic and advanced mode switch (different target user groups?)
* Quick prototype mode (link between screens)
* RWD Widgets
* Use in mentor community
* Build apps in the phone
* Integration with webmaker accounts
* Level up from build-in components to component authoring
* Payment component
* Get-started documentation (tour guide)
* Data source + Filters
* Need a split screen view where the drag and drop screen's actual code can be seen
* We need to limit number of widgets taht can be added, the phone no longer looks like a phone with lots of components
* Need an ability to add new widgets (or create) since original widget list is not long enough
* Badge motivated w/ social sharing
* Joystick support
* Add a view source mode
* Publish your app to an app gallery
* Ideas & Maker match
* Export your app as a zip file
* More appmaker components
* Grid system for layouts
* New apps from marketplace
* User contributed apps (string manifest)
* User contributed localization (right click "localize this")
* Localization
* Data source & filters
* Appmaker strength - Easy in developing apps for all platforms
* Persistance
* View component source
* Layouts - more customization
* Ease transition to coding
* Push to phone - live device view
* Accessibility
* Push to phone
* L4ON <- ?
* Auto generate
* Visualize all the functional components
* Shit it!
* Editable
* Hackable
* Remix existing apps
* Logic editor (like yahoo! pipes or scratch)
* Templates for apps
* Export to code
* POP Mode -
* Accessibility in appmaker
* Vetting apps and components for accessibility
* Vetting components / widgets for quality
* Let users customize the editor UI
* Call the components 'widgets'
* Produce accessible apps by default
* Make widget self-documented
* Non drag and drop interface
* Ability to import non-appmaker code into appmaker (as long as it's written)
* Can i use appmaker without the editor (take advantage of the components
* A11Y - "lint" components for accessibility
* Bluetooth widgets
* Multiple projects at once
* Persist in an editable form, so I can create a text-based project and be able to share with other people
* Make appmaker color-blind friendly
* Localization of apps and widgets - for obscure langugages
* Localize an app while using it!
* More appmaker swag
* Visualize all functional components
* We need apps for ecosystem or firefox OS
* Add an RSS feed component
* POP Mode - user draws prototype images on papers, system chooses automatically
* Integrate JS fiddle / JS Bin to make it easy to edit and share components
* Add app templates
* Lets users just change api source URLs to make apps local
* Manifest maker
* Add sounds and video components / functionality
* Add touch navigation within appmaker apps
* Bake in translation within each app
AppmakerAllow for invisible components/widgets for things like data storage access or playing a sound
Use AppMaker as a training language to move on from Scratch. It can scale because you can then learn to write widgets in real code.
Appmaker + Firefox OSAn idea for merging cross-Mozilla tools for teaching and learning: pilot the distribution of FirefoxOS phones to teens in low-income communities with the message that this may not be an iOS or Android phone but the Marketplace on it is full of apps that you and your friends have built yourselves using Appmaker as a developer tool--call it the App Makerplace attached to the App Marketplace. With support from Mozilla and ZTE, we could get some phones in the hands of kids who are eager to be empowered to make their mobile future. This would be a perfect pilot project for the Hive Learning Networks a and the teen communities they serve. Older community members could serve as mentors to teen app makers. Taking a step further, if the apps kids make take off, they could become a revenue stream to underwrite the cost of the phones for the teen user-developers.
Cloud Services (Identity Services such as Persona)Keep allowing user-controlled private keys as an option (maybe the default?) for sync/user profiles.
Cloud Services (Identity Services such as Persona)We'd love a unified communication tool that moves where we do - emails, chats, etc. like an open version of the communication parts of iCloud
Cloud Services (Identity Services such as Persona)For OpenID-backednpersona (eg Gmail), make your authentication to the 3rd party not persist.
Cloud Services (Identity Services such as Persona)- Make sure the server code is free open source, to encourage local deployments, prototyping/QA, enterprise deployments
- Work with existing providers to get commercial deals and community cooperation that embrace Mozilla values, example:
- Improve Persona plugins that have high impact: WordPress, PHPBB, Mediawiki, involving Persona team directly
- Take the opportunity to create a new Persona email account or unique ID so when someone wants to abandon for example, they can do it w/.o going to each service
- Identify properly in detail all services/accounts tied / enable dby persona/sync/accounts
- On Android, work with CyanogenMod account developers to combine forces
- Encourage installation of WordPress plugin, PHPBB plugin, followup with big communities that use such products (an example: Globe And Mail and Sympatico portals in Canada)
- Encourage all local Mozilla communities, MozReps to use Persona /. Accounts on their local sites, not only Mozilla resources but also on personal blogs and resources
Cloud Services (Identity Services such as Persona)Installation of a personal vesion of Persona (including your own IdP) should be as simple as installing wordpress is now. i.e. It should a native packagein the local package manager.

Installing one's own personal Sync Server should be similarly trivial.

In a general sense, even in the world of cloud-connected services, local control must always, always, always be an option.
Through Mozilla's advocacy of decentralised development and global mutual accountability, we should be reaching out to social justice networks in the developing world, listening hard to how they do outreach and evangelism, and providing the tools for them to safeguard and share their own data on their own terms.
Cloud Services (Identity Services such as Persona)Build:
- Integrate with self-hosted data, e.g. OwnCloud, email/calendar hosting - and provide a specification and standardization for that process to allow others to tap into it
- Add backup capability into PICL - move to follow Chrome, other models that allow for real-time device equivalency from laptop to phone, including more data/features
- Implement device-to-device connectivity over local network for Sync future - why go through a server if both devices need to be present?
- Separate the layers of data storage and third-party Web services, creating API/language for the two to connect, so that users can independently select storage providers (or self-host) and use 3rd party services without relinquishing control [ex: OAuth but on steroids]
- Dream goal: Make public key crypto easy to use and integrate for data management
- Alt dream goal: distributed storage for data, DHT or other, to increase resistance to surveillance

- Most important: improve seamlessness and ease of use and transparency of operation
- Create sane defaults with options for choice of greater protections

- Educate on importance of ownership and control over data - why do people need a more privacy preserving system? Not that many know

Shape Environments:
- Integrate with 3rd party/independent web services and other entities in the personal ecosystem to shift market dynamics to empower individual
- When we start hosting data, engage in the legal conversations about 3rd party doctrine for data - there is a *real problem* with law and policy frameworks that say the companies own "your" data
- Metaphor: Banks hold your money but they don't own it. Third parties can withdraw funds when authorized, but they don't get access to your other funds, or control anything. We need a "databank".
Turn the personal identity communities (OwnCloud, etc) into Mozillians - bring them into our community through interoperability with PICL/future Sync

Work on standardization of all components to make it easier for third parties to be part of the ecosystem

Find allies on legal advocacy side - build the community around it - emphasize "data is money" / just as important - the databank!
Cloud Services (Identity Services such as Persona)* make environment and data transparent between devices (settings, look/feel, files, apps, windows, passwords)
* browser agnostic
* gaming transparency between console and desktop
* sync state between mediums. ex. moving data, settings, state between cars, kindles, watches
** resuming experience as you change between platforms
* allow integration between devices
** migrate your itinerary from mobile/desktop to the car
make it easy, fun and friendly
Cloud Services (Identity Services such as Persona)* Where does my data live; 'Collusion'-like visualization + actionability
* Self-hosted cloud services
- Teach that you can. Documentation and examples are key.
- Make it easier to do and start with.
* Standardized protocols for cloud services
- For example: standardize eventual data sync protocol for other browsers to use.
- Open formats to maximize portability and interoperability
* Decentralized, distributed systems (expand Mozilla's expertise to this field)
* small (local) communities providing hosting of cloud services that Moz provides. Like, a French Sync Service.
* Community can participate in thinking about or offering remixing of services using and because of standardized protocols.
* Reach out to researchers (universities) for help on efficient distributed algorithms
Cloud Services (Identity Services such as Persona)I saw that mozilla is going to the cloud, including a "Firefox Account". This is nice, but I think it's *really* important to do that keeping in mind that the user is the owner of his data, so he has to be able to control it. So, one of the ideas to accomplish that is to allow the user to install *easily* the server corresponding to the service. At the moment, the only service like that is Sync, and it's not really easy to install...Some small start up in WebFWD are specialized in the cloud, like CozyCloud. I think it could be really interesting to work more with them.
Cloud Services (Identity Services such as Persona)Provide preformatted AMIs, CloudFormation, or other cloud provider images for simple user controlled services, such as Sync.Make the documentation more visible and accessible for running personal services.
Cloud Services (Identity Services such as Persona)Increase awareness of distinctive qualities of Mozilla's cloud.

Build awesome user-facing services, not tied to Firefox.

Mozilla allows you to run your own cloud, increase awareness of this.

Video chat using open protocols, like XMPP.

Easier 3rd party access to Sync.

Outreach to other open cloud projects to ensure interoperability.
Cloudmaker: make it easy for people with an idea for a new cloud service to build one.

Cloud services onboarding: bring the people with knowledge on scalable cloud services and people with ideas for new services together.
Cloud Services (Identity Services such as Persona)- Sync + 3rd party apps
- Decentralized dropbox
- Persona app to authenticate on 3rd party services (IOS, Facebook, etc.)
- App to help people make cloud services
- Help startups to develop open software and services
- Crash reporting as a service.
- Partner with projects like OpenStack to improve deployment
- Social gaming services and standardising across platforms.
- Full user profile on the cloud.
- Cross browser user profiles.
- Ability to customize what cloud service to use.
- Connect your user profile with persona where you can selectively share profile pictures, etc.
Cloud Services (Identity Services such as Persona)* Increase awareness of distinctive qualities of Mozilla's cloud.
* Provide clients to use Sync-dwelling passwords for services other than the web: ssh, mail, calendar, SFTP, wifi, disk images. All existing password managers are insufficiently cross-pltaform or cross-service. We are the most trustworthy cloud provider. I'm sick of having 10 keychains. Ooo! And we could champion an open, published storage format so others can write clients—we don't have to write them all ourselves. Agile Keychain is a decent strawman: just a bunch of AES-encrypted JSON files that are easy to rsync.
* Encourage content production—Mozilla + Neocities = <3
* OAuth-style delegation via Persona
* Protect users from spying by e.g. NSA regarding Mozilla Sync by reconsidering security model, i.e. look for mechanisms that can't be hacked if Mozilla has to hand over all of its data.
* Outreach to other open-cloud-services projects, to ensure interop
* Cloud service not accessible in China due to GREAT WALL thing
* Build awesome user-facing services, not tied to Firefox.
Cloud Services (Identity Services such as Persona)- Sync + 3rd party apps
- Decentralized dropbox
- Persona app to authenticate on 3rd party services (IOS, Facebook, etc.)
- App to help people make cloud services
- Help startups to develop open software and services
- Crash reporting as a service.
- Partner with projects like OpenStack to improve deployment
- Cloud services on boarding
- dropbox
- Mozilla allows you to run your own cloud instance - increase awareness for them
- video-chat with OPEN protocols, Firefox friends
- Social gaming services and standardising across platforms.
- Full user profile on the cloud.
- Cross browser user profiles.
- Ability to customize what cloud service to use.
- Connect your user profile with persona where you can selectively share profile pictures, etc.
- pre formatted cloud servers for setting up personal sync servers, RTC, etc.
- Mediagoblin + Persona = Federated media hosting
Cloud Services (Identity Services such as Persona)Protect users from surveillance invasion by using a security model that would not enable a third party to decrypt data if they got private keys and certificates from MozillaNot really
Cloud Services (Identity Services such as Persona)- an open cloud IRC service: waartaa
Cloud Services (Identity Services such as Persona)ICMP as a Service! Every ping should help feed a kitten!

On a camera.

Granted, the kitten might explode after a few seconds, but that's a rate problem.
Cloud Services (Identity Services such as Persona)Shape environment:

* Allow persona to share more info abouth the user, in a user controlled way, to make persona more attractive to web sites compared to Facebook connect.

For instance, Persona could share an avatar to web sites, if the user agrees to share it. Other details could also be optionally shared, such as billing information or other info that may need more restrictive handling.
Code Name UP1) give users the ability to create several different profiles---for searching for different things, or tied to different devices (I.e. home, work,etc)
2) give users the ability to turn it off.
3) manage what sites can even ask you--so it doesn't try to confirm youre looking for new jobs if your boss is standing over your shoulder.
4) include user friendly explanations of what sharing data means--and the differences between locally stored data vs encrypted on a cloyud, etc.
Code Name UP1) give users the ability to create several different profiles---for searching for different things, or tied to different devices (I.e. home, work,etc)
2) give users the ability to turn it off.
3) manage what sites can even ask you--so it doesn't try to confirm youre looking for new jobs if your boss is standing over your shoulder.
4) include user friendly explanations of what sharing data means--and the differences between locally stored data vs encrypted on a cloyud, etc.
Code Name UPHow would the list of interests be maintained? Should it be a cloud service offered by Mozilla?
Tie UP to Do Not Track, do not use cookies
Idea for UIs
Pinterest (and other similar services) integration?
Website aggregation and notification
Bookmark data usage
Able to select from browser history - limited automation, able to filter by date, url, etc
Facebook (other providers available) checkins
Photo analysis from pictures taken (client side or ethical cloud services)
Google glasses integration
Community can contribute / maintain list of categories?
Code Name UPAs a starting point we agreed that the project has been refocused for now around editorial content rather than advertising, though it was hard for us to separate these two.

We discussed the name of the project and whether this may be a turn-off for some. Personalization rankles some because it sounds like Mozilla is collecting data about us so we need to do a better job of educating people about client side data saving as opposed to serve side saving.

Consider offering a cross platform experience but also consider that people may still separate activities across platforms. For example some only use Facebook on their mobile phone and not their work desktop and may value personalization that varies from device to device as a result.

Consider educating single computer-multiple user households about setting up different accounts so the browser experience is still personalized for each user.

Could we/should we market this as an improvement on google search? For example could it generate smarter news content for me when I set up a search for news items on the Russian olympics, by which I mean (for arguments sake) original journalism and not articles that are simply reprinted in different outlets from the original.

UP can be used to generate sense of empowerment in student community. Create examples of seeking knolwedge that generates additional content focused around acquiring more knowledge, either at universities, museums or elsewhere.
Code Name UP1) Have an means of manual input or feedback.

2) Find a way to input negative signals to null interests. (Short site visits or scroll-past as an indicator of dis-interest.) Feedback mechanism to say, "Never show this")

3) Users want ads to work. (We found this out when we did click-to-play for flash ads, where all the ads broke) So treat ads as content.

4) Have sharing settings uniform across sites. (Always set fonts to large for instance.) Possible input for preferred languages or other skill-level preferences?)

5) Track the places where you've shared interests.

6) Consider a setup screen on new Firefox setup.

7) Permit the ability to block certain sites from accessing. (or to avoid certain sites from being included in the training algorithm.)

7) Use UP in Mozilla products like marketplace.

8) Steer clear of "creepy" perception that could tarnish brand or product.
We anticipate the community will give us insight into sites that might be good to engage with in distributing or training about UP.
Code Name UPUser info to optimize content, not just ads.
Need big social partners
New types where you don't know you're being advertised to. i.e. for example Search rankings.
Advertising isn't bad? Some people like targeted ads. We have advertising people in the community.
Evanglise this well, otherwise PR could hurt
Online ads are great for frugal startups.
Rebrand "ads" since the name has negative connotations.
Best practices for ads. Don't make it hard to click them. Don't make them "annoying".
Porn drives a lot of things. Sex sells. We can't ignore that. This opens things up for them a bit.
More diversity of partners. Same players over and over. Allow new players to get into the game.
Send ads at appropriate times and places. Track things you're interested in temporarily. "I'm buying shoes now" "i'm vacation shopping". "I'll be in Boston next week"
Generalize buckets as opposed to too specific.
Understanding better the decision you made. Don't show me ads for shoes that I bought. By leaving a site, I've made a decision, don't send me more about them.
Think about what's best for the user.
Relevent ads can sell really well.
My recommendations being broadcast to my social circles is a good thing. Can my client help keep track of that and broadcast to my social circles. Recommendations.
Removing the middleman between sites and advertisers.
Word of mouth marketing is a huge thing.
What ads suck, and what works. Emotional heart wrenching ads. People who never click on ads, might be OK rating them.
Can we use this data on new tab page. Recommended sites on about:home.
Can we server things per-site/per advertiser. Can users opt out of groups they don't want.
Opt in to surveys.
Allow people vote up and down ads, to rank ads for appropriateness. Community based filtering/ratings.
Users can help guarantee user sovereignity/behavior/tos.
Categorization of ads
Surveys that could get people involved.
Talk to advertisers.
Monitor input really really closely.
Talk to contributers to guage interest and ideas.
Can users talk to/certify sites that are honoring the user opt-ins.
Code Name UP- Reverse the power relationship
- Be a real user agent
- User Agent "mode" - for shopping, research, etc
- Different Chrome for different user experiences
- Think about shared environments, improve control and personalization options & What about shared computers?
- What if we built an open ad market where users and advertisers can connect according to a set of rules
- Can the browser 'Learn" the user and serve them? Make it a benefit to the user alone.
- Tell the user we care about them most - and mean it
- Multiple user profiles automatically detected
- Cross device (leverage login to browser)
- Using search engines to only include sites firefox knows I've visited
- How does the browser learn about you & what mode you're in?
- Identity in the cloud
- personalization on all devices
- user control of sharing data per site
Build products:
- multiple user profiles
- leverage cross-device log-in
- identity in the cloud
- decentralized data storage

Empower communities:
- make user opt-in a viable choice - prove the industry wrong
- give the user control in multiple ways, provide info at the moment about what their choices mean
- show the user we care about them most
- loyalty card in browser
- gamification as a learning process
- earning points through sharing content on social networks

Teach and learn:
- show cause and effect - what are you broadcasting and when - create transparency in the product
- show the value of your data

Shape environments:
- create open advertising marketplace
- become a true user agent
- reverse the power relationship
- work aggressively in mobile market
- consider and build for emerging marketplaces
Code Name UP*Strengths*
- Mozilla has clout in the standards space

- not sure how the community will react, especially if this is used to enter the ad space through

- being a neutral player, Mozilla can partner with more orgs

- competition may use UP to create FUD against Mozilla

Appeal to the community that's most concerned about privacy especially after the PRISM incident and package UP as the privacy-friendly means of the inevitable personalization in the web
Code Name UP- allow users to provide alternative mechanisms for determining a user's categories (eg. plugins which can mine history)- ensure this isn't just going to give more material to add to what is already being tracked on people
- add to the doorhanger an easy way for people to discover a site's privacy policy
- link with the "firefox account" to support cross-device synchronisation, and multi-user single-profile
- discoverable and clear ui for displaying what information is shared with what sites
Code Name UP-- Questions --
Can we trust 3rd party websites with our preferences? (profilation)
Who gets to decide the categories an user can choose from?
Why are we involved in this? Does it respect our values?
How to increase UX without loosing privacy?

-- Opportunities --
Satisfy everyone (users, publishers, technologists) better than any other in the market
Personalisaton across more axes (preferences)

-- Weaknesses --
Mine profile (technical)
Disclosure of personal information

-- Threats --
We're not tier 1 player
Potential foot-gun
Browser bloat
Code Name UPAdd weight to the tags so very important messages from stuff I'm not interest in on a daily basis will show up in my thread. Encourage content providers to provide weight information. (Frontpage gets 10 and such)

Be able to provide data about yourself (shoe size like) to limit things that don't fit
Code Name UPThere is a lot of confusion on how exactly it works and how our data will be handled (ie local or cloud). Is the relationship you and you alone or socialised.
Challenge to communicate in a way that doesn't sound creepy.
Challenge of bad signals (eg like friend's kids pictures but don't have kids myself).
User control in personalisation is valuable - magic sauce with user control.
Mozilla had position to create personalisation data handling standards.
Cookielike API to get personalisation from sites you already use.
What is the problem we are trying to solve!?
Seems in early ideation, have beta people and try and determine how to help.
There are a lot of concerns and dialogue to be had, create a visible space for all that.
Code Name UPShip electrolysis
Add defaul keywords to search engines
Turn Devtools into addons
Reduce PDFjs memory use
Only decode visible images
Code Name UP1. Feedback loop for refining interest.

When sharing interests with a websites, the websites can share their generated interests back. Can also express that a particular interest was never used or weight interests based on occurrence.

2. How do you access profile data from apps? Will need a W3C standard and web API so others can utilise it.

3. Some way to solidify the idea that your data is worth actual money. "You saved $0.10 by sharing your data"

4. Be able to store your profile data anywhere you like. (On Dropbox, Persona, your own personal server)
By conveying to users that their profile and information should be owned by them and not
CommunityAnnie Elliott

Build a community networking platform that empowers Mozilla communities or ANY community can use to congregate and connect people to do good on the web, teach and learn, and shape their environments.

Should support:

Open Badges
Community groups (ability to identify all mozilla communities)
Community management
Meaningful entry points and UX on mobile, desktop
Kick it off!
CommunityMozilla should support the volunteers in their work, not disrupt them.
Also it would be nice if Mozilla said "thank you" time and again.
Mozilla is good at overloading volunteers with work. Stopping that might increase motivation.
Devtools* Drag borders in the highlighted elements to change their size/properties
* List of running timers
* Message Passing Debugging
* Display elements outerHTML in the console rather than node type, specially when it's a NodeList
* Clicking/Hovering on DOM elements logged to the console should highlight them or take you to their location in the DOM tree
* Integrate Scratchpad more tightly into the other Devtools
* Highlight elements when you have a DOM node selected or hovering them in the DOM tree
* Put box model under Computed tab
* Making it more extensible could be a good start
* Do some evangelism on how to potentially extend and create new devtools, or domain specific devtools
Firefox (Desktop and/or Android)We should lead the pack in championing secure protocols in the browser (e.g. TLS 1.1/1.2). We should encourage other browser vendors' interopability with these protocols.
Firefox (Desktop and/or Android)firefox smaller, slimmer, faster
in my home country not all people have fast inet and new pcs. i know the situation is about the same in many countries all rounnd the world. so i think it is really important to develop a version of firefox that lacks some opportunities but is smaller and faster
Firefox (Desktop and/or Android)Let's secure chrome-internal pages with Content Security Policy! (also filed as 923902)We can emphasize that the steps to remove inline scripts and rewrite the markup of those internal pages are good first bugs. They also positively impact the security of hundreds of millions of users :)
Firefox (Desktop and/or Android)Put more focus into ESR - Releases and plan features for enterprises that go into it,We could involve company feedback and try to give enterprises the tools and customization they need.
Firefox (Desktop and/or Android)Analyze user behavior and browser history (opt-in or opt-out) and tailor the Firefox experience to it. For example, "evergreen users" may do a search for "Facebook" or "yahoo mail" instead of using a bookmark or typing a URL. And the Firefox could have fewer buttons/icons.

If an advanced user never uses the home button, have it disappear (configurable to put it back).
Firefox (Desktop and/or Android)- increase the product life cycle span for Firefox browser because the localizers has no enough time to localize all the strings and to test the locale
- QA Automation Tools that may be used by the non-technical users
- at least one local community meeting per year
Firefox (Desktop and/or Android)AWESHOME is the new Android launcher that will let people try the Firefox OS experience on their Android device, without having to buy a device at the beginning. It is going to replace the Android home including all the Web Apps you installed from Marketplace. It has a DEV Mode that will transform your Android device into a developer platform for Firefox OS remotely connected to the DEV Tools. Well. It's AWESHOME!Mozilla paid staff and community can definitely take lead into developing this AWESHOME new launcher. Let's build it, as great as the rest of Mozilla's products. This way we can extend the scope of testing on Android platform so the development of Firefox OS will be more effiecient and effective.
Firefox (Desktop and/or Android)Building a Firefox Community / Get developers to return to Firefox

Old devices (tablets, phones, laptops) - CSR initiative to collect these and re-use them in developing countries. Use our existing community to use these devices to teach the web/familarise people with the devices you use to access the Web, not least Firefox as the browser to use the Web with.

Mozilla to either be the intermediary that collects the devices and passes them on or partner with an existing charitable initiative/'cash for old devices' company like Computer Aid or Mazuma (UK examples) who would collect the devices on our behalf. Then we can even consider putting Firefox OS on the devices as well.

What's the incentive to anyone who would donate a device? Freepost. An Open Badge in recognition of their contribution

Where would Mozilla succeed in developing countries where companies like Google or Apple might fail? We have a human face and a human voice. G&A are corporate and already on the back foot c.f.: 'evil' / not seen as benevolent enough.

Firefox as a platform like Google Docs - open tools to use in an education initiative. Using Firefox in an education setting/early on in someone's formative years would evoke an emotional response to the product.
see above
Firefox (Desktop and/or Android)Make it easier for people to translate Firefox (and other Mozilla products) and see the results live via interactively translating Firefox inside of Firefox.

This would allow more collaboration between translators via allowing partial translations and easy corrections of mistranslated words. Additionally, it gives the strings in the context that the string is used. This should enable crowd-sourcing of translations.
This would allow any person who knows multiple languages to contribute to Mozilla, even without any advanced technical skills. Localizers already have an important skill of knowing multiple languages, there should not be other barriers of entry for translators. This should easily allow languages that have a small user base to easily get a browser in their own language.
Firefox (Desktop and/or Android)Building a Firefox Community / Get developers to return to Firefox (IDEA #2: developers)

Education about Firefox developer tools
Going to developer conferences - more of that
Hacker News, Reddit, Stack Overflow Q&A - replying to/more carefully monitoring these channels
Sponsor tags
I am a Firefox Developer - 1x month
Making new web developers - dedicated/paid staff
For answering new developer questions in IRC (different languages)
New community flow

Paid time off one day a month to go developer mentoring sessions
We asked ourselves what motivates developers? Emotional response? Being the best (fastest, best features) Getting money for their apps? Daring to be different? Wanting to be part of the Open Source movement? Not wanting to be a 'Google product' or part of their drive to 'sell your eyeballs' to advertisers. Firefox data principles (a protest in response to how much data you have to give Google vs. not having to give any to Firefox)

We need a standard set of tools to help developers test in all browsers so that they don't have to keep switching tools each time they test in different browsers. Protocols for data coming out of tabs and browsers. We are uniquely positioned to affect standards. A translation layer - just like the example 'translation tool' that Rick Fant gave when looking at Web apps across different platforms.

Some de facto standards are emerging. We have processes to develop and codify fast-moving standards.

Stand-alone developer tools application (we could easily achieve).

Firefox (Desktop and/or Android)Firefox team can include in the help menu videos to learn how users use the features!
Firefox (Desktop and/or Android)We are imagining how to make it possible for more people to experiment with tab management and history management and organization of the browser experience.

Right now we have the built-in functions (tabs, bookmarks), and addons can access history, but these aren't accessible to a large number of people.

We imagine a way of providing a new kind of extension or addon.

In this model, the history management tool gets access to lots of information that we would not normally give content. In exchange it gives up access to any information-leaking APIs: XHR, loading arbitrary resources, form posts, etc. Any data has to be saved in localStorage (under a unique origin), and only transferred via Sync. Similar to packaged apps, but with permissions removed in addition to added.

- Access to the partially entered content in the URL bar
- List of open tabs
- Collapse, organize tabs?
- Annotating history; categories, extra information awesomebar can search on
- Camera access? Any ambient sensor.
- Others

Note: an interesting paper on the permission topic: "User-Driven Access Control: Rethinking Permission Granting in Modern Operating Systems"
It's much easier for people to effect the browser experience using this than a traditional addon.

It's more feasible to make a very custom experience, one targeted at a specific group or even individual.

More ways to create accessibility tools.

Gives "addons" (in this more minimal form) a broader potential audience.

Maybe doesn't have to be as much of a gatekeeper, if this category of addons are not as scary in terms of security and safety.

More minimal, but more stable APIs, mean less churn for these kinds of extensions.

Some of the inclusiveness of bookmarklets, which are successful in terms of participation.
Firefox (Desktop and/or Android)Reclaim browsing!!
combat search and make Internet browsing passive like flipping channels on a TV or browsing flipboard or social media
Possible browsing platform like a reddit type experience - anonymous way to vote up and serve information by geographies or themes or hashtags

Web literacy
require coding in schools -
- add webmaker to about:home
Moz Edu from LATAM
Teach parents how to talk their kids
Firefox can be the gold standard at schools
Firefox in schools
Web based office tools
Compile office suite liberoffice.js

Making Firefox ubiquitous
(even at the price at sacrificing technology stack)
Make it simple to jailbreak your phone
iPhone rooting service
Firefox for iPhone - Firefox Jr
Working with Business partners/hardware resellers to be preloaded in more devices like TV
Working with content providers to say also on Firefox

Leverage about:home
WebEd and/or Webmaker
Phone store on about:home
Making build community part of everyone's job description
like the 80/20 rule - 80% on your job description, 20% on community
Mozillians by definition have to dedicate some time recruiting or evangelizing.
Employee toolkits for advocacy to leverage with their other communities such as schools, local governments, boyscouts
Firefox (Desktop and/or Android)A privacy slider, choose how privacy conscious you want to be. Default is Google and a regular browser with better defaults, slide up to 'tinfoil hat' and you get a lot more prompts about choices which have privacy implications.

Strip out devtools from default install with option to install on the fly

Build out devtools that work for multiple browsers, be able to use Mozilla devtools to control a chrome frame for cross browser development.

YouTube video to ringtone converter. Choose a video, crop the audio and Firefox saves it as a ringtone on Android.

Stumbler integrated that helps map out and save public wifi hotspots to help people find places to connect to the internet.
Community research gathering, surveys and facts about the areas. Downloads speeds, wifi hotspots, cell phone cost, carrier plan costs, etc.

Firefox (Desktop and/or Android)Web compresion
More campaign on #FirefoxFast
Introduce more campaign on Firefox Developer Tools
Use F12 for Firefox Dev Tools
Firefox (Desktop and/or Android)* More Language support for Desktop/OS
* Creating More Awareness about Mozilla Localization Products
* Concrete Documentation about l10n Processes and products
* The idea of what we lack in terms of other contemporary browser can help us to make improve Firefox
* The importance of open source browser like Firefox is that it can support any language even though having less users and it should continue to support the languages having less speakers
* Importance of Community Building in terms of localization and currently so called 'mainstream' Mozilla community is not in sync with localisation community

* Not directly related to Firefox browser but from overall 'web' technology we think that it should be able to provide seamless interpretation between languages - a wish, Hope firefox will help to achieve the same.
* Hassle Free Translation Process - standardization of process -

* On the fly Translation Tools

* Syncing between locamotion commit and hg should be on the fly

* Need Testing Process Something like FLTG -

Firefox (Desktop and/or Android)Web content sandboxing
Privilege control on browser add-on
Firefox (Desktop and/or Android)-- Threats --
Personalisation weakened
Losing developer mindshare
Commodification of browsers
Reputation for bloat/performance

-- Opportunities --
Australis is simple but powerful, keep in mind personalisation

-- Ideas --
Don't follow the trend
Build UP for Firefox (change prefs and everything exposed based on how you use Firefox) so that different categories of users will have the browser they want

-- Challenge --
Usability vs. privacy -> need for a smarter browser
Firefox (Desktop and/or Android)- Add On/feature required to save webpages in pdf format
- Add On/feature to save a website's multiple pages into an image
- Intelli-sense in Styling Console should be there
- Introduce the option to save a complete website on a local drive (with complete hierarchy) for the developers.
- Ease of access to passwords through password manager- privacy violation
- Non-unique User Interface (Australis) will not attract more users. Firefox should at-least retain it's personality (theme) in Australis.
- keep the similar idea sharing notepad for the summit participants through out the year.
Firefox (Desktop and/or Android)Weaknesses:
* There is no Intellisense in styling console.
* Easy accessible password manager
* Australis weakness: Non-unique user interface
* No option in Desktop version to save webpages in PDF format. (suggested twice)
* Feature bloat
* Cluttered
* Customization
* Unstable API (addons)
* Forward-compatible with customized UI
* Lack localization tool
* Sync sucks!!!
* Unversal account for all devices/platforms
* Add-ons would slow and crash browser
* User interface complicated for normal users, would sometimes confuse users
* FF add-ons are over-privileged
* Not enough direct avenues to support
* GIFS! (faster, please)
* Not on iOS (suggested twice)
* 64-bit version on Windows
* Japanese users are too lazy to consider to change their daily browser. Now IE occupies the market. Behind in market share.
* No integrated service other than search
* Compatible with the local commonest IE-only web sites
* Too hard to diagnose crashes
* Too hard to config sync
* Setting on release version will crash Nightly and then the setting will return to default setting. SOmetimes can't add new tabs in release version.
* "Slow"
* All addons not compatible with all versions of firefox.
* FF 25.0 unstable
* Does not integrate with platform/rest of OS
* Feel at home on Mac. No other browser but Safari does: * Don't ever change which menus are showing. That's weird. * User OS_standard text-editing key shortcuts. Option-leftarrow should use the same word boundaries as TextEdit.
Firefox (Desktop and/or Android)**Opportunities**
- Better Sync experience
- Designing for multi-user devices
- Intuitive UI for multiple profiles
- Multi-screen
- Enable me to stop browsing at one device and continue in another device
- Sync my (web apps) across my devices
Streamlining product UI
- Contextual profiles for UI management
- 80/20 focusing on the most used features
- Designing for more practical defaults
- Integrate tabs, tab groups, bookmarks
- Do not play autoplay Youtube videos in background tabs
- Do not resume audio on background tabs on resume
- Indicate which of my tabs are playing audio -- and help me get to them directly
- Better tab switching on Firefox for Android
Streamlining Performance
- Unload unused tabs from RAM
- Optional/smart page prefetching
- Perception of speed for page loads
- Web compression
- Make Firefox for Android use less space for unmovable profile
- Ship Electrolysis fast!
- Zipped and much better App Cache
Building up user competency
- Better interactivity with web content
- Help mode (reference: Sketch for mac app)
- with other services like dropbox, pinterest
Make life easier for Web Developers!
- Use F12 for Firefox Dev Tools
- Security by Electrloysis
- Add-on permissions
- Web content sandboxing
- Dev tools -- ability to save CSS + HTML + JS in the browser + share with others for feedback & learning
- Better Source code nagivation with the tools
- More article case study - developer tools for firefox
- Champion Firefox as a gaming browser: Enable continuous gaming through cross-device integration (leave off at one place and start with another)
- Interoperability within web apps
- More SWAG
- Promote easier content discovery
- More language support -- better language grouping and ordering in preferences
- Providing shortcuts for better accessibility
- Communicate more about what Mozilla is offering – Tell us more Mozilla ideals, values
- Could build an OS that has browser capabilities rather than building a browser with OS capabilities for desktop (inspiration: look at Coast by Opera)
- iOS
- native HTTPS
- Instant user support via WebRTC/chat, screensharing video
- Navigation page in China, Japan, Korea users hard to type because (input character) users prefer click rather type in. Local popular site directory (a popular site pattern in China)

- Privacy (Collusion,…)
- Backwards compatibility
- We are different as a compaby
- We care about users
- Passionate add-on community
- Promoting security more than other browsers

- Fennec is not cool
- Safari, Chrome, IE, iOS
- Optimize private browsing mode
- Finance: we only get money from Google at the moment
- Not playing well between the devices/platforms
- Balancing personalization vs complexity
- Not having a strong enough brand identity
- Losing developer mindshare
- Reputation for low performance
- Support for Flash
- Tendency towards closing down add-ons, plugins…
- Closed mobile platforms
- Complification of browser
- Less users from indie localized
Firefox (Desktop and/or Android)I love the concept of multiple profiles in Firefox, but there's no UI to manage them.

The closest I've found is the profileswitcher addon, but it doesn't have a way to set icons for different profiles that you run at the same time.

Would be quite appreciative of this! Users would greatly benefit from understanding profile management for privacy, security, and performance reasons (different addons for different browsing purposes)
Firefox (Desktop and/or Android)Hi, I think the way we actually share content in the internet can be improved. Today, sharing is done either by downloading the content or manually copying the url, then uploading / paste it again in the website / the social network we want. The other way is provided by the social buttons, which are really heavy (lot of js etc loaded, on mobile it's annoying) and really bad about privacy (the social networks can track you everywhere with these iframes).

So the idea is to complete the right click menu, adding "share on this website" action in addition to the actual "download image" and "copy link" actions. The websites available in this menu could be set in the firefox settings (diaspora*,, Facebook, Twitter, Tumblr, Pinterest, google+, wordpress, etc...)

Once that is done, we can even propose to the user to block the now useless like buttons, obtaining better speed and privacy.
Firefox (Desktop and/or Android)Generate and provide a SHA1024 signature for each binary image and plugin that we generate and provide to a well known site, that is both independently verifiable by users as well as by the binary so that users can detect alteration or intrusion by malicious parties.Yes, by making the user properly paranoid while increasing awareness of how to avoid being compromised.
Firefox on IOSiOS is one of the leading mobile operating systems out there today, many are getting online for the first time on iOS devices from iPhones to iPods to iPads. We think that it is time a Firefox app was built for iOS.
Firefox OSA compact Firefox OS keyboard (like the feature fone keyboard - T9)
In our Firefox OS target market it will make an easier usability transition for people who've had feature phones and phones with physical keyboards.
The keyboard is the primary interface element for sending text messages and writing emails and a poor experience here reflects badly on the whole usability of the phone.
Most of our shipping devices have small screens and the compant keyboard makes it much easier to type on it (especially on smaller screens).
For elderly and people with limited dexterity having larger key buttons will improve accessibility.
Fairly easy to implement as we have multiple keyboard support already.

Problems to solve:
Educating the user on the different keyboards
Implementing setup - include it in the FTU screen?
This idea could probably be done in a hackday by enthusiastic community members.
Firefox OSFirefox OS Game
Having How-To's 101, 102, 103 to help developer learning game building.
We need to make sure the Firefox OS Team can have time to help people writing those How-To's
Work with gaming partners on writing such contents.
Publish this on MDN on a Game "Zone"
Firefox OSEmergency push notifications for natural disasters (and eventually monitorization of radio emergency frequencies)We could work with government agencies to promote standardization for emergency notifications.
Firefox OSKill packaged widgets. Figure out how to trust the trustworthy parts of the web. Combine the "whereness" of a site and hence the site-specific trust users have grown during years of being netizens with powerful web/device APIs. That's when the web becomes our platform. (Oh, and fix offline so no "widgetmarked" site/app will ever go 404 pn me.)We could integrate with "Web of Trust", or make our own trust directory - or both. Volunteers can help with reviewing and nominating websites.
Firefox OSThe current situation of typing on FFOS could be improved, especially by improving the keyboard's responsiveness - the delay between the phone picking up two keypresses.

This is important for more than "speed" reasons. Typing is one of the main interactions the user has with the phone and if this experience is frustrating, the user will just want to use something else.

In order for the devs to actively work on this, we need to have a consistent way of measuring the improvement. We should have an automated test that sends keypresses to the device at a frequency similar to that of a human and count how many keys the device registers.

It might be doable with Marionette and Eideticker or even sending inputs to the input driver directly.
It seems that we already care and work very much on app responsiveness (especially startup time) - we are sure there must be other parts of the community who would be interested in improving responsiveness in other parts of the FFOS experience - like typing!
We could grow participation on this project by engaging people interested in increasing performance outside of app-startup.
Firefox OSACCESSIBILITY!! Make accessibility very easy, for all disabilities. Some specifics - make it easy to:

- Change contrast and colors, including background colors
- make it easy to resize text everywhere
- audio options across the board.
I'm sure there are plenty of communities that can help with that.
Firefox OSAdd compatibility for more devices, specifically higher end devices

* Support for Samsung Phones, Nexus, ...
* Promote "It Now it works on …" to make developers happy
* Pilot Program on the kind of hardware you are used to
* Intended Audience: Web Developer + Enthusiasts Community, not consumers
* Privacy concerned users
* Allow booting both android and ffxos?
Get a wider range of people using Firefox OS without requiring them to have the experience to port to new hardware. Targets especially webdevs that don't have hardware experience and the higher end devices enthusiasts.

Focus on Software, not the Hardware
Makes it more attractive in terms of status
Dual Booting: Completes functionality, in case something doesn't work. Provides comparison.

Putting in the money for a high end device will make you expect everything works smoothly
Market may be different, different expectations --> Developing for the wrong audience
Performance on low end devices might decrease

More diversity through multiple versions of the OS
Expand developer base both for core and for apps
Marketing opportunities through brand recognition

Only one chance for entry into target markets
Bug management, higher volume of bugs
High demand for supporting more devices diverts attention from lower end markets
Firefox OSVoice Browsing: ask for a website to be read with your voice and the website is read back out loud to you in Firefox OS and possibly the android client.University research collaboration on voice technologies.
Partnership with cloud voice technology companies.
Collaboration with existing open source projects.
Firefox OS- Inclusion of well know mobile manufacturers, big players on the market (Sony, LG, etc.)
- Top 20 apps from Google Play and App Store must be ported to Firefox OS
- Accessible prices for low end phones on emerging markets and also accessible high end phones for developed markets
- Easier start to develop an app compared to competition (learning slope is easier)
- Alternative marketing strategy: Phone are cheaper than marketing campaigns
- Programing sprints to start developing process inside community
- Phone for the best app events (Develop a similar app that is on Android or iOS top 20 list)

Firefox OSWe are thinking about the os being a global game changer, reaching a vastly different market economic set.Merge the concepts, the FEELINGS, with the marketing. Mozilla Missionaries -- the Next Frontier. Make it feel like religion.
Acknowledge and actively engage and reward Contributors
Keep the price point low, if not free.
Free Apps!
Make it easily usable and translatable to those that are not technical and don't use technology as their primary point of contact today.
Online tutorials.
Library sessions, like "office hours" for those willing to teach those that are looking to learn.

Firefox OSWe're trying to connect the world through Firefox OS in a true, Mozilla way.

1. Seek out donations from developed countries in the form of old phones which are obsolete. Make it like a food drive but for old phones. These are likely more powerful and MUCH MUCH cheaper if not free compared to our FFOS launch devices.
2. Create a super light weight version of FFOS which has all the new technology users would want...
+ Camera
+ Browser
+ Phone
+ SMS / What's App

No other apps since everything else can be accessed through the browser. There would be no app grid, just 4 panes the user can swipe to and from.

3. Get Mozilla eng. to flash these phones and ship them to areas in the world with low internet penetration
In these more remote areas internet access is going to be limited. By pass the carriers. Set up our own wifi tower and use mesh networks to distribute the internet within each community.

Each person connected with our phone becomes part of the internet and in turn part of a greater community.
Firefox OSShape Environments
FFOS in 500 Lanuges
Tayloring customization for regions
Wireless mesh
Larger community influence
Grow with the audience
Create off polities to engage the community
Using FFOS as a teaching tool

Product builds

Larger community influence

Teach and learn
FFOS as a teaching aid
One laptop per child - slow devices, FFOS as an alternative

Create be ideas to engage communities
Progress openness
Not comprising in openness

500 languages
South east Asia
Encouraging development throug open hardware

Getting people up to the newest os more quickly -

Mozillians using with nothing but FFOS.
Make it easier to contribute.
Too much ramp up time to contribute.
Open hardware

Developing FFOS drill run on devices (ie android, iOS, hp, bb)
Developing drivers to access cameras, mice, speaker, on other Orem phone. Flashing FFOS to the device and have them accessing all the hardware from ALL the different oems. Old or new. Ultimately repurposing all old devices as new devices running the lasted FFOS.

PCs running FFOS!! Changing the Gaming industry!!!

Built in tools for anonymity online

Open updates out of the box

Antiquated phones
Flashing FFOS on all devices old and new. Giving FFOS the ability to access drivers across the board from all oems. All the old devices sitting in our draws will be new FFOS devices that are relevant, viable and modern!!
Firefox OSFxOS on Appliances: WebAPIs for TV, fridge, thermostats, cars! Unified user experience across them all

Mozilla Persona and Cloud as trustworthy middlemen for peer-to-peer messaging, queuing, rendezvous
Mozilla's real data flows (Bugzilla; wiki) need to become more like the social apps people already use.
Firefox OS- one tablet/phone/device per child, with connection between them sharing also internet
- internet for every child in places that don't have access nowadays
- interface of FxOS plug'n'play for every kind of device switchable, easy to make your own even when not a developer
- add hoc networking
- oportunistic anonymous data sharing about traffic conditions from one car to another, about public communication, delays, the real time to travel, etc - also without internet access just from one device to another without anyone's action limited to a few meters
- devices for impaired people
- new input methods like tracking eye movements to help people after some serious accidents who cannot communicate otherwise
- run a pilot in Latin America / Africa where every person can have a device, start developing, reference to how FxOS changed your life
- one click install - transform your android dev into a FxOS in minutes

- phone in the cloud - don't have my phone with me but have dev with internet access, log in to the side, get the interface, all my contacts, voicemail - profile in the cloud

- phone encryption
- FxOS corpo - not just blackberry and iphone
- a device that you don't need a carrier network to call but can make calls between themselfs, even using others as a relays
- native voip integration
- ad-hoc audio-video conferencing system for groups bigger than just 2-3 people but also large ones formed just from the phones people have with them
- one click install to bring the android users to the FxOS
- the FxOS village idea with dev communicating and people can share content (webmaker integration?)
- universities participation - FxOS lab, place for a new ideas to be not just born but also realized
- every user is a developer, make it easy to become an active user of the web
Firefox OS* Create a Mozilla controlled reference device available direct to consumers worldwide
* Support a wider range of devices
* Ability to flash any device with Firefox OS with maintainers for particular ports
* Globally connect app developers to local content providers
* Follow through on promise of multiple app stores and cross-platform apps
* Evangelism inside big companies
* Make a reference device available to everyone
* Inform people who buy a device about Mozilla and their mission
* Better tools and documentation for contributors - a single point of entry for people to learn how to help
* Educate partners about community contribution
* Turn phone users into advocates & spokespeople for Mozilla
Firefox OS1. Develop an open messaging app system.
2. Develop better multi-tasking experience.
3. Allow people to get Firefox OS on "their" phone.
4. Provide a localization mode to more easily localize Firefox OS.(eg. developer mode).
5. Make apps off-line compatible to work without connectivity.

1. Provide a process for community reps to get funding to set up a local office for community meetings and co-working.
2. Use open hardware along with open software.
3. Partner with organizations that could provide medical and education information (off line).
4. Allow the community to easily customize the apps that we ship on the device (under open licenses)
5. Facilitate localization of apps

Firefox OSDesperately need whatsapp
Maybe higher end phone because I tried using fxos on Keon ( the orange one ) and the edge of the screen isn't very responsive.
Firefox OS- performance
- look & feel
- apps diversity
- Involve QA
- Spread the word about FF OS
Firefox OS- More apps (YouTube, Facebook, Dropbox)
- More call details (call length, etc.)
- Speed dial
- Search by name
- Embedded machines support (cars, TVs, boards, vending machines)
- Port on as many phones as possible
Firefox OSDevices:

- more powerful devices
- only a feature phone replacement
- support smart appliances
- strength / opportunity launching in feature phone areas
- more device categories


- improve performance
- select/copy/paste text on web pages
- resending messages - copy/paste
-performance, look and feel
- better keyboard
-back button too small
- the 4 corners in the screen are not responsive
- responsiveness
- make starting the phone app fast

- need more apps
- better default local apps on device
- missing top 100 apps
_apps diversity
- easy to do own app
- add secure im
- more games
- IM app
- dropbox like cloud background apps
-more educational apps
-more GPS

- outreach more countries
-enable testing community through devices
-local community training
- technical - local support through community
- events/training
- involve qa
- do people care if its open? or easy to make apps
- ff is: integrate into education system, develop training materials,support training

- language packs
- localization apps and interface

- provide sensors api such as temperature
- more apis for low level
- connect to Bluetooth keyboard
-limited open APIs for devs

- less restrictions on ff is branding more open
-more marketing, promotion materials
-os competition
-weakness finance

- easier to share content
-pin contacts to home screen
- provide an interface to let 3rd party to provide media source
- hand write ime
-voice command
- more customizations - ringtones etc
- generic media source
-online updating
-share phone,screen-webrtc
-sync contact data cloud

-fragmentation, stop cannibalizing our resources
- need more documentation at lower layers of fx is
-social api for fx is
-insrant user support via webrtc/chat/screen sharing video
-longer battery
- nfc and WiFi direct
-support ff is on embedded machines like vending machine
- port ff os as many phones as possible
Firefox OS= FirefoxOS =

Easier to get dev phone in every country.
Font customization.
Benchmark for high quality.
Benchmark for high quality game developing, to avoid user get awful experiments only after install and play it.
In-app purchase (payment) API.
Design an Ad broadcasting mechanism to attract more App developers.
Semantic Webapp (Semantic Web + Webapp search, etc.)
Native extensible module API in C/C++, or even in Rust like Node.js, for performance, close source and some "necessary" dirty works.
More friendly developing tutorial/documents
Add-on api for FirefoxOS (system level add-on installation, marketplace)

= Marketplace =

Better notification if 1 try to use an internet-required app without network
Multi-language for information of application on MarketPlace (by the language user used)
Disable malware [remotely] (click to show a message about reason)
Bind applications with Mozilla account (Persona?) so that all my devices can have the same app list
Can purchase books, music and other non-app categories without install new apps.
Firefox OSThe availability of convenient apps will determine the feelings that the users have toward the platform, and will ultimately determine if users will recommend Fx OS devices to their friends.

The following ideas relating to apps were discussed:

* Guitar tuner app
* Notepad app
* Calculator app
* Voice recorder app
* Get more large companies to port their apps, like Spotify and Netflix, Instagram, banking services, Snapchat
* Open Source, hackable, music streaming service. DRM free!!!
Firefox OSa decent Text-To-Speech system
CMU flite is more customizable
need more documentation and support on how to integrate a custom built TTS engine into Firefox OS,
Firefox OSSystem usability is a major success factor. The designers must design for what is convenient, as well as what looks pretty on the device.

The following concrete issues were discussed:

* Make privilegied APIs available to less privilegied apps. (So that it's easier for web apps to use functions that are normally unavailable to web pages). Developers will love being able to access the hardware.

* Function to adjust brightness is missing

* Larger lockscreen lockpad buttons: Easier to hit, harder to miss. Like in iOS 7. Make Cancel and Emergency call buttons a tad smaller, maybe just a text string, so it's easier to avoid hitting them when using "7" and "9".