Difference between revisions of "25 Steps to Build Your Own Micro ISV"
LeonBambrick (talk | contribs) (first cut of the list) |
LeonBambrick (talk | contribs) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 44: | Line 44: | ||
20. [[Obfuscate Your Assemblies]] | 20. [[Obfuscate Your Assemblies]] | ||
− | 21. Automate Your [[Build+Release | + | 21. Automate Your [[Build+Release Strategy]] |
22. Free up enough time/resources for [[Dealing With Support]] | 22. Free up enough time/resources for [[Dealing With Support]] | ||
Line 53: | Line 53: | ||
25. [[Do It All Again]] | 25. [[Do It All Again]] | ||
+ | |||
+ | |||
+ | I'd also like to reorganise this story into a more flowing piece, which will have different steps, in a more logical order. Below is a work-in-progress of that order. | ||
+ | |||
+ | == Pre-Compilation == | ||
+ | * What's your idea(s)? | ||
+ | * How To Fail Fast | ||
+ | * Plan your [[Promotional Strategy]] | ||
+ | * Strategy: [[Separate "Free" From "Professional"]] product | ||
+ | * [[Register That Domain]] (aka, Choose a Name) | ||
+ | |||
+ | == Code == | ||
+ | * Write your software... | ||
+ | ** Even a one-person company [[needs source control]] | ||
+ | ** [[Shiny, Usable, Helpful]] | ||
+ | ** [[To Obfuscate or not]]? | ||
+ | ** Automate Your [[Build+Release Strategy]] | ||
+ | ** [[Auto Update Strategy]] | ||
+ | ** Testing | ||
+ | ** Beta users | ||
+ | ** [[Write Your Own EULA]] (end user license agreement) | ||
+ | ** Installer, or stand alone | ||
+ | * One page website | ||
+ | ** [[Reliable Hosting]] | ||
+ | ** [[Get The Best Screenshots You Can]] | ||
+ | * Release the free edition | ||
+ | ** [[Create a PAD file]] (portable application description) | ||
+ | ** [[Register at Download Sites]] | ||
+ | |||
+ | == Going Pro == | ||
+ | * Advanced Website | ||
+ | ** [[Website Design]] | ||
+ | ** [[Basic Website Content]] | ||
+ | ** Create forums, [[Encourage Feedback]] | ||
+ | ** Choose a price range | ||
+ | ** [[Establish Payment Account]] | ||
+ | ** [[Allow Payment]] from your website | ||
+ | ** Build/Buy a [[License Management Database]] | ||
+ | ** [[License Activation Webservice/Website]] | ||
+ | |||
+ | == Coda == | ||
+ | * [[Do It All Again]] | ||
+ | * [[Configure Email For Your Domain]] | ||
+ | |||
+ | == Extra Credit == | ||
+ | ** [[Traffic Monitoring]] | ||
+ | ** Experimentation | ||
+ | ** [[Build a Proper Installer]] | ||
+ | * Free up enough time/resources for [[Dealing With Support]] | ||
+ | ** [[Maintain a FAQ]] | ||
+ | |||
+ | |||
+ | |||
+ | == Highlights == | ||
+ | In each section, there would be 'pull-quotes'/highlights around: | ||
+ | * Tough Decisions | ||
+ | * Pitfalls | ||
+ | * Industry Quotes | ||
+ | |||
+ | [[Category:MicroISV]] |
Latest revision as of 16:47, 21 March 2010
Turning an amateur software project into a professional project is a straight forward process -- but it involves a lot of steps.
We're putting together articles on each of the steps we've identified, as a way to help other developers turning their fledgling idea into a working MicroISV.
5. Install Traffic Monitoring on your site
6. Create forums, Encourage Feedback
8. Get The Best Screenshots You Can
9. Configure Email For Your Domain
11. Allow Payment from your website
12. Create a PAD file (portable application description)
13. Register at Download Sites
14. Strategy: Separate "Free" From "Professional" product
15. Write Your Own EULA (end user license agreement) -- infact write two!
17. License Activation Webservice/Website
18. Get a License Management Database
21. Automate Your Build+Release Strategy
22. Free up enough time/resources for Dealing With Support
24. Plan and enact your Promotional Strategy
25. Do It All Again
I'd also like to reorganise this story into a more flowing piece, which will have different steps, in a more logical order. Below is a work-in-progress of that order.
Pre-Compilation
- What's your idea(s)?
- How To Fail Fast
- Plan your Promotional Strategy
- Strategy: Separate "Free" From "Professional" product
- Register That Domain (aka, Choose a Name)
Code
- Write your software...
- Even a one-person company needs source control
- Shiny, Usable, Helpful
- To Obfuscate or not?
- Automate Your Build+Release Strategy
- Auto Update Strategy
- Testing
- Beta users
- Write Your Own EULA (end user license agreement)
- Installer, or stand alone
- One page website
- Release the free edition
- Create a PAD file (portable application description)
- Register at Download Sites
Going Pro
- Advanced Website
- Website Design
- Basic Website Content
- Create forums, Encourage Feedback
- Choose a price range
- Establish Payment Account
- Allow Payment from your website
- Build/Buy a License Management Database
- License Activation Webservice/Website
Coda
Extra Credit
- Traffic Monitoring
- Experimentation
- Build a Proper Installer
- Free up enough time/resources for Dealing With Support
Highlights
In each section, there would be 'pull-quotes'/highlights around:
- Tough Decisions
- Pitfalls
- Industry Quotes