- 1 Development Team
- 2 Design Specs
- 3 Source Code
- 4 IRC
- 5 Code Style Guidelines
- 6 Filing bugs
- 7 Handling bugs
- 8 Project Management
- 9 Some future development
- 10 The Gecko API for Mobile Messaging
- 11 Security Review
You'll be able to find the current team on the Firefox OS modules page.
The SMS team is part of the larger Comms team.
Versions specific specs
For 2.1, 2.2 and 3.0 we had no visual refresh so we have no visual design specifications. The specifications for the Right To Left work are common to all apps and can be found on box.com (mirror on bugzilla).
For 2.0, the Visual Refresh specifications are on bug 950175.
For 1.4, please visit :
- https://mozilla.app.box.com/shared/yt7hl2leikogcuili7kp/1/1578257617 for the Wappush DSDS spec
- https://mozilla.app.box.com/shared/yt7hl2leikogcuili7kp/1/1425004300 for DSDS UX spec
- https://bugzilla.mozilla.org/show_bug.cgi?id=947139 for the DSDS Messaging Visual Design spec
For 1.3, please visit https://mozilla.app.box.com/shared/0u4jt353ei9ov2c150ip/1/1170795225 (for the generic specs) and https://mozilla.app.box.com/shared/0u4jt353ei9ov2c150ip/1/1206603879 (for DSDS)
The following link contains the specifications for versions 1.0, 1.1 and 1.2: https://mozilla.box.com/applications/1/864518430.
Mirror for the UX spec for version 1.3: File:FFOS MessageApp V1.3 20131125 V8.0.pdf.
Mirror for the UX spec for versions 1.1 and 1.2: File:HTML5 SMS-MMSUserStorySpecifications 20130503 V8.0.pdf. This spec is still the authoritative one for anything that has not been redesigned.
Mirror for the UX spec for version 1.0: File:HTML5 SMS 20121212 R2S1 V8.0.pdf
The source code can be found in the gaia repository in github.
You can find us on the IRC server irc.mozilla.org, channels #gaia and #gaia-messaging.
Code Style Guidelines
You can file bug on Bugzilla. Please include the Firefox OS version you use, and possibly a screenshot or a video. Any console from logcat is welcome as well, or you could provide your message sqlite from your device by retrieving the following file & directory(if you don't mind the content):
There are 2 goals:
- making the bug move forward thanks to other people until it's actionable.
- not forgetting an important bug
With this flow, we still need to be careful to:
- assigned bugs without activity
- needinfo that are not answered
Indeed these bugs could still be forgotten if they don't move.
We try to follow the Scrum methodology. Please have a look to the SMS Scrum Page for more information.
Some future development
Using datastores for SMS
Haida and Sheets
New Gaia architecture
The Gecko API for Mobile Messaging
The SMS application uses several API from Gecko. Especially it uses the API for Mobile Messaging, which allows to send and receive SMS and MMS.
On this wiki, several pages show the design behind the API: WebAPI/WebSMS and WebAPI/WebMMS. They're probably somewhat obsolete noawadays but they will provide useful information about some design.
MDN has also a good documentation about this API. It's also lagging a bit but is more uptodate.
Finally, the most current information is given by the IDL files in the gecko tree (and some part is in a separate place).
The security review for this app can be found here.