Historical low info from the extension becomes less relevant after a price raise

Open
#129 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by reviewing how the extension displays historical lowest prices on Steam store pages and how the SteamDB /sales page categorizes discounts. Compare the listed game examples and decide which proposed presentation best handles price raises; done means users can distinguish outdated historical lows from relevant post-raise lows.

Written by the indexing model from the issue text.

Description

enhancement

Steam updated their recommended regional prices at the end of October, and some publishers already raised their prices. In some regions, like Turkey and Argentina, new price is up to x5 higher than it was. This also means, that while "SteamDB lowest recorded price is" is still correct from the historical point of view, it is not practical anymore in such cases, since you can't rely on it when making purchase decisions, cause you probably won't see it being that low ever again.

Maybe, when the lowest price date is earlier than the last price raise, a red asterisk can be shown after the "lowest recorded price" with "price was raised to N at date" tooltip at hover? Or, you could even move the old lowest data to that tooltip, and display "lowest recorded price after base price raise is" instead by default.

This can be useful not only for the extension, but for SteamDB /sales page too. Right now most discounts from affected games fall into the plain "not green or blue" category, and will be filtered out, which means any discount progression may be missed in the future, unless you follow specific games closely and read their graph on sales.

Proposed changes will also be useful for Early Access games, since they tend to raise prices incrementally before the release, and relying on the extension historical price data on the store page means that you may miss a good discount thinking to wait for that historical low again.

Some game examples:
https://steamdb.info/app/877810/
https://steamdb.info/app/977880/
https://steamdb.info/app/894020/
https://steamdb.info/app/370020/
EA:
https://steamdb.info/app/1217060/
https://steamdb.info/app/1160490/
https://steamdb.info/app/758870/
https://steamdb.info/app/1794680/
https://steamdb.info/app/1227650/

Dominant language
JavaScript
Stars
1.2k
Forks
96
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SteamDatabase/BrowserExtension

All issues in SteamDatabase/BrowserExtension

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.