Hi everyone,
I woke today feeling rested enough to embark on the promised custom app for the TMC supercharging game. My current job has kept me in the role of manager these last three years, which prevents me from doing what I love most .. coding .. something that has otherwise occupied my days for 30 years (this month). Three years is too long away, so this project is a way to do what I love while helping the super-cool Tesla community.
Since I'm not legally allowed to profit from this undertaking, it will be completely free and open-source. I will donate the hosting and domain fees, along with my time, which isn't a hardship because I have some under-utilized AWS instances that host a few websites I made during my 20 years running my own software company.
So what are building?
* web front-end using JavaScript, ReactJS
* two mobile apps using JavaScript, React Native (Android and iOS)
* backend using Java, Spring Boot, Hibernate, RabbitMQ, AWS RDS (db)
We'll build it to full production standards, which means multi-region, load-balancing, fault-tolerant, high-security, etc. We might only have 20 concurrent users, but we'll build it for 20,000.
So what does it do?
At heart, the apps allow Tesla drivers to plan and log their visits to superchargers. Our first goal is to replicate the functionality that is now tracked manually in spreadsheets by the dedicated volunteers in the thread linked above. This includes:
* keep track of which users have visited which superchargers (and when)
* keep a tallyboard of users with the most visits, viewable by certain criteria
* allow users to see chargers along their route that they have not visited
* allow users to log visits using GPS, photos, and log text (like trail journals)
So why the name ChargeWeave?
I grew up in an ad agency, so brand names are second nature to me. I've come up with a dozen or so such names, using instinct and Roget's Thesaurus. ChargeWeave was the first name I thought of a few months back, though today I gave it the full Roget's treatment, looking and listing variations for an hour or so. Everything was either cliche or fraught with bad connotations.
ChargeWeave tells you what it's about ... connecting chargers together with routes and stories. We are collectively weaving our journeys through common waypoints, stitching together a future free of gas stations and smog.
As any good name, it allows the thing to expand beyond it's original intent, still anchored to charging as the central purpose. But it can grow beyond the current use (gotta catch 'em all) to allow other uses (tell your story for other visitors).
And, I got the domain names
chargeweave.com, chargeweave.net, chargeweave.org
So what's next?
I need to set up the infrastructure, which will include AWS, GitHub, Jira, Confluence, and CI/CD. We can then begin building out the backlog of features and even vote on which we want most.
Please use this topic to discuss your thoughts. This is a community project. I might be the only coder, but the ideas are everyone's.
I woke today feeling rested enough to embark on the promised custom app for the TMC supercharging game. My current job has kept me in the role of manager these last three years, which prevents me from doing what I love most .. coding .. something that has otherwise occupied my days for 30 years (this month). Three years is too long away, so this project is a way to do what I love while helping the super-cool Tesla community.
Since I'm not legally allowed to profit from this undertaking, it will be completely free and open-source. I will donate the hosting and domain fees, along with my time, which isn't a hardship because I have some under-utilized AWS instances that host a few websites I made during my 20 years running my own software company.
So what are building?
* web front-end using JavaScript, ReactJS
* two mobile apps using JavaScript, React Native (Android and iOS)
* backend using Java, Spring Boot, Hibernate, RabbitMQ, AWS RDS (db)
We'll build it to full production standards, which means multi-region, load-balancing, fault-tolerant, high-security, etc. We might only have 20 concurrent users, but we'll build it for 20,000.
So what does it do?
At heart, the apps allow Tesla drivers to plan and log their visits to superchargers. Our first goal is to replicate the functionality that is now tracked manually in spreadsheets by the dedicated volunteers in the thread linked above. This includes:
* keep track of which users have visited which superchargers (and when)
* keep a tallyboard of users with the most visits, viewable by certain criteria
* allow users to see chargers along their route that they have not visited
* allow users to log visits using GPS, photos, and log text (like trail journals)
So why the name ChargeWeave?
I grew up in an ad agency, so brand names are second nature to me. I've come up with a dozen or so such names, using instinct and Roget's Thesaurus. ChargeWeave was the first name I thought of a few months back, though today I gave it the full Roget's treatment, looking and listing variations for an hour or so. Everything was either cliche or fraught with bad connotations.
ChargeWeave tells you what it's about ... connecting chargers together with routes and stories. We are collectively weaving our journeys through common waypoints, stitching together a future free of gas stations and smog.
As any good name, it allows the thing to expand beyond it's original intent, still anchored to charging as the central purpose. But it can grow beyond the current use (gotta catch 'em all) to allow other uses (tell your story for other visitors).
And, I got the domain names
chargeweave.com, chargeweave.net, chargeweave.orgSo what's next?
I need to set up the infrastructure, which will include AWS, GitHub, Jira, Confluence, and CI/CD. We can then begin building out the backlog of features and even vote on which we want most.
Please use this topic to discuss your thoughts. This is a community project. I might be the only coder, but the ideas are everyone's.
