User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

is there any best practice for naming prefix or index when i have more then 100 screen in mockup so i manage properly

currently i use just like following

000 Login 001 Registation

010 Dashboard

020 Profile 021 User Setting 022 Change Password

so please provide me some better way

share|improve this question

I like what you've got so far but you may want to edit it slightly to make it more readable. I like to use the 'Work Breakdown Structure' methodology when prefixing because it clearly identifies the parent/child relationship. For example:

0.0 Home
1.0 About Us
2.0 Products
2.1 Menswear
2.1.1 Jeans
2.1.2 Shirts
2.2 Womenswear
2.2.1 Dresses


share|improve this answer
+1 for linked source – jsejcksn Sep 23 '14 at 7:55

As you've noticed, the presented way of enumerating mocks is problematic since you can't exceed a certain number of mocks on the same level of structure, and omitting zeros at the beginning of the ID would cause sorting problems.

Since you already have something around 100 mocks, the simplest solution is to (preferably automatically) add a dash and another 0 before each next digit of your ID; so it would come up with something like that:

02 Profile 02-01 User Settings

You can create as many tree levels as you wish and also, you can create up to 99 mocks on the same level.

For the next time, I'd recommend using folders, so it would look like that:

   [User Settings]
       User Settings.jpg
       [Another tree level]

(square brackets represent folders)

share|improve this answer

We use points to distinguish levels. Each level can be infinite.

So you may have:




...though I'd argue if you have 100 pages in your wireframes, you may be over-documenting things to begin with--which is especially true if you are using LEAN UX as your tags seem to indicate. LEAN UX encourages less documentation rather than more. :)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.