Mobile App Deck

About this template

The first outside walkthrough of an app

Ten slides for introducing an app externally for the first time: a pre-diligence meeting, a partner briefing, an internal feature review where you have about twenty minutes to cover what the app is and how it is doing. It is not a live demo deck. To show large screenshots you must clear the list area of a body slide and place the image there, or add slides of your own.

How the ten slides break down

Cover, agenda, two divider-plus-body pairs, comparison, key figures, trend, closing. The agenda on slide 2 carries first-impression design, the four core screens, previous versus current version, key metrics and trend analysis, marked from 01 / 05 to 05 / 05, and each name matches the slide title that follows it word for word. Only two items get a divider plus a body slide – first-impression design on slides 3 and 4, the core screens on slides 5 and 6 – while the rest are single slides: the comparison on slide 7, the metric cards on slide 8, the bars on slide 9. To add a subject the file does not carry, such as user flow or device support, duplicate a divider-plus-body pair to reach twelve slides and update both the new agenda line and the progress markers to 06.

Filling the two body slides

1. Fix the cover subtitle first: whose task the app replaces, in one sentence.
2. The first-impression slide is about the opening seconds. The defaults – core feature visible within three seconds of launch, browsing without login, one-tap launch from a home widget – are all first-run experience. Keep the form: user outcomes, not feature names.
3. The core-screens slide holds the order in which you show screens; “home, search, detail, profile” is the default. There is no image placeholder on this slide, so clear the list area or add a slide.
4. The four metric cards already carry app numbers: 120,000 cumulative installs, 4.6 store rating, 48 MB app size, 1.8 s first-screen load. Size and load time change per release, so add a line under the cards naming the version measured.
5. The trend bars climb from 41 in January to 106 in April. They are built for a metric where higher is better – monthly installs or active users. A metric like crash count, where lower is better, reads backwards here.

Values that fit

• Card swaps: keep 120,000 installs and the 4.6 rating, and replace app size and load time with D7 retention 41% and crash-free sessions 99.6% to make it a user story.
• Trend bars: monthly active users of 41k, 58k, 79k, 106k from January to April keeps the built-in growth shape and only adds a unit. The bars carry a “unit: index” footnote, so change that too.
• First-impression line, for example: after adding login-free browsing, first-week drop-off fell from 24% to 11%. Both sides in one sentence.

Common mistakes in an app deck

• Editing an agenda line and a divider title separately. The two sets of names match exactly today, so when you duplicate a pair or rename a section, fix the SECTION number and the 01 / 05 markers in the same pass.
• Keeping the stock values on slide 7 (first launch 4.2 s to 1.4 s, store rating 3.6 to 4.5). Ratings are visible in the store, so a wrong one is caught on the spot.
• Not updating a value anyone can verify in the store, such as 48 MB. If it is wrong, the other three cards are doubted too.
• Cramming six screenshots onto one slide until the in-app text is unreadable; one or two per slide.