API Testing App Screenshot Template — Request Lab

The story the slides tell

Paired panels: a request crop and a response crop side by side joined by request-response arrows; method badge on each slide.

1. Slide one — promise: shows collections · request panel + collections · response panel, decorated with request-response arrows and json brackets. Example copy: “Give your API requests a workspace.” / “Organize the endpoints you work with.”
2. Slide two — primary feature: shows request editor · request panel + request editor · response panel, decorated with request-response arrows and json brackets. Example copy: “Build the request clearly.” / “Set the method, URL, and supported request data.”
3. Slide three — secondary feature: shows headers · request panel + headers · response panel, decorated with request-response arrows and json brackets. Example copy: “Keep the details visible.” / “Review headers and authentication settings.”
4. Slide four — personalisation: shows response · request panel + response · response panel, decorated with request-response arrows and json brackets. Example copy: “See what came back.” / “Inspect the response status and content.”
5. Slide five — closing: shows history · request panel + history · response panel, decorated with request-response arrows and json brackets. Example copy: “Return to a useful request.” / “Reuse saved requests and review previous runs.”

How to use Request Lab

1. Open the template in Screenshot Studio. “Use this template” opens a new-project dialog in your browser; nothing is saved until you choose Create.
2. Upload and map your app screenshots. Slots are named Collections, Request editor, Headers, Response, History.
3. Edit the headlines and supporting descriptions. Click any text on the canvas or use the copy table for every language.
4. Apply your colours, fonts and target sizes. Brand kits and per-size adjustments keep the master layout intact.
5. Preview, validate and export. Validation flags empty slots, overflowing text and missing fonts before the PNG export.

Advice for this template

• Use a collections screen for slide one, a request editor screen for slide two, a headers screen for slide three, then response and history screens for slides four and five.
• Use legible editor captures and keep code examples large enough to read in the final artwork.

Questions

Which app screens work best in this template?

In order: collections, request editor, headers, response and history. Each slide has a named screenshot slot so captures map by position.

Can I replace the device frame?

Yes. Each screenshot slot can switch between the generic drawn frame styles (including frameless cards). Realistic manufacturer device artwork is not bundled.

Can I change the gradient colors?

Yes. The background is an ordinary editable gradient; the template also offers a matching solid colour and an alternate light/dark treatment.

Can I use this design for both platforms?

Yes. Projects can target App Store and Google Play sizes together. The master layout is 1320 × 2868; other sizes are resized proportionally, and you can adjust any size individually.

Which parts remain editable?

Every headline and description, screenshot slot, background and SVG decoration is an ordinary named layer you can edit, recolour, move, hide or delete.