As a small software company, one of our chief advantages over larger competitors is the ability to move quickly and respond to changes in the marketplace and technology. This is the main reason we've resisted mapping out a long-term plan for DotNetInvoice.
With the release of version 2.4 on August 7, 2008 we realized that a sketch of what to expect in the coming year could serve as a guide without the strangling effect it might have on a larger software company.
In other words, treat this document as our best forecast of high-level changes to DotNetInvoice over the coming year, but it is by no means set in stone and will be updated throughout the year as business and technical changes warrant
We plan to release 2-3 new versions per year; more and our customers feel like they are constantly upgrading. Less and the software begins to grow stale.
Here are some key points that we plan to implement in the coming year (and beyond), in approximate order of implementation. Priorities were established based on surveys sent to our current and potential customers:
A C# version (implemented in v2.5)
An API for .NET Developers (implemented in v2.6)
Give DNI Administrators more control over recurring billing (implemented in v2.6)- Time Tracking
- QuickBooks integration
- A Simple Checkout Page where a customer can choose a service and DNI
will automatically create a one-time or recurring invoice for the
customer
We are excited about the future direction of DotNetInvoice, and hope you'll stick around!
---
Rob
DotNetInvoice Support