What is Jetpack here for?

Who are the Jetpack team? What are they here for? A lot of people in Mozilla don’t know that Jetpack still exists (or never knew it existed). Others still think of it as the original prototype which we dropped in early 2010. Our goals have changed a lot since then. Even people who think they know what we’re about might be surprised at what our current work involves.

Let’s start with this basic statement:

Jetpack makes it easier to develop features for Firefox

There are a couple of points wrapped up in this statement:

  1. The Jetpack team doesn’t develop features. We enable others to develop features. We should be an API and tools team. We’ve done a lot of API development, but we should work with the developer tools team more to make sure that Firefox developer tools work for Firefox development, too.
  2. I didn’t say “add-ons.” I said “features”. The APIs we develop shouldn’t be just for add-on developers, Firefox developers should be able to use them too. If the APIs we create are the best they can be, then everyone should want to use them. They should demand to use them, in fact. It follows that this should make it easier for add-ons to transition into full Firefox features, or vice versa.

We happen to think that a modular approach to developing features makes more sense than the old style of using overlays and xpcom. All of the APIs we develop are common-js style modules (as used in Node and elsewhere) and we’ve built the add-on SDK to simplify this style of add-on development. That work includes a loader for common-js modules which has now landed in Firefox and is available to all feature developers. It also includes tools to take directories of common-js modules and convert them into a standalone XPI that can be installed into Firefox.

The next step in supporting Firefox and add-on developers is to land our APIs into Firefox itself so they are available to everyone. We hope to complete that by the end of this year and it will bring some great benefits, including smaller add-ons and the ability to fix certain problems in SDK based add-ons with Firefox updates.

Mythical goals

Jetpack has been around for a while and in that time our focus has changed. There are a few cases where I think people are mistaken about the goals we have. Here are the common things that were talked about as hard-goals in the past but I don’t are any longer.

Displace classic add-ons

Most people think Jetpack’s main goal is to displace classic add-ons. It’s obvious that we’ve failed to do that. Were we ever in a position to do so? Expecting the developers of large add-ons to switch to a different style of coding (even a clearly better one) without some forcing factor doesn’t work. The electrolysis project might have done it, but even supporting e10s was easier than converting a large codebase to the add-on SDK. The extension ecosystem of today still includes a lot of classic addons, and the APIs we build should be usable by their developers, too.

Forwards compatibility

Users hate it when Firefox updates break their add-ons. Perfect forwards compatibility was another intended benefit of the SDK. Shipping our APIs with Firefox will help a lot, as the add-ons that use them will work even if the specific implementation of the APIs needs to change under the hood over time. It won’t be perfect, though. We’re going to maintain the APIs vigorously, but we aren’t fortune tellers. Sometimes parts of Firefox will change in ways that force us to break APIs that didn’t anticipate those changes.

What we can do though is get better at figuring out which add-ons will be broken by API changes and reach out to those developers to help them update their code. All add-on SDK based add-ons include a file that lists exactly which APIs they use making it straightforward to identify those that might be affected by a change.

Cross-device compatibility

There’s a theory that says that as long as you’re only using SDK APIs to build your add-on, it will magically work on mobile devices as well as it does on desktop. Clearly we aren’t there yet either. We are making great strides, but the goal isn’t entirely realistic either. Developers want to be able to use as many features as they can in Firefox to make their new feature great. But many features in one device don’t exist or make no sense on other devices. Pinned tabs exist on desktop and the SDK includes API support for pinning and un-pinning tabs. But on mobile there is currently no support for pinned tabs. Honestly, I don’t think it’s something we even should have for phone devices. Adding APIs for add-ons to create their own toolbars makes perfect sense on desktop, but again for phones makes no sense at all.

So, do we make the APIs only support the lowest common denominator across all devices Firefox works on? Can we even know what that is? No. We will support APIs on the devices where it makes sense, but in some cases we will have to say that the API simply isn’t supported on phones, or tablets, or maybe desktops. What we can do, again by having a better handle on which APIs developers are using, is make device compatibility more obvious to developers, allowing them to make the final call on which APIs to employ.

Hopefully that has told you something you didn’t know before. Did it surprise you?

After an awesome Jetpack work week

