Roadmap

Releases

• v0.2.0: July 1, 2016 (Download) (Change log)
• v0.1.0: March 15, 2016 (Download) (Change log)

v0.3.0 - Shipping September 2016

1. Explore ways to make plugin development possible without editing code directly (visual editor, flow charts)
2. Improve NER using a combination of hashmaps and n-gram Bayesian Classifiers with shared globally available models (or another approach). This should reduce false positives dramatically with a negligible increase in false negatives.
3. Handle multiple requests in the same message by detecting/splitting messages into multiple independent clauses
4. Expand the training interface to extract custom content from sentences.
5. Expand confused responses based on the type of statement. Was it a question? "I'm not sure I understand what you're asking." Was it a statement? "I don't understand that."
6. Add in-place signed updates of the binary.
7. Improve tooling for plugin developers: generation/scaffolding, testing tools, feedback on plugin publishing if there's an error, and automatic alerts when breaking API changes occur included steps needed to fix those issues.
8. Implement tests throughout, including fuzz testing on core.
9. Automatically correct user spelling and substitute slang like "ur," "lol" and emoji with what the slang/emoji represent.
10. Extend response panel support beyond SMS to support conversations over email and web/apps via sockets
11. Create a video to walk through the Abot admin panel.
12. Improve CLI interface, adding installs for specific plugins and cleaning up the API.
13. Move plugin tests to plugin.json, remove plugin test scaffolding.

v1.0.0 - Shipping December 2016

1. Offer simple deployment and hosting options for Abots with pre-configured defaults
2. Provide automatic upgrades and one-click plugin installs through hosting solution with generated tests
3. Support pre-compiled, binary (closed-source) plugins
4. Build an online storefront at itsabot.org that allows charging for closed-source plugins on a monthly basis (similar to Heroku)
5. Build additional interfaces to make it easy to perform common tasks across multiple services using an API similar to Go's SQL drivers. Services could include ordering a car, having a courier make a delivery, etc.