Deployment model
The plan was to sell TTSync as a hosted service, but no one is going to trust their private data to an unknown company, and it will stay unknown until I get a bunch of customers. Problemo. So.. plan B - package it up and get people to install it themselves. There are several issues here straight off...
- its in Java. Its dead easy for someone to to reverse engineer and run off with the fruits of my labours.
- How do I license it?
- Its a bit complicated to configure.
I've looked as obfusticating the code, but I'm not sure it helps - anyone determined to reverse engineer it could still do so. For a small fortune you can buy an ahead-of-time java compiler to make it into a native .exe application.
Licensing - plan A - rely on honesty. Plan B - ???. I like plan A.
Configuration - I've started writing a guide. Its already getting really ugly. configuring Google APIs is hideous, and then configuration for the software itself is a mass of regular expressions. Maybe I could sell my services setting it up + give away the software for free? This is looking increasingly like a good plan.
I've also made enquiries about various partner programs - they cost. No surprises there.
Edited by jim_potter

0 Comments
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now