Open Axure, click on the summary in the upper left corner and see if there are a bunch of "(shape)" "(combination)" "(rectangle)" "(picture)" "Lorem ipsum"? If it's just a few pages of simple low-fidelity prototypes, it doesn't hurt to use the default naming. But once you start making high-fidelity prototypes, the importance of standardized naming is self-evident, because the components we need when writing interactions often have There are many identical or similar ones. If they are not named correctly and clearly, it is easy to confuse and lead to logic errors (and in the existing Axure debug mode, such logic errors caused by wrong component selection are left to others to review and troubleshoot. is very troublesome). This is why major Internet companies have detailed specifications to follow when making prototypes, not only to make the product documents produced by different product managers as readable as possible for development, but also to It also allows communication costs to be reduced and work efficiency to be improved when the same product document is taken over by multiple product managers.
Here are some of my own views on naming:
1.? The naming of the page is best described in terms of the actual function Page. The same page It is recommended to use the "-" sign to separate the different functions below. For example, we can name the login page LoginPage, and we can name the SMS verification code page included in the login page LoginPage-SMS, so that it is clear and clear. Why not use the simpler writing method Login-SMS? Although the page name in Axure may only be used when opening the page and calling functions, in order to avoid overlapping with component names, it is recommended that all pages have the word Page for identification.
2. It is not recommended to use Chinese for all components and page names. If you are really struggling with English, you can try pinyin annotation. Although Axure seems to me to have very good support for Chinese variable names, it is still not recommended to use Chinese in any place involving logic to avoid unknown errors.
3. The component name can be written in camel case (Pascal nomenclature) or Hungarian nomenclature. Personally, I am used to using Pascal nomenclature (that is, the first letter of each word is capitalized). Although the Hungarian nomenclature is more intuitive and easy to classify, Pascal nomenclature is simple and easy to type, and it is more suitable for me.
4. When naming components, it is recommended to name them in the form of "function" and "property", such as return button "BackButton", delete button "DeleteButton", and install friend The dynamic panel of the list "FriendListDynamic", the repeater of the avatar "AvatarReapter", and the friend list master "FriendListUnit". In this way, when we are looking for corresponding components to write logic, we can quickly and accurately find the components we need through the search box search function or name, avoiding the need to search over and over again in the list.
5.? It is recommended to use an easy-to-understand "function description" when naming global variables. For example, when this variable is used to record the page name that jumps to the album, we can be very intuitive. Name it "WhoCalledAlbumPage", so that when calling, it will look much easier to identify than variables such as Var1, V1111, GlobalVar1, and GlobalVar1111.
6.? If there are many pages and components, be sure to use the group function to group them. The shortcut key is very simple. Select the corresponding page and component and press cmd G.
The grouping of pages is generally determined by functional division. For example, the pages before login are grouped into "BeforeLogin", the chat pages are grouped into "Chat", etc. The grouping of components is relatively flexible. Due to the use of component libraries, groups may often be formed. This is harmless. I often determine the grouping by buttons, panels, functions, and logic. The specific situation requires detailed analysis, so I will not go into details here. .
Through reasonable naming and grouping, we can save a lot of time searching for components when making prototypes, and also greatly improve the utilization rate of this component for others, please Everyone should pay more attention to naming groups in daily work and study, and develop good naming habits.
————————————————Article Table of Contents——————————————————
Chapter 1
Preparation before starting
1.?Written before, why should I start this pitfall of Axure? ?
2. To launch a product without a complete concept is to act rogue.
3. Think before doing it: high fidelity or low fidelity?
4. You still need to know a little bit about the relevant specifications of the mobile terminal.
Chapter?2
Let’s get started, confusing questions for beginners:
5. Standing on the shoulders of giants: install a component library first
6. Too many skills are not overwhelming, too many components are really important Press
7. Text box and text field: How to get the input text?
8. How to use url and variables to link pages and achieve jumps
9. About naming conventions: pages, Component, group.
10. When should you use dynamic panels?
11. When should repeaters be used?
12. How should I start learning interactions, variables, and functions?
13. The last line of defense for interaction - enabling situations
Chapter3
Practical tutorial, to be continued...