OpenRocket should be a web app. There, I said it.
I love the program and it also drives me crazy. There is nothing in the program that couldn't be implemented straightforwardly in JavaScript with a server back end. Here are just a few reasons why it would be better:
How I wish I had time to undertake this.
I love the program and it also drives me crazy. There is nothing in the program that couldn't be implemented straightforwardly in JavaScript with a server back end. Here are just a few reasons why it would be better:
- Instant mobile support - I expect there is zero chance of ever seeing a mobile-based rocket sim program, but code it as a web app using mobile-friendly libraries and there it is, on Android and iOS.
- Access to all your designs, from anywhere - At the field, I could pull out my phone and check on something. Right now I put my designs on DropBox, but I still have to have the program installed on each machine.
- Easier design sharing - Just like every other on-line design software, it would be easy to share designs with others. How cool would it be to have access to a large library of designs right from within the program?
- Java sucks - enough said
- Easier library management - Additions to the part and motor library would instantly be available to all users. The motor library could be linked to Thrustcurve.org on the back end.
- Ways to make money - Free and paid tiers are easy to imagine. I don't think it would ever make anyone rich (or necessarily even support anyone as a full-time job), but it could at least (I think) offset the hosting costs. I'd pay a yearly fee to get access to this, no problem.
- Chance to redo the UI - Oh, it needs redoing so badly. Web app would be a chance for a clean sheet.
- As a web app, it would still be possible to import and export OR and Rocksim files, so no problem there.
How I wish I had time to undertake this.