[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post:app-store-screenshot-captions-tips":3},{"post":4,"related":121},{"id":5,"title":6,"slug":7,"excerpt":8,"status":9,"publishedAt":10,"updatedAt":11,"coverImageUrl":12,"coverImageAlt":13,"readingMinutes":14,"wordCount":15,"source":16,"focusKeywords":17,"category":22,"tags":27,"author":45,"html":47,"toc":48,"coverImageCredit":26,"coverImageCreditUrl":26,"seoTitle":102,"seoDescription":103,"faq":104,"noindex":120},"cmvxaybvp000707icbpld2eqw","App Store Screenshot Captions: 9 Tips That Get Read","app-store-screenshot-captions-tips","Good App Store screenshot captions are short, benefit-led headlines of roughly 3–7 words. They are set large and in high contrast, written for one idea per screenshot and localized for every market. On Google Play, keep taglines under 20% of the image and leave out calls to action.","published","2026-11-01T04:00:44.189Z","2026-11-01T04:00:44.198Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fapp-store-screenshot-captions-tips-cover-mvxay9ug-uUcndSOehUzlRCURv5dYjkxSXjoqTK.jpg","iPhone 17 Pro Max mockup showing App Store screenshot captions with a bold headline above the app UI",7,1548,"auto",[18,19,20,21],"app store screenshot captions","screenshot caption tips","app screenshot text","google play screenshot taglines",{"id":23,"name":24,"slug":25,"description":26},"cmvxaybv0000607icji6ezyp6","App Store Optimization","app-store-optimization",null,[28,32,35,38,41],{"id":29,"name":30,"slug":31},"cmvxaybuh000207icl8qm96nh","app store screenshots","app-store-screenshots",{"id":33,"name":34,"slug":34},"cmvxaybuz000507ichpv2j0iu","aso",{"id":36,"name":37,"slug":37},"cmvxaybuh000307ict03whrjp","captions",{"id":39,"name":40,"slug":40},"cmvxaybuk000407icua2hqb74","copywriting",{"id":42,"name":43,"slug":44},"cmvxaybtd000107icufwenxb9","google play","google-play",{"name":46,"avatarUrl":26},"Nexa Admin","\u003Cp>The best App Store screenshot captions are short, benefit-led headlines of roughly 3–7 words, one idea per screenshot. Set them large enough to read at thumbnail size, in strong contrast against the background. Write the captions before you design anything. Then check them against both Apple's and Google's store rules and localize them for every market you ship to.\u003C\u002Fp>\u003Cp>Below are nine practical screenshot caption tips, based on the official App Store Connect and Google Play Console guidance, plus a checklist you can run before every upload.\u003C\u002Fp>\u003Cimg loading=\"lazy\" decoding=\"async\" src=\"https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fapp-store-screenshot-captions-tips-mockup-mvxayb3a-479q49SgSp2QcapLy8BgDwIiuV8dcw.jpg\" alt=\"Trio of phone mockups with short benefit-led captions above consecutive app screenshots\" width=\"1200\" height=\"630\" \u002F>\u003Ch2 id=\"what-are-app-store-screenshot-captions\">What are App Store screenshot captions?\u003C\u002Fh2>\u003Cp>An App Store screenshot caption is the short marketing text placed above or below the app UI in a store screenshot. It usually has a bold headline and sometimes a smaller subline, and it tells shoppers what the screen shows and why they should care. It is not part of your app's interface. It is a layer of copy you add on top when you design the screenshot.\u003C\u002Fp>\u003Cp>Captions matter because people scan store listings quickly. Apple notes that \u003Ca href=\"https:\u002F\u002Fdeveloper.apple.com\u002Fapp-store\u002Fproduct-page\u002F\" target=\"_blank\" rel=\"noopener\">the first one to three screenshots appear in search results\u003C\u002Fa> when no app preview is available, depending on orientation. Those first images and their headlines often have to make the case for the whole app.\u003C\u002Fp>\u003Ch2 id=\"is-text-allowed-on-app-store-and-google-play-screenshots\">Is text allowed on App Store and Google Play screenshots?\u003C\u002Fh2>\u003Cp>Yes. Both stores allow text overlays, with conditions. Apple's App Review Guideline 2.3.3 says screenshots \"should show the app in use, and not merely the title art, login page, or splash screen.\" It also says they \"may also include text and image overlays.\" Guideline 2.3.7 adds that metadata, including screenshots, should not include prices or other descriptions that don't belong there (\u003Ca href=\"https:\u002F\u002Fdeveloper.apple.com\u002Fapp-store\u002Freview\u002Fguidelines\u002F\" target=\"_blank\" rel=\"noopener\">App Store Review Guidelines\u003C\u002Fa>).\u003C\u002Fp>\u003Cp>Google Play is stricter about app screenshot text. The \u003Ca href=\"https:\u002F\u002Fsupport.google.com\u002Fgoogleplay\u002Fandroid-developer\u002Fanswer\u002F9866151?hl=en\" target=\"_blank\" rel=\"noopener\">Play Console preview assets guidance\u003C\u002Fa> says:\u003C\u002Fp>\u003Cul>\u003Cli>Add taglines only if they are needed to convey key characteristics of the app, and keep them to no more than \u003Cstrong>20% of the image\u003C\u002Fstrong>.\u003C\u002Fli>\u003Cli>Avoid small text and backgrounds that compete with the text.\u003C\u002Fli>\u003Cli>Avoid calls to action such as \"Download now,\" \"Install now,\" \"Play now\" or \"Try now.\"\u003C\u002Fli>\u003Cli>Don't suggest Play performance or rankings with words like \"Best,\" \"#1,\" \"Top,\" \"New,\" \"Discount,\" \"Sale\" or \"Million Downloads.\"\u003C\u002Fli>\u003Cli>Avoid time-sensitive taglines that will go out of date quickly.\u003C\u002Fli>\u003Cli>Localize any taglines or text overlays.\u003C\u002Fli>\u003C\u002Ful>\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>App Store (Apple)\u003C\u002Fth>\u003Cth>Google Play\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Text overlays allowed\u003C\u002Ftd>\u003Ctd>Yes (Guideline 2.3.3)\u003C\u002Ftd>\u003Ctd>Yes, only if necessary, at most 20% of the image\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Screenshots per device type\u003C\u002Ftd>\u003Ctd>1–10\u003C\u002Ftd>\u003Ctd>Up to 8\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Calls to action (\"Download now\")\u003C\u002Ftd>\u003Ctd>Not addressed by name; keep copy specific to the screenshot\u003C\u002Ftd>\u003Ctd>Avoid\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Ranking or price claims\u003C\u002Ftd>\u003Ctd>No prices (Guideline 2.3.7)\u003C\u002Ftd>\u003Ctd>Avoid \"Best,\" \"#1,\" \"Sale,\" etc.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Transparency\u003C\u002Ftd>\u003Ctd>No alpha channel\u003C\u002Ftd>\u003Ctd>24-bit PNG (no alpha) or JPEG\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\u003Ch2 id=\"how-long-should-a-screenshot-caption-be\">How long should a screenshot caption be?\u003C\u002Fh2>\u003Cp>Keep the headline short enough to read in about a second. In practice, that means roughly 3–7 words, with a subline of no more than one short line. This is a working rule of thumb, not a store requirement. The real limit is legibility, since shoppers see screenshots at thumbnail size in search results and can't zoom in.\u003C\u002Fp>\u003Cp>A quick test: shrink the finished screenshot to the size of a search result thumbnail on your phone. If you can't read the headline at a glance, cut words or increase the type size. On Google Play, also confirm that the caption area stays under 20% of the image.\u003C\u002Fp>\u003Ch2 id=\"9-tips-for-writing-captions-that-get-read\">9 tips for writing captions that get read\u003C\u002Fh2>\u003Ch3 id=\"1-write-the-captions-before-you-design\">1. Write the captions before you design\u003C\u002Fh3>\u003Cp>Draft all your headlines in a plain list first, one per screenshot. Read them in order and check that they tell a story: the core promise first, then the main features, then the extras. If the list doesn't make sense as text, design won't fix it.\u003C\u002Fp>\u003Ch3 id=\"2-lead-with-the-benefit-then-name-the-feature\">2. Lead with the benefit, then name the feature\u003C\u002Fh3>\u003Cp>\"Plan meals in 5 minutes\" beats \"Meal planner module.\" Apple's own advice is to \"focus each subsequent screenshot on a main benefit or feature\" (\u003Ca href=\"https:\u002F\u002Fdeveloper.apple.com\u002Fapp-store\u002Fproduct-page\u002F\" target=\"_blank\" rel=\"noopener\">Apple Developer\u003C\u002Fa>). Put the benefit in the headline and the feature name in the subline.\u003C\u002Fp>\u003Ch3 id=\"3-one-idea-per-screenshot\">3. One idea per screenshot\u003C\u002Fh3>\u003Cp>Each caption should describe exactly what the screen below it shows. If the headline says \"Track every habit\" but the screenshot shows settings, shoppers notice the mismatch and stop trusting the listing.\u003C\u002Fp>\u003Ch3 id=\"4-make-the-first-three-count\">4. Make the first three count\u003C\u002Fh3>\u003Cp>Because the first one to three images can appear in search results, the first headline should state the app's core value in plain words. Save secondary features such as widgets, Dark Mode or integrations for screenshots 4 and later.\u003C\u002Fp>\u003Ch3 id=\"5-go-big-and-high-contrast\">5. Go big and high-contrast\u003C\u002Fh3>\u003Cp>Use a heavy, simple sans-serif and give the headline real size. A dark headline on a light backdrop, or the reverse, reads better than mid-gray on a gradient. Google specifically warns against backgrounds that compete with the text, so keep busy images behind the device, not behind the words.\u003C\u002Fp>\u003Ch3 id=\"6-use-the-words-people-search-for-naturally\">6. Use the words people search for, naturally\u003C\u002Fh3>\u003Cp>Appfigures reported that \u003Ca href=\"https:\u002F\u002Fappfigures.com\u002Fresources\u002Fguides\u002Fapp-store-algorithm-update-2025\" target=\"_blank\" rel=\"noopener\">Apple appears to extract text from screenshot captions\u003C\u002Fa> and treat it as part of an app's keyword metadata. The same analysis notes that caption-only keywords seem to be a weaker signal on their own and that repeating them doesn't help. Apple has not officially documented this, so treat it as a bonus. If \"budget tracker\" is your main keyword, a caption like \"Your budget tracker, simplified\" helps shoppers and possibly search. Don't stuff keywords, and keep captions consistent with your app name, subtitle and keyword field.\u003C\u002Fp>\u003Ch3 id=\"7-skip-claims-you-can-t-keep\">7. Skip claims you can't keep\u003C\u002Fh3>\u003Cp>Leave out prices, \"#1,\" \"Best,\" \"Sale,\" launch-week promotions and calls to action. They break Google Play's guidance, can clash with Apple's metadata rules, and go out of date. \"Your notes, synced everywhere\" will still be true next year. \"50% off this week\" won't.\u003C\u002Fp>\u003Ch3 id=\"8-keep-a-consistent-caption-system\">8. Keep a consistent caption system\u003C\u002Fh3>\u003Cp>Use the same position, font, size and color logic on every screenshot. A consistent system makes the set read like a single sequence when shoppers swipe through it. Change one thing per screen, such as the accent color, if you want variety.\u003C\u002Fp>\u003Ch3 id=\"9-localize-don-t-just-translate\">9. Localize, don't just translate\u003C\u002Fh3>\u003Cp>Both Apple and Google ask you to localize screenshots for each market. German and French captions often run longer than English, so leave room in your layout or rewrite the line instead of shrinking the type. Have a native speaker check that the benefit still lands.\u003C\u002Fp>\u003Ch2 id=\"where-should-captions-go-above-or-below-the-device\">Where should captions go: above or below the device?\u003C\u002Fh2>\u003Cp>Most apps put the caption above the device, because the headline is the first thing people read when scanning from the top. Place it below when the most important UI sits at the top of your screen and you want it fully visible. Whichever you choose, use the same position across the whole set.\u003C\u002Fp>\u003Cp>Tilted device angles give a caption more breathing room. A hero-left or hero-right angle frees space beside the phone, which leaves room for a two-line headline without covering the UI. A flat front view keeps the screen as large as possible, which works better for dense interfaces.\u003C\u002Fp>\u003Ch2 id=\"how-to-add-captions-to-device-mockups-in-mockiso\">How to add captions to device mockups in mockiso\u003C\u002Fh2>\u003Cp>In \u003Ca href=\"\u002F\">mockiso\u003C\u002Fa>, captions are built into the mockup workflow, so you don't need a separate design file for basic store screenshots:\u003C\u002Fp>\u003Col>\u003Cli>\u003Ca href=\"\u002Fregister\">Create an account\u003C\u002Fa> and start a \u003Cstrong>New project\u003C\u002Fstrong>.\u003C\u002Fli>\u003Cli>Pick a device, for example an iPhone 17 Pro Max for the 6.9-inch iPhone slot or an iPad Pro 13″ for iPad (see the \u003Ca href=\"\u002F#devices\">full device list\u003C\u002Fa>).\u003C\u002Fli>\u003Cli>Upload your screenshot by clicking, dragging and dropping, or pasting with Ctrl\u002FCmd+V.\u003C\u002Fli>\u003Cli>Choose an angle preset such as \u003Cem>front\u003C\u002Fem>, \u003Cem>hero left\u003C\u002Fem> or \u003Cem>float\u003C\u002Fem>, then fine-tune the lens, yaw, pitch and scale.\u003C\u002Fli>\u003Cli>Set a solid or gradient backdrop with enough contrast for your text, or start from one of the 70 backdrop templates.\u003C\u002Fli>\u003Cli>Turn on the App Store style caption and type your headline and subline.\u003C\u002Fli>\u003Cli>Use the \u003Cstrong>duo\u003C\u002Fstrong> or \u003Cstrong>trio\u003C\u002Fstrong> layout to show consecutive screenshots side by side.\u003C\u002Fli>\u003Cli>Pick a store canvas size preset and export as PNG or JPEG. Choose an opaque backdrop rather than a transparent one, because App Store Connect doesn't accept alpha channels and Google Play requires PNGs without alpha.\u003C\u002Fli>\u003C\u002Fol>\u003Cp>One honest note for Android listings: Google Play's guidance lists device imagery as an element to avoid, because frames can date quickly. For Google Play, consider a flat front angle with a minimal frame, or test frameless screenshots. Device mockups still work well for the App Store, your website, press kits and social posts.\u003C\u002Fp>\u003Ch2 id=\"key-takeaways\">Key takeaways\u003C\u002Fh2>\u003Cul>\u003Cli>Keep each caption to one idea and roughly 3–7 words, and check that it is readable at search-result thumbnail size.\u003C\u002Fli>\u003Cli>Lead with the user benefit. Put the feature name in the subline.\u003C\u002Fli>\u003Cli>On Google Play, keep taglines to 20% of the image or less and avoid calls to action, rankings and sale language.\u003C\u002Fli>\u003Cli>App Store Connect accepts 1–10 screenshots per device size in JPEG or PNG without transparency. Google Play accepts up to 8 per device type.\u003C\u002Fli>\u003Cli>Localize captions for every market, and keep any keywords in captions consistent with your other metadata.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2 id=\"write-your-captions-then-render-them\">Write your captions, then render them\u003C\u002Fh2>\u003Cp>Good App Store screenshot captions come from clear copy first and a clean, consistent layout second. Draft your headlines, pick your angles, and render a full set of captioned device mockups in the browser. \u003Ca href=\"\u002Fregister\">Start your free 24-hour Pro trial\u003C\u002Fa> (no card required), or compare plans on the \u003Ca href=\"\u002Fpricing\">pricing page\u003C\u002Fa>.\u003C\u002Fp>",[49,53,56,59,62,66,69,72,75,78,81,84,87,90,93,96,99],{"id":50,"text":51,"level":52},"what-are-app-store-screenshot-captions","What are App Store screenshot captions?",2,{"id":54,"text":55,"level":52},"is-text-allowed-on-app-store-and-google-play-screenshots","Is text allowed on App Store and Google Play screenshots?",{"id":57,"text":58,"level":52},"how-long-should-a-screenshot-caption-be","How long should a screenshot caption be?",{"id":60,"text":61,"level":52},"9-tips-for-writing-captions-that-get-read","9 tips for writing captions that get read",{"id":63,"text":64,"level":65},"1-write-the-captions-before-you-design","1. Write the captions before you design",3,{"id":67,"text":68,"level":65},"2-lead-with-the-benefit-then-name-the-feature","2. Lead with the benefit, then name the feature",{"id":70,"text":71,"level":65},"3-one-idea-per-screenshot","3. One idea per screenshot",{"id":73,"text":74,"level":65},"4-make-the-first-three-count","4. Make the first three count",{"id":76,"text":77,"level":65},"5-go-big-and-high-contrast","5. Go big and high-contrast",{"id":79,"text":80,"level":65},"6-use-the-words-people-search-for-naturally","6. Use the words people search for, naturally",{"id":82,"text":83,"level":65},"7-skip-claims-you-can-t-keep","7. Skip claims you can't keep",{"id":85,"text":86,"level":65},"8-keep-a-consistent-caption-system","8. Keep a consistent caption system",{"id":88,"text":89,"level":65},"9-localize-don-t-just-translate","9. Localize, don't just translate",{"id":91,"text":92,"level":52},"where-should-captions-go-above-or-below-the-device","Where should captions go: above or below the device?",{"id":94,"text":95,"level":52},"how-to-add-captions-to-device-mockups-in-mockiso","How to add captions to device mockups in mockiso",{"id":97,"text":98,"level":52},"key-takeaways","Key takeaways",{"id":100,"text":101,"level":52},"write-your-captions-then-render-them","Write your captions, then render them","App Store Screenshot Captions: 9 Practical Tips","Write App Store screenshot captions that get read: length, contrast, keywords, localization and Google Play tagline rules, with a checklist to use today.",[105,108,111,114,117],{"q":106,"a":107},"Can I use emojis in App Store screenshot captions?","Neither Apple's nor Google's screenshot guidance specifically bans emojis in caption text. Use them sparingly, though. They can render differently across fonts, compete with your headline, and don't carry keyword meaning. One emoji as a visual accent is usually the most a caption needs.",{"q":109,"a":110},"Should every screenshot have a caption?","Not necessarily. Captions help most on screenshots where the UI alone doesn't explain the benefit. Games and very visual apps sometimes do better with little or no text. Google Play says to add taglines only when they are needed to convey key characteristics of the app.",{"q":112,"a":113},"Do screenshot captions help App Store search rankings?","Appfigures reported in 2025 that Apple appears to read caption text and treat it as keyword metadata, though as a weaker signal than the keyword field. Apple hasn't officially documented this, so write captions for people first. Natural use of your main keyword is fine; stuffing it in is not.",{"q":115,"a":116},"What font size works for screenshot captions?","Neither store sets a minimum font size. Choose a size that stays readable when the screenshot is shown at search-result thumbnail size, which usually means bold, large type that fills a good part of the canvas width. Test by viewing the exported image at actual thumbnail size on a phone.",{"q":118,"a":119},"Can I use the same captioned screenshots on the App Store and Google Play?","You can reuse the copy, but check each store's rules first. Google Play discourages calls to action, ranking words, time-sensitive taglines and device imagery, and limits taglines to 20% of the image. You may need a separate Play version with smaller captions or no device frame.",false,[122,153,178],{"id":123,"title":124,"slug":125,"excerpt":126,"status":9,"publishedAt":127,"updatedAt":128,"coverImageUrl":129,"coverImageAlt":130,"readingMinutes":14,"wordCount":131,"source":16,"focusKeywords":132,"category":137,"tags":141,"author":152},"cmvxfbv3s000008laxxudp6p6","App Store Screenshot Trends 2026: 8 Styles Worth Using","app-store-screenshot-trends-2026","The biggest App Store screenshot trends in 2026 are outcome-first hero frames, panoramic sets, angled 3D devices, frameless UI crops, dark mode frames, Liquid Glass UI, multi-device sets and bold color blocking. Use each one only where store rules allow it.","2026-11-01T06:03:14.087Z","2026-11-01T06:03:14.105Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fapp-store-screenshot-trends-2026-cover-mvxfbswd-UOXv8F72iD9KsroJvKVVlI6aS3E1h8.jpg","Designer reviewing app store screenshot trends on a smartphone",1706,[133,134,135,136],"app store screenshot trends","device mockup styles","app screenshot design","google play screenshots",{"id":138,"name":139,"slug":140,"description":26},"cmvxbz973000108kxliuusz0h","Design","design",[142,143,144,148,149],{"id":29,"name":30,"slug":31},{"id":33,"name":34,"slug":34},{"id":145,"name":146,"slug":147},"cmvxbz972000008kxigja0le6","device mockups","device-mockups",{"id":42,"name":43,"slug":44},{"id":150,"name":151,"slug":151},"cmvxbz975000208kxi3iyhypr","marketing",{"name":46,"avatarUrl":26},{"id":154,"title":155,"slug":156,"excerpt":157,"status":9,"publishedAt":158,"updatedAt":159,"coverImageUrl":160,"coverImageAlt":161,"readingMinutes":14,"wordCount":162,"source":16,"focusKeywords":163,"category":168,"tags":169,"author":177},"cmvxdcd9n000108ie52zhuyou","App Store Screenshot Rejection: 12 Mistakes to Fix First","app-store-screenshot-rejection-mistakes","Most App Store screenshot rejections come from a few fixable mistakes: splash or login screens instead of the app in use, prices or \"free\" claims, other-platform imagery, real user data, and wrong sizes or transparent PNGs. Google Play adds bans on rankings, awards and promo text.","2026-11-01T05:07:38.406Z","2026-11-01T05:07:38.411Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002Fapp-store-screenshot-rejection-mistakes-cover-mvxdcaal-ub0WBB8VDHnDSXyybdr1RF0PiD9W1e.jpg","iPhone and Pixel 3D mockups illustrating how to avoid an App Store screenshot rejection",1671,[164,165,166,167],"app store screenshot rejection","guideline 2.3.3","google play screenshot policy","app screenshot checklist",{"id":23,"name":24,"slug":25,"description":26},[170,171,172,173,174],{"id":29,"name":30,"slug":31},{"id":33,"name":34,"slug":34},{"id":145,"name":146,"slug":147},{"id":42,"name":43,"slug":44},{"id":175,"name":176,"slug":176},"cmvxce04r000708kx59ilvqys","launch",{"name":46,"avatarUrl":26},{"id":179,"title":180,"slug":181,"excerpt":182,"status":9,"publishedAt":183,"updatedAt":184,"coverImageUrl":185,"coverImageAlt":186,"readingMinutes":187,"wordCount":188,"source":16,"focusKeywords":189,"category":194,"tags":195,"author":201},"cmvxd9hwr000008ieqz0egwe3","3D vs Flat Mockups: When Each Style Works Best","3d-vs-flat-mockups","Use flat mockups when the interface has to be read: the first App Store screenshots, documentation and UI walkthroughs. Use 3D mockups when you need atmosphere and depth: hero images, launch posts, landing pages and later screenshots in the set.","2026-11-01T05:05:24.452Z","2026-11-01T05:05:24.459Z","https:\u002F\u002Frzg4dr9ak9vfbaym.public.blob.vercel-storage.com\u002Fblog\u002F2026-11\u002F3d-vs-flat-mockups-cover-mvxd9ftz-c3k0Epl1aqu4M8NidiHM2Fpi44N79r.jpg","Designer comparing 3D vs flat mockups of a mobile app on a smartphone",8,1912,[190,191,192,193],"3d vs flat mockups","3d device mockups","flat device mockup","app screenshot mockup style",{"id":138,"name":139,"slug":140,"description":26},[196,197,198,199,200],{"id":29,"name":30,"slug":31},{"id":33,"name":34,"slug":34},{"id":145,"name":146,"slug":147},{"id":42,"name":43,"slug":44},{"id":150,"name":151,"slug":151},{"name":46,"avatarUrl":26}]