How to operate and monitor after the release (when there is a problem, what methods can be used to help troubleshoot the problem)
Concern 1: How much UI is needed
How many UI components to draw and how many UI pages to add depends first on the Requirements Document (PRD) and the Visual Interaction Design Draft. For development, please pay attention to requirements review and visual interaction review. For good quality requirements documents or visual design drafts, the UI components/page ranges given in the documents are generally the UI ranges to be implemented by the development; For the demand for poor quality or even the demand for a sentence, the UI scope needs to be “combed and determined” by research and development. Regardless of the quality of the requirements document or visual design draft, R&D personnel need to focus on “abnormal logic” in the process of requirements review, visual interaction review, technical design, and coding implementation. What is exception logic? For example, for a query class requirement, scenarios such as “the query result is empty” and “there is no network when querying” belong to the “exception logic”. Many times, the place where novices are prone to problems or omissions is the handling and display of exception logic.
UI range: the scope of the functional page, the change logic of the page state and state, the abnormal logic of the interface, and so on
Disassembly of page elements: list elements, card elements, animation elements, UI effects, etc. (this is also the basis for precipitating common components)
UI display objects: the scope of copywriting, the source of multilingual translation, the scope of RTL adaptation, pictures, short videos, etc.
Focus 2: Where does the data come from?
Network data: When disassembling requirements, focus on the interface document, interface name, data fields returned by the interface (including field type, scope, field name, etc.), the corresponding team or specific development of the interface, the upstream and downstream links of the interface (example: the search for the interface will involve advertisements, algorithms, etc.), interface testing and joint debugging methods. For novices, when dismantling is required, it is also necessary to confirm: the type of data gateway (MTOP gateway, data after Node orchestration, data gateway corresponding to Web sites, etc.), and clarify the domain name used for network data scheduling (for example, the domain name of some APP transaction functions is separate from the domain name of non-transaction function, and the scheduling method will be different).
Locally stored data: During the requirements dismantling phase, it is necessary to clarify whether to store the data locally or to be responsible for it or to use the ability of others. If you are responsible for yourself, you need to further determine whether the data is written to the local database or to the local file; If someone else is responsible, what is the way and interface of the data is read and written.
Memory data: The demand disassembly focuses on how memory data is read and written, and how the data is released after use.
Rich media content streaming: multimedia streams such as pictures, short videos, live broadcasts, etc. Pay attention to the form of these content storage when disassembling the requirements (take the image as an example: whether the image is the URL of the CDN, or the file address or ID of OSS, or even the encoding result after base64 processing); At the same time, it is also necessary to determine whether these demonstration capabilities are existing or need to be newly introduced.
Hierarchical diagram of data logic (according to actual needs)
The comparison relationship between the function and the data interface, the interface document, the platform of the interface, the mock method of the interface, etc
Functional data flow and logical flowchart
Concern 3: How does data relate to the UI?
One-way data binding: Data changes automatically drive UI refresh, and code implementations are embodied as various Observers or Observables.
Two-way data binding: the view is refreshed at the same time as the data changes, and the view change can also change the data at the same time.
It does not matter about data binding, data association to UI is procedural programming, embodied in: loading data, loading successful manual code on the screen, etc.
Functional data flow and logical flowchart
Code design, data relationship flow design, and more
Data state changes, UI refresh timing, etc
The binding capability used for the association, the notification mechanism after the data changes, etc
Focus 4: User behavior response
Summarize user action points in a requirements document or design document, including: tap, swipe up and down, swipe left or right, long press, unlock screen, virtual keyboard response, zoom gestures, and more.
Common handling of action points: page jumps, tips/toast/pop-up window displays, animation processing, interface zooming, interface closure, etc
The interface or specification that needs to be agreed: the schema/reference of the page jump, the way in which the two- and three-party capabilities are evoked, etc
Focus 5: User behavior capture
Data leakage collection: It may be that the product/data students do not have clear data requirements, or it may be the development of omission data buried point code.
Data point errors: including event type errors, data point name errors, collection timing errors, more collection, less collection, data parameter errors (data parameter errors include field names are not correct, the actual value passed by the field is not correct), and so on.
Whether the requirements require the collection of buried point data
Whether the name of the point meets the requirements of the consumer, such as product/data
Whether there are requirements for parameter ranges and parameter values
After the requirements are completed, who verifies the data collection?
Focus 6: How to operate and monitor after the release
Not seen or scattered~
GTS Cloud Rider Essay Contest is online!
Before October 10, he submitted the GTS Yunqiao Wind Rider Essay Contest and won the 38 yuan Tmall supermarket card! (Limited number) The content of the article is not limited to Yunqiao, as long as the [concept of assembled application] is used, you can submit an article! There is also a chance to get 888 yuan cat super card and Tmall Genie Sound~
What is the concept of cloud and assembly application? Yunqiao is the landing of the concept of “assembled application”, which helps everyone improve the delivery speed, improve the delivery quality, and reduce labor costs.
Click to read the original article for details.