Some time ago, I built a Chrome extension called Teduh Unit Counter to help property buyers browse TEDUH more conveniently. The earlier version has since been marked deprecated after TEDUH revamped its website and removed the old direct, URL-friendly experience.
In the old version, the extension depended heavily on the webpage UI itself.
It needed the TEDUH page to load first, then it would read and extract the information shown on screen. That approach worked before, but it became much more fragile once the new TEDUH frontend was introduced.
What changed in the new version
The revived version now works in a very different way.
Instead of depending on the TEDUH webpage UI to expose the data, the extension now retrieves the information directly from TEDUH's server-side endpoints. This means the extension no longer needs to rely on opening a specific project page and scraping the rendered page content just to get the data.
From a technical point of view, this is a much stronger foundation than before.
Why this is better
- Lookup is faster because the extension requests the data directly
- It is less dependent on TEDUH's frontend layout and modal flow
- The user experience is cleaner because data retrieval no longer depends on page rendering
- The extension is now easier to maintain when the website UI changes again
What remains in real time
The project details and unit list are now retrieved live whenever a lookup is performed. In that sense, the extension now gives a real-time TEDUH lookup experience in a more direct way than before.
The trade-off
There is still a trade-off.
The old version was tightly coupled to the TEDUH webpage flow, so some page-specific observations were easier to derive directly from what was visibly loaded in the browser. The new version no longer depends on that rendered UI layer.
However, this does not mean newly sold tracking is completely gone. The extension still keeps track of newly sold units by comparing the latest fetched unit statuses with the previously saved local snapshot. So the feature still exists, but it is now based on local comparison logic rather than depending on the TEDUH webpage display itself.
Why I think this is the right direction
The old extension solved a real problem, but it was tied too closely to the website structure. Once the TEDUH frontend changed, the original approach naturally became outdated.
Rebuilding it around direct server-side data retrieval makes the extension more practical, more stable, and more future-resistant. It also makes the TEDUH experience much more convenient again for users who just want quick access to project information without clicking through multiple layers of UI.
Final note
So yes, the TEDUH Chrome extension is back.
This time, it is not just revived. It has been rebuilt on a better approach.
The previous version depended on the webpage. The new version talks to the data source more directly. That is the key difference, and it is exactly why the new version now comes back stronger than before.
