CPU performance API interest for use in Adobe web apps
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
I just wanted to chime in that there is a lot of interest in this CPU performance API for Adobe web apps. This would allow us to create fallback experiences for app features that aren't performing as well on less capable CPUs, or to progressively enhance the experience to best match the device's CPU capabilities.
I can imagine this would be quite helpful for numerous of our public facing web apps, including these, and more to come:
- Photoshop
- Illustrator
- Lightroom
- Firefly
- Frame.io
- Express
- Acrobat
I agree that a small number of performance buckets seems like the correct approach, and having buckets that do not change over time (so a tier 4 CPU will always remain a tier 4 CPU, even when more capable CPUs are introduced) feels like the most useful approach for targeting the user experience correctly.
Very much looking forward to progress on this!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue describes interest in a CPU performance API for Adobe web apps, but names no repository files, tests, or entry points. There is no defined implementation scope or completion condition to follow; the API design and desired change would need clarification first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100