Client work · Case study

Taking over and developing a weather application

The client needed to continue developing a system that the original developer no longer had time for. I helped build on the existing work, reduce the risks of making changes, and gradually add new features.

JavaScript · HTML · XML APIPlaywright · AI-assisted testingLong-term collaboration
Weather station dashboard with charts for wind, temperature, humidity, pressure and energy. Current readings include wind at 1.2 m/s, temperature at 17.5°C, humidity at 73% and pressure at 1015.0 hPa.
ProjectWeather data visualization application
My roleTaking over the codebase, analysis, development, and support
TechnologiesJavaScript · HTML · XML API
CollaborationOngoing updates across several stages

The brief, solution, and outcome

Project overview
1

The brief

The original developer no longer had the capacity to continue. The client needed to develop an older web application that communicated with a weather station microcontroller via an XML API. The project had no technical documentation or automated tests.

2

The solution

I first familiarized myself with the code and clarified the requirements with the client. With the help of AI, I quickly created basic Playwright tests to verify selected aspects of the existing behavior. This was followed by bug fixes, a more configurable dashboard, and new visualizations of wind and lightning activity.

3

The outcome

The client was able to continue developing the product without the original developer. A one-off engagement grew into ongoing collaboration across several stages, without the need to completely rewrite the existing system.

Approach to collaboration

Ongoing review and transparent estimates

I did not charge for the initial consultation and analysis. For each change, we agreed on an hourly rate and an estimate of the work required in advance.

We reviewed the results regularly to confirm as early as possible that they matched the client's expectations. If a major issue arose outside the original estimate, we openly agreed on how to proceed.

Given the lack of tests and documentation, it was important to balance technical debt, the risks of making changes, and the benefits to the client. The goal was not a complete refactoring, but meaningful product development.

Have a similar project?

Do you need a new website, changes to an existing application, or a discussion about AI possibilities? Get in touch and we can find a sensible way forward together.

Discuss your project →