Clarifying the Codebase: Why “Working in Prod” Doesn’t Mean It’s Done Here

[Anastasiia-Svechnikova]

Hello everyone! 👋

We’ve noticed some confusion around issues that seem to be already implemented in production. Just to clarify:

• Our current production app is based on an older codebase that is no longer scalable.

• This repository represents a completely new codebase, built from scratch.

• We're in the process of migrating all existing production features into this new project.

• Once the migration is complete, we’ll begin adding new enhancements.

So if you see an issue for something that “already works in prod,” it just means it hasn’t been ported yet.

Thanks for your patience and contributions! Let’s build something great together. 🚧

[tobymurray]

I think it would be very valuable from a project success perspective to have an "official" deployed version of the code in this repo. I don't think it should, in the short term at least, have any impact on the legacy map (both can coexist).

Is AirGradient up for hosting this project? I know there was mention of on-prem servers, so maybe a cheap way to sneak this relatively lightweight page onto the public internet. Not suggesting it be broadly publicized until it's ready, just having it accessible at all makes this project more compelling.

[airgradient-achim]

Yes we discussed this today and we will bring the new map app onto a server in the next few days so that people can actually see and experiment the new version.

[airgradient-achim]

Here is the "official" deployed version. Since the app is very early, this is our integration server.

https://map-int.airgradient.com/

Once we have achieved rough feature parity with our old app hosted at https://www.airgradient.com/map/
we will deploy this new code base to replace it.