B2G/MarketCustomizations: Difference between revisions
< B2G
Jump to navigation
Jump to search
(Created page with "==Q&A== '''How to store per-market customization configurations in a private repo?''' '''How do you build the product with a specific market's configuration? '''What is in a p...") |
(→Q&A) |
||
| Line 2: | Line 2: | ||
'''How to store per-market customization configurations in a private repo?''' | '''How to store per-market customization configurations in a private repo?''' | ||
* Store each of the files changed only. | |||
* Currently these are in various locations in the filesystem. | |||
* For v2, we should consolidate to a single location, similar to the branding directories we have for Gecko. | |||
'''How do you build the product with a specific market's configuration? | '''How do you build the product with a specific market's configuration? | ||
'''What | * Copy your changed files into a checkout of Gaia, and build using that modified Gaia. | ||
'''What can be customized per-market?''' | |||
* | * Installed locales | ||
* | * Default locale | ||
* | * Default keyboard layout | ||
* Branding names and | ** (or is that set automatically by the locale choice?) | ||
* | * Bundled 3rd party apps | ||
* Application grid contents and positioning of apps | |||
* Branding names and logos | |||
* Licensing | |||
* In-app payment provider configuration | |||
* Settings App | |||
** Device Information - Model (name or #) | |||
** Device Information - Legal Information link or content | |||
** Help - Online support link | |||
** Help - Call support phone number | |||
** Help - User guide link | |||
* Browser default bookmarks | |||
'''How and where do you define a customized app grid layout?''' | '''How and where do you define a customized app grid layout?''' | ||
Revision as of 18:58, 5 December 2012
Q&A
How to store per-market customization configurations in a private repo?
- Store each of the files changed only.
- Currently these are in various locations in the filesystem.
- For v2, we should consolidate to a single location, similar to the branding directories we have for Gecko.
How do you build the product with a specific market's configuration?
- Copy your changed files into a checkout of Gaia, and build using that modified Gaia.
What can be customized per-market?
- Installed locales
- Default locale
- Default keyboard layout
- (or is that set automatically by the locale choice?)
- Bundled 3rd party apps
- Application grid contents and positioning of apps
- Branding names and logos
- Licensing
- In-app payment provider configuration
- Settings App
- Device Information - Model (name or #)
- Device Information - Legal Information link or content
- Help - Online support link
- Help - Call support phone number
- Help - User guide link
- Browser default bookmarks
How and where do you define a customized app grid layout?
Is it possible to define whether an app is removable in the homescreen configuration?
How do you add a preloaded packaged app to the build?
How do you add a preloaded hosted app to the build?
How do you prepare a preloaded hosted app for initial offline support?
Process Questions
- Is it better to have specific bugs for each app on a homescreen grid, or just one bug per layout per market?
- How to deliver/retrieve code for pre-loading? Manual delivery of assets, or suck it from a live app?