It has not been updated for a long time. Today, I will continue to think about Liang Ning's series of courses. In this class, Liang Ning is talking about the content of "scenes". At the beginning of the article, let's learn the terminology of this class first: "Field" is the concept of time and space, and a field is time plus space. "Scenery" is the situation and interaction. When the user stays in this space, there must be situations and interactions to trigger the user's emotions, which is the scene. Only scenes that can trigger user emotions are the real traffic portals.
If you look at the C-end products, you mobile number list will think of many familiar scenes in life. For example, if you are hungry in the middle of the night, you may open Meituan to order takeout, and when you go to work in the subway, you may open Himalaya to listen to audiobooks... Don't B-end products need to consider scenarios? Although we said before that B-end products emphasize efficiency, we have not yet analyzed the scene well. It happened that when I was working on data visualization products recently, I had some experience and experience.
Today, we will talk about the scene of data visualization products (for the basic content of data visualization, please refer to my previous article "How to realize data visualization?" ). 1. Design based on data scenarios Timeliness is one of the important indicators of data products. There are two main types of data aging in visualization products. One type is offline data in the T+1 cycle, that is, only the data up to yesterday can be queried at the latest today. Generally, the data up to yesterday is run through the scheduling mechanism every morning or before working hours, and then the data that has run well is extracted. offline data for visual display.