DickRasmussen wrote:
Carlton Whitehead wrote:
Michael Czeiszperger wrote:
Good luck! Its not "rocket science", but not a trivial project either. What are you writing it in?
I'm writing the backend in Java 8. I had started prototyping the core service with a Spark REST interface a few weeks ago, but the project quickly outgrew it. I just finished moving what I have so far over to Dropwizard. Its learning curve is much steeper (Spark's was nearly zero), but I think it'll be a much better fit for the project going forward.
And ... cue the Java haters coming out of the woodwork.
What do you think you can do better than axti.me which seems to have good reviews and apparently is selling?
I think the autocross timing software market is not large enough to sustain more than one commercial product. AXware has (had?) a monopoly, let their software stagnate, and treats their customers like dirt. axti.me has a lot of awesome things going for it, and I could see them running AXware right out of business. Once enough clubs make the switch, network effects will put additional pressure on the remaining AXware users to switch too. That would leave axti.me with the monopoly. I don't know how the owners of axti.me will run their company if/when they get into that position, and I don't really want to wait to see how that shakes out. What if the owners run it well, but decide to sell off the business and it ends up with someone less benevolent?
I'm planning to make my project free and open source. Anyone with the skill and the will would be able to make contributions to it. If it gets even a little bit of traction, it'll help keep the commercial offering honest and innovating.
I definitely want to match some of the features that axti.me has. Real-time updates, worker roles, mobile/desktop browser-based access. I don't think they have split/sector times, and I'd love to build that in.