Roadmap
The schedule for Querki is constantly shifting and adjusting, so nobody should take any of this as set in stone. (Or even especially firm gelatin.) But here is the current rough plan for what will be happening when for the next while. Items in italics are internal technology enhancements.
Publication (in progress)
Improved Look-and-Feel
- A front page that looks decently modern and informative
- Improvements to font sizes and layouts (must have a way to override this back to the old style)
Integrated Help
Comment Emails
Moderation
Facebook Integration
Business Rationale: Facebook (and G+ and Twitter, etc, but mostly Facebook) integration is crucial for helping Querki go viral. Growth is likely to remain relatively slow until we have Facebook.
- Create accounts directly from FB -- users should not need to have a Querki login at all. This will make it far easier to sign up casually.
- Share Things/Spaces/Apps via FB -- make it trivially easy to share your stuff, which will help Querki spread.
- Notifications and invitations via FB -- this will make it much easier to bring people from your FB community into your Querki one.
Constraint Solver
Monetization
App Gallery
App Communities (crowdsourcing)
Other Possible Features
- Querki for Small Business -- includes UI for managing user access to Spaces for employees
- Offline functionality for Querki: view and edit a Space to a limited degree when not on the network -- Use case: Shopping List
- Alternate UIs -- in particular, a version of the website designed specifically to work well with older browsers and assistive technology.
- QL -- ability to write complex algorithms that actually change data -- Use case: automated LARP casting
- Conversations -- add Threading -- Use case: Querki Blog
- PDF Export -- Use case: LARP writing
- Security -- ability to define security groups -- Use case: making LARP casting questionnaire (and nothing else) available to players. Think about this in the context of Small Business plan.
- Integration, Integration, Integration -- exploring new APIs for both fetching data from Querki, and importing it in. The long-term vision is that you define what information and structure you want, and it should be as easy as possible to pull it in: one-touch, or even automatically for some cases. (This is a long-run research project.)