Developround releases public beta version 2.0, with more unified behavior and faster access to services

In the past period of time, we have restructured Developround, and you should be able to experience some changes on the official website, mainly manifested in a significant improvement in opening speed. The refactored Developed has stronger performance, which can help developers obtain more high-quality services in a more efficient and stable way. The biggest adjustment we have made is to unify the planning of the services, avoiding different ways of calling and displaying the services provided. This means that in the future, when similar new services emerge, we can go online faster and provide them to you for use.

Significant performance improvement

We have achieved a significant performance improvement in the overall system by optimizing the architecture. Compared to the public beta 1.0, 2.0 has improved performance by nearly 70%. In terms of website opening speed, we have even achieved over 90% improvement, which gives old users who haven't visited our website for a long time a clear sense of speed when they come back this time.

Unified UI interface

In the past 1.0, the service interface we provided did not have a unified planning, so when you switch between two services of the same class, there may be a feeling of inconsistent interface, which is a bit troublesome for users who are accustomed to using services on the page. A unified UI allows users to spend very little time exploring the UI and focus their main energy on utilizing the services we provide to realize their own creativity.

Enhancement of functionality

We have made adjustments to the LLM user interface by consolidating functions into the chat window while maintaining the original interface, so that we can complete all operations in one interface. This is very helpful for users who need to embed chat windows into other applications. At the same time, we have strengthened our voice chat capabilities. Previously, we chose to directly integrate the voice recognition function into the browser, but due to browser compatibility and network issues, many users were unable to experience it. And this time, you just need to click the "phone" button in the chat window to immediately call LLM.

Enhancement of API interface

One of the characteristics of the Developer Ground is that it supports OpenAPI access throughout the line to help developers call the required services in their own applications. This time, we have re planned the API interface to make the interface calls more unified, which will be beneficial for you to implement calls in the same way after new services are integrated in the future.

Our next step is to unify the output structure of resource class service APIs, so that developers do not need to decide how to read calculation results based on different models, but only need to follow a unified format (or determine which format to use through parameters).

Other improvements

In this upgrade, we have also made new improvements in other aspects, including but not limited to

  • Added support for multiple languages, currently supporting en US and zh CN, and will support all languages in the future
  • Support blog system, allowing you to easily understand our product situation
  • Data isolation to avoid mutual contamination of data from different things and users
  • Better presentation of service documents
  • ……

Destruction

This upgrade has also brought some damage, which we deeply regret for users. In the development process of the product, such damage is inevitable. As we are currently in the public beta stage, we will make moderate adjustments to the product. The destructive impacts brought by this upgrade mainly include:

  • The old data is incompatible. You may have noticed that your previous data did not appear on the website. This is because the old data is incompatible. We have made a backup of the data. If your past data is important to you, please contact us and we will export it through technical means and send it to your account email.
  • You may have noticed changes in the API interface, as some previous API calls encountered 404 errors. This is because we have made a unified interface plan, please make adjustments in a timely manner according to the documentation of each service.