platform oriented towards experience

shafi765@gmail.

As an example. The simplest version can be filled in the form. Once filled out, the release is completed. There is no need to build the API first. Write these complex functions in state machines and API documents. After this version goes online, it can be provided to industry, research and customers. Version : Build docking cycle statistical capabilities and experience evaluation capabilities, and build a and efficiency. Building complete document writing and presentation capabilities, in past operational experience, the


biggest cost comes from version changes of offline documents. The version Malaysia Phone Number Data of the document that everyone gets is inconsistent, resulting in various reworks. And specialized API documentation capabilities can greatly improve the efficiency of customers learning to use APIs. Version : Focusing on customer access efficiency, build complete API navigation, API debugging tools, logging tools and other capabilities. Version : Focusing on customer access experience, further optimize the experience of using various tools. This chapter only explains the





version planning for product function construction. In fact, each version must be supported by operational actions to make the platform finally available and easy to use. Please see Chapter for the operation of the platform. Product Operations Typical platform products = platform trading tools + supporting platform process specifications + platform operation governance. The first chapter has already explained the construction of platform trading tools. This chapter focuses on the construction of platform process specifications and daily operation governance. Platform cold start After the product MVP version is built, it can theoretically be put into production. However, because the functions are very crude and incomplete, it cannot actually be delivered to