It’s the first day back at work after spending a great work week in London with the Jetpack team last week. I was going to write a summary of everything that went on but it turns out that Jeff beat me to it. That’s probably a good thing as he’s a better writer than I so go there and read up on all the fun stuff that we got done.

All I’ll add is that it was fantastic getting the whole team into a room to talk about what we’re working on and get a load of stuff done. I ran a discussion on what the goals of the Jetpack project are (I’ll follow up on this in another blog post to come later this week) and was delighted that everyone on the team is on the same page. Employing people from all around the world is one of Mozilla’s great strengths but also a potential risk. It’s vital for us to keep doing work weeks and all hands like this to make sure everyone gets to know everyone and is working together towards the same goals.

Mossop Status Update: 2012-05-11

Done:
Submitted pdf.js packaging work for review (bug 740795)
Patched a problem on OSX with FAT filesystem profiles (bug 733436)
Patched a problem with restartless add-ons when moving profiles between machines (bug 74483…

Done:

  • Submitted pdf.js packaging work for review (bug 740795)
  • Patched a problem on OSX with FAT filesystem profiles (bug 733436)
  • Patched a problem with restartless add-ons when moving profiles between machines (bug 744833)
  • Added some quoting for the extensions crash report annotation (bug 753900)
  • Thoughts on shipping the SDK in Firefox and problems with supporting other apps: https://etherpad.mozilla.org/SDK-in-Firefox

Mossop Status Update: 2012-04-28

Done:
Fixed a likely memory leak in the SDK
Fixed a few warnings in the SDK code
More experimenting with pdf.js packaging
Fixing a bug that can stop bootstrap startup() from ever being called
Fx work week!

Done:

  • Fixed a likely memory leak in the SDK
  • Fixed a few warnings in the SDK code
  • More experimenting with pdf.js packaging
  • Fixing a bug that can stop bootstrap startup() from ever being called
  • Fx work week!

Mossop Status Update: 2012-04-13

Done:
Updated most Jetpack feature pages with reality
Additional Jetpack triage
Work week planning
Interviews
Fixed XULRunner universal builds
Working on pdf.js add-on blocking problem

Done:

  • Updated most Jetpack feature pages with reality
  • Additional Jetpack triage
  • Work week planning
  • Interviews
  • Fixed XULRunner universal builds
  • Working on pdf.js add-on blocking problem

Mossop Status Update: 2012-03-02

Done:
Phonescreens for new hires
Working on how to prioritise bugs for Jetpack
Fixing XULRunner stub dependencies (bug 706186)

Coordination: Trying to get back on the horse of posting t…

Done:

  • Phonescreens for new hires
  • Working on how to prioritise bugs for Jetpack
  • Fixing XULRunner stub dependencies (bug 706186)

Coordination:

Trying to get back on the horse of posting this every week

Mossop Status Update: 2012-01-13

Done:
Finalized the Add-ons SDK goals for Q1
Add-ons SDK work week planning
Finalized the new Toolkit module peer structure
Working on testing the new hotfix feature
Building test hotfix add-ons to ship out to beta users…

Done:

  • Finalized the Add-ons SDK goals for Q1
  • Add-ons SDK work week planning
  • Finalized the new Toolkit module peer structure
  • Working on testing the new hotfix feature
  • Building test hotfix add-ons to ship out to beta users

Next:

  • Post to the newsgroup about the Toolkit module peer changes
  • Find owners for all the Add-ons SDK goals
  • Write up the draft schedule for the Add-ons SDK work week

Mossop Status Update: 2011-10-29

Done:
Implemented a number of performance fixes for mobile (bug 696141 and dependents)
Reviewed more of the default to compatible work
Basic implementation for add-on hotfix (bug 694068)
Landed the final third-party add-…

Done:

  • Implemented a number of performance fixes for mobile (bug 696141 and dependents)
  • Reviewed more of the default to compatible work
  • Basic implementation for add-on hotfix (bug 694068)
  • Landed the final third-party add-on patches on aurora and beta
  • Product planning meeting for Firefoxes 8, 9 and 10

Next:

  • Finish the add-on hotfix work
  • Various HR stuff
  • Start planning Jetpack work week