Todo

This documentation outlines our current to-do list and future plans for Bot Studio. Here, you can find all the upcoming updates and features we aim to implement.

Slack Bots

  • Add more nodes to Slack bots.
  • Update Slack bots and remove them from beta mode.

Web Automation Bots

  • Add more nodes to Web Automation bots.
  • Update Web Automation bots and remove them from beta mode.
  • Implement a virtual browser for Web Automation bots. This simulator will be available at https://chrome.botstudioo.com/virtual-browser and will simulate a browser. This browser can detect developer interactions within the simulated environment and capture all their interactions, subsequently creating bot data for the editor based on the actions performed.

WhatsApp Bots

  • Add more nodes to WhatsApp bots.
  • Update WhatsApp bots and remove them from beta mode.
  • Resolve issues with converting WhatsApp bots from nodes to code.

Editor Plugins

  • Enhance the "Connection" plugin with a magnetic connection system to simplify bot connections.
  • Update the "Node Renderer" plugin to ensure that when a node is copied, its inputs and outputs are copied as well.
  • Allow developers to customize editor plugins. The options system is ready; we need to find a way to demonstrate how developers can edit these options.
  • Interact the "History" plugin with the "Comment" plugin. Comment actions should be stored by the history plugin.

Website

  • Add a forum page to facilitate communication between developers using their existing Bot Studio accounts.
  • Finish the Bot Studio Forge project. This project is available at Bot Studio Forge GitHub and allows developers to create custom flows and publish them.
  • Complete the bot explorer. This feature should allow developers to publish their bots on search engines, making it easier for developers to discover and use them. (Developer consent is required for showing the bot on search engines.)
  • Create a new page called "Analytics". This page is used for showing Bot Studio's overall analytical data to all developers.
  • Create a "Messages" page. This page will include all messages received by other developers and some notifications such as comments on shop items.
  • Add the light mode and dark mode support to the website.
  • Each page should have a unique SEO meta og image instead of one single image for all pages.
  • Add a button called "Logging via Anet" to the authentication page.
  • A new server must be created at beta.botstudioo.com. This page is used for showing the new features in the beta version.

Handlers

  • Standardize handlers to run on port 3060. Currently, due to budget constraints, they run on different ports. Once we have more servers, they will run on port 3060.

Email

  • Implement a valid email inbounding service for the contact us form and eliminate the need to create a Python server for receiving emails. Currently, budget constraints prevent this.
  • The Python's contact.py file which is used to receive emails should be replaced with an email inbounding system and the requirements.txt file should be removed. This system requires some money for email providers.

CDN

  • Serve files using CDNs instead of Bot Studio's servers. Currently, budget constraints prevent this.

AI

  • Include AI nodes in the default nodes list. Use Python libraries related to AI for this purpose.

Authentication and Security Enhancements

  • Implement two-step verification using an authentication app.
  • Automatically lock the account when there are multiple access attempts from different IP addresses.
  • The authentication page should have a captcha verification for some developers who might be attacking the website.
  • Fix the issue with verification emails. Then show if a developer account is verified on the shop page and profiles page.

Resource Management

  • The maximum resource and memory usage by bots processes should be limited.
  • The size of developer's database should be limited.
  • Creating a billing system for each 5000 processes. Each 5000 process should have a small cost.

Customization

  • Creating a new feature called custom CSS. This feature allows developers to customize the website using custom CSS codes. This feature should be added to the shop under the "Settings Files" category.

Future Phases

Phase 3: FlowGram

  • The next phase, Phase 3, will be called FlowGram. In this phase, Bot Studio will expand its focus beyond bots to support a broader range of platforms. We plan to allow developers to add custom platforms. More information related to this phase will be kept private.
  • After the project has been open-sourced, people can create new platforms in Bot Studio. The system must indicate which developer maintains each platform the most.
  • After the project has been open-sourced, 25% of the revenue generated from each platform will be allocated to its maintainer.

Additional Todos

  • Monetization for Popular Bots: Implement a system where popular bots on major platforms that are created using Bot Studio must display a message indicating they were created with Bot Studio. These bots should receive a monetary reward.
  • Team Collaboration: Enable developers to create and join teams, allowing collaborative work on projects.
  • Credit System Integration: Integrate the credit system with the Anet project.
Last Commit: Edit on GitHub
Technologies Changes