in2apps Product Roadmap

The last post spoke to our in2apps Development Principles, which we use to guide our overall decision making process on what features and functionality we introduce and what areas of our platform, thin-client applications, and API we concentrate on.  Now it’s time to cover what you’ll be seeing in the next 90 days from in2apps.

We've released in2community in public beta trial mode – if you didn’t know that, it’s time for you to sign up!  However, in2apps is much more than our social networking application, it is a SaaS platform that we are using to develop our proof of concept applications (and just because we deem them proof of concept does not make them any less usable in the real world) and we chose to start with in2community because it is the first pillar of our community, content, and commerce philosophy.  So our product roadmap covers everything in our development pipeline, working against a 90-day project plan. 

Since we are a small dynamic company, our 90-day plan needs to be flexible so we can add, remove, and shuffle projects based on level of difficulty, customer requests, priorities, resources, ROI, and of course how they align to our development principles.  We also have a parking lot to store features and functionality that we will implement when the opportunity arises and it is technically and resourcefully feasible for us to do so.  Those are usually the fun features that sneak in. 

So with this development approach in mind, it is somewhat difficult to provide a product roadmap that is carved in stone, because if we did that we wouldn’t be all that dynamic anymore.  The best we can do is to provide a 90-day roadmap at 90-foot level.

At the 30-day mark, which we consider the month of April, we will be releasing a number of features both major and minor for in2community:

• A CSS wizard to customize your community
• Google AdSense within our thin-client (which you might have noticed there already)
• The ad inventory buy-out feature so for a monthly fee you can place your own ads or none at all
• External end-user invites
• Extended digital media

And we are excited to start on our next thin-client application, in2classified.

At 60-days, which we consider the month of May, we will continue to evolve the in2community thin-client with more features and functionality and of course, really dig into in2classified.  Look for the following for in2community:

• A requesting system to support friendship and private groups
• Whitelabelling
• Fully enabling private and public communities
• Preliminary features for end-user monetization

At 90-days, the month of June, one last feature for in2community to support templates, full-on development and possible private beta launch of in2classified, and laying some solid groundwork for our open three-tier API.

You can keep up-to-date through our blog and through the Product Release Notes in the Forum, as these are updated with the release of each new version of the thin-client.