Design specs or prototype?
Why is it called Prototypes & Specs in my CC account when a spec file is a prototype file. What's the point in this double wording? Something I missed here? A Design spec file is also a prototype.
Why is it called Prototypes & Specs in my CC account when a spec file is a prototype file. What's the point in this double wording? Something I missed here? A Design spec file is also a prototype.
Haven't met a single developer in my environment (21 developers) that refers to design specs files as anything else than a prototype of the UI design. Just sayin. What designers in general is using as termology is something else. Like it would be most authentic to call a static lofi UI presentation a mockup a developer wouldn't relate to that. Design specs and prototype is two different doc types so it should not be merged in CC into Prototypes & Specs. Just like Library items & Files wouldn't make sens either.
If you're wondering why Prototypes & Specs and grouped in https://assets.adobe.com/links I think it's because those are both "cloud" features generated from XD files. They are not XD files, but things created from XD files stored in your CC account. I could see separating Prototypes & Specs out to make the appropriate asset easier to find (or at least the ability to filter by Prototypes or Specs.
As for the naming (with all due respect) it seems your environment is not the industry norm. Companies often have their own language for things, and maybe that varies from place to place, but these are the terms I've seen every major design app use. For example... Design specs tell you something about a design (font, color, size, spacing, etc), which a prototype does not. A prototype is a clickable version of the UI design.
InVision creates prototypes and says What are prototypes?
A prototype is a barebones, relatively simple working model of an app or webpage. They are typically the next step in the product design process after wireframing. Prototypes typically have color, animations, and (hopefully) the actual content that will be on or in your product. Unlike wireframes, prototypes are often medium to high fidelity. They allow the user to test a digital product’s interface and interactions, and this level of functionality can be useful during the usability testing of an application. Because they often resemble a more finished product, the time and effort invested in creating a prototype can translate to savings during the development phase.
—Source: https://www.invisionapp.com/blog/wireframe-prototype-difference/
Sketch says this about Prototyping:
When you’re designing for screens, whether it’s mobile or web interfaces, it might be useful to see your work in action. With Sketch’s Prototyping features it’s easy to create interactive workflows and preview your designs as your users will see them.
—Source: https://sketchapp.com/docs/prototyping/
Sketch Measure calls it a spec export and that is like Adobe's Design Specs.
So Adobe has a lot of company in using these terms and is in line with the people I've worked with (both designers and developers).
As for organization on the CC website, what is the issue that's causing confusion? Do they only want to see one type of thing (Prototypes or Specs), or it mainly the terminology?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.