Webmaker/2015/MakerFox: Difference between revisions

From MozillaWiki
< Webmaker‎ | 2015
Jump to navigation Jump to search
Line 14: Line 14:


=Key Initiatives=
=Key Initiatives=
* ''to come''
* The Webmaker concept could be a real way to differentiate and grow market share for Firefox, especially on mobile.
* However, this idea is not yet supported by evidence or working products in market.
* In 2015, we will create a cross-Mozilla MakerFox Tiger Team project to do product exploration in this area.
 
* '''Target market''': learners, bloggers, redittors etc. Especially those not currently on Firefox.
 
'''Things this team might invent / test / recommend:'''
* Rebrand Webmaker App as Firefox Makes or MakerFox or something
* Build a maker-centric version of Firefox Desktop or Android. Like the developer browser but for larger audience and integrating Webmaker features (e.g. MakeDrive).
* Integrate Webmaker App features into Firefox for Android in major way.
* Add maker-centric features to Firefox Desktop (e.g. right click on image gives you more advanced capabilities).
* Bundle Webmaker App in Firefox OS / doing product marketing on this.
* Webmaker-friendly business development opportunities for Firefox (e.g. revenue share deal plus integration w/ SquareSpace or a storage provider like Amazon).
 
'''Engaging our volunteer and supporter community will be key in making this happen.'''  
* e.g., generate new ideas for features / offerings via a design challenge with design schools and our community. Or run a community ‘barn raising’ to get coders actually building a MakerFox version for Firefox (Q2?). Participation will be key.
* This group would include people from different teams with a mandate to act boldly and with a great deal of autonomy. No sacred cows allowed.
* Leadership would happen in the Webmaker product group, with participation from Firefox team, MoCo Brand and Seneca College.
* The team would have clear quarterly targets re: what things to test. Ideas with no traction would get killed quickly.
 
 
 
 
 
Firefox and MoCo Brand teams: active participation in the Lab including setting goals and assignment of staff.
 
Services: this may also be an environment where we can test out some of the new concepts that will emerge in Firefox Accounts. If so will need Services involvement.
 
Funding: most likely needs to be fully funded internally. MoFo can assign some existing Webmaker staff and $100k Seneca funding. But likely need small headcount and additional Seneca funding.


=Milestones=
=Milestones=

Revision as of 16:59, 7 November 2014

Vision

  • What we're building. Why. How it fits into the overall picture.

df70t5s6.png

Goals

  • What are the top-level 2015 goals for this part of the initiative?

Before & After

  • Before. Where do we stand now? (one paragraph)
  • After. What this will look like in Dec 2015? (one paragraph)

Metrics

  • to come

Key Initiatives

  • The Webmaker concept could be a real way to differentiate and grow market share for Firefox, especially on mobile.
  • However, this idea is not yet supported by evidence or working products in market.
  • In 2015, we will create a cross-Mozilla MakerFox Tiger Team project to do product exploration in this area.
  • Target market: learners, bloggers, redittors etc. Especially those not currently on Firefox.

Things this team might invent / test / recommend:

  • Rebrand Webmaker App as Firefox Makes or MakerFox or something
  • Build a maker-centric version of Firefox Desktop or Android. Like the developer browser but for larger audience and integrating Webmaker features (e.g. MakeDrive).
  • Integrate Webmaker App features into Firefox for Android in major way.
  • Add maker-centric features to Firefox Desktop (e.g. right click on image gives you more advanced capabilities).
  • Bundle Webmaker App in Firefox OS / doing product marketing on this.
  • Webmaker-friendly business development opportunities for Firefox (e.g. revenue share deal plus integration w/ SquareSpace or a storage provider like Amazon).

Engaging our volunteer and supporter community will be key in making this happen.

  • e.g., generate new ideas for features / offerings via a design challenge with design schools and our community. Or run a community ‘barn raising’ to get coders actually building a MakerFox version for Firefox (Q2?). Participation will be key.
  • This group would include people from different teams with a mandate to act boldly and with a great deal of autonomy. No sacred cows allowed.
  • Leadership would happen in the Webmaker product group, with participation from Firefox team, MoCo Brand and Seneca College.
  • The team would have clear quarterly targets re: what things to test. Ideas with no traction would get killed quickly.



Firefox and MoCo Brand teams: active participation in the Lab including setting goals and assignment of staff.

Services: this may also be an environment where we can test out some of the new concepts that will emerge in Firefox Accounts. If so will need Services involvement.

Funding: most likely needs to be fully funded internally. MoFo can assign some existing Webmaker staff and $100k Seneca funding. But likely need small headcount and additional Seneca funding.

Milestones

  • to come

Dependencies

Collaboration / Partnerships / Needed resources

  • to come

Links

  • helpful added context or documents