Marketplace/Performance optimization: Difference between revisions

No edit summary
Line 10: Line 10:
The short version is that we need to optimize things that should be optimized regardless of other constraints (device constraints, network constraints, etc). Only then can we differentiate between strategic investment and Doing Things The Right Way.
The short version is that we need to optimize things that should be optimized regardless of other constraints (device constraints, network constraints, etc). Only then can we differentiate between strategic investment and Doing Things The Right Way.


At a high level, these are the strategies being considered:
At a high level, these are the strategies being considered for marketplace.firefox.com:


# [https://bugzilla.mozilla.org/show_bug.cgi?id=900241 Feature/Memory/Device detection (reliable) (900241)]
# [https://bugzilla.mozilla.org/show_bug.cgi?id=900241 Feature/Memory/Device detection (reliable) (900241)]
# Speed and Performance bugs, general at this point (see below)
# Speed and Performance bugs, general at this point (see below)
## Establish target benchmarks & KPIs for performance
## Establish target benchmarks & KPIs for performance
### low-bandwidth, cold
# Front and Back-end Performance adjustments (pending benchmark results -- currently the mark is "as fast as possible")
### high-bandwidth, cold
### low-bandwidth, warm
### high-bandwidth, warm
# Front and Back-end Performance adjustments (pending benchmark results)


Possibly Tarako-specific:
Tarako-specific:
# Front and Back-end Performance adjustments
# new "low resource" responsive state
## new "low resource" responsive state
# Filtering apps for "low resource" device
## Filtering apps for device (UI)
## payment flow slimming/changes?
# UI updates to accommodate RTL & other local language requirements (pending target markets)
# UI updates to accommodate RTL & other local language requirements (pending target markets)


== Open issues ==
== Open issues ==
Confirmed users
745

edits