![]() ![]() Prototyping and researchĪlthough there would still be key differences between platforms, we wanted the tools to be easy to access and use and for people launching Acrobat on any platform, to at once understand what they could do. The workflows, which we called “megaverbs,” changed our design approach from one focused on multiple individual tasks (like “organizing pages,” “editing text,” and “adding images”) to one focused on an entire workflow (like “edit” or “sign”). Together, we identified problems we'd encountered on our respective platforms and worked toward platform-agnostic design solutions.Ī turning point in the design process was our “megaverbs” concept, the consolidation of multiple workflows under a single action. The solution was to unify as a single team with a common goal. ![]() Because Acrobat lacked a common framework, each platform team was struggling with the same basic issues of how to make workflows smoother and tools more discoverable. It meant multiple groups worked simultaneously, but separately, on the product that consumers think of as a unified Acrobat. Historically each Acrobat platform (desktop, web, tablet, and phone) had its own team composed of design, engineering, and product staff addressing its own set of problems and creating its own set of solutions. Above all else, Adobe Design emphasizes exceptional experiences: To create a cohesive experience and a flexible framework in a product like Acrobat, we'd have to consider every platform, at every size, for every tool, right from the start. We knew the scope of the redesign was monumental. Acrobat is everywhere (desktop, web, tablet, and phone) but an inconsistent experience across platforms meant that people had to constantly reorient themselves whenever they opened the app somewhere new. We needed to present the full value of the features waiting on the other side of the paywall before asking people to pay for them. This purchase process was not as effective or smooth as it could be. Many people using the free version of Acrobat convert through in-app purchases (for example, someone viewing a document might pay to edit it). Over the years we'd developed new editing features for Acrobat, but because we hadn’t surfaced them in the viewer, anyone bypassing Acrobat's home screen for a one-time need (say, to compress a PDF) were missing out on some of the app’s most powerful capabilities. Many people don't know that Acrobat is a PDF reader and an editor. Exploring how to harness Adobe’s artificial intelligence capabilities helped us consider how to unlock more value and make Acrobat even smarter. Asking ourselves “What makes Acrobat unique?” helped us think beyond our application’s existing features and functions to improving people’s relationships with PDFs. Since PDF is an open-standard and widely adopted format, multiple applications from multiple vendors are used to view it. Most importantly, the friction between tasks had to be removed so people could effortlessly move between them (for example, someone viewing comments in a PDF should also be able to easily edit the text of it without interrupting their workflow). We needed to showcase the features people didn't know existed and help them uncover the features they couldn't find. There were five design challenges ahead of us: Identifying our design challengesįor years we’d been focused on adding and updating features and functionality, but we hadn't revisited or redesigned Acrobat's foundation in quite some time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |