Mapping the Toolkit: Claro, Flow, and Capture

The Unified Ecosystem Shift

Moving from Articulate 360 to Claro is a move from a fragmented suite of desktop and web apps to a unified, cloud-native ecosystem. No more switching between Storyline for slides and Rise for web; everything happens in one browser-based interface.

Welcome to the future of authoring. In the Articulate world, you often find yourself jumping between Storyline on your desktop and Rise in your browser. With Claro, that fragmentation disappears. You have one unified, cloud-native workspace where every tool is just a click away, regardless of whether you are on a PC or a Mac.

Mapping the Toolkit

How do your daily tools translate? Click each Articulate tool to reveal its Claro equivalent and the core workflow differences.

Let's map your current toolkit to the new platform. Click on any Articulate tool to see how it translates to Claro. Peek and Replay are replaced by Capture. Instead of just passive video, Capture creates interactive Show Me, Try Me, and Test Me simulations from a single recording. Rise maps to Flow. While Rise uses rigid blocks, Flow is truly responsive, giving you full control over layouts and breakpoints. Review 360 becomes Review. In Claro, comments appear directly in your authoring workspace, so you can edit and resolve feedback in context. Storyline translates to Claro. The biggest change? Claro is cloud-native and macOS compatible, allowing for real-time co-authoring without checking files in or out.

Choosing Your Authoring Mode

Claro offers three distinct authoring modes. Choose based on your design goals and target device.

Choosing the right tool depends on your design goals. Claro is your go-to for pixel-perfect, slide-based designs and complex branching. Flow is the gold standard for mobile-first learning, using a flexible grid that adapts to any screen. And Capture is a dedicated engine for software training, generating multiple outputs from a single session.

Scenario: Pick the Right Tool

Read the project requirements and drag the correct tool to the scenario card.

Let's put your knowledge to the test. I'll present three scenarios. Drag the tool icon—Claro, Flow, or Capture—that best fits the client's needs. Great choice! That tool is perfectly suited for those specific requirements. Not quite. Consider the primary device or the level of custom layout control needed for this specific project.

The Workflow: From Device to Library

Follow this 3-step workflow to start any project efficiently in Claro.

When starting a new project, follow these three steps. First, identify the primary device. If it must be 100% responsive, start in Flow. Second, check for software tasks. Use Capture to record any 'how-to' segments first. Finally, upload everything to the Central Library. Unlike Articulate, these assets can be shared across both Claro and Flow projects simultaneously.

Design Strategy Diagnosis

Review the client brief and provide a tool recommendation. Explain your choice based on the device and interactivity needs.

Now it's your turn to act as the lead designer. Read this client brief and type your recommendation in the box. Be sure to explain why you chose a specific tool over the others.