Singapore MRT Map: LRT Planner

The first 3 screenshots do not build a clear install story.

The first three move from route planning to route selection to trip details, giving a workable install story.

The first screenshot shows a low-conversion screen. Lead with the product outcome.

#1 is a strong lead screen with route-planning context; #2 is rawer and more functional but still on-core.

Screenshot 1 explains the category, but the user benefit could be more specific.

#1 combines a clear route-planning headline with a transit map and route UI, so the use case is understandable at a glance.

Captions explain the feature, but the user benefit could be more specific.

Captions are benefit-oriented, though several read more like feature labels than outcome-led promises.

The gallery relies on raw app UI without decorated store creative or a benefit-led caption layer. Add readable headlines, proof callouts or framing so new users understand the value faster.

Most screenshots use store-facing captions over product UI, but the set is still largely standard marketing-panel framing.

Multiple screenshots repeat the same idea.

Some screenshots repeat the same template-like product framing, but each still surfaces a different feature.

The screenshots sound like any app in the category. Add a sharper differentiator.

Specific Singapore transit coverage and offline planning differentiate it, though the store creative style is fairly conventional.

The gallery shows features but not the payoff users want.

The gallery shows outcomes like route time, transfers, and nearby places, but several panels still lean on feature views.

The screenshots are understandable, but they do not create enough visual pull. Add a stronger hook, more distinctive composition and more energetic category-relevant art direction.

Clean and usable, but the gallery is fairly static and not especially eye-catching.

The screenshots lack enough concrete visual hook mechanics. Add pull-outs, callout overlays, arrows, gesture cues, proof badges, awards/laurels, context scenes, comparisons or depth where they help sell the value.

Uses depth/layering and angled phone mockups, but few stronger hook devices beyond standard framing.

The screenshot composition feels plain or poorly spaced. Tighten alignment, crops and padding so the gallery feels intentionally designed.

Balanced and clean, but the layouts are straightforward and template-like rather than especially crafted.

The screenshots do not feel premium or distinctive enough. Improve brand craft, typography, colour and art direction.

Competent and consistent, but the art direction is safe and template-like rather than premium.

Key screenshot text is difficult to read at store browsing size.

Main headlines are readable, but the set includes several compact supporting labels and small in-phone details.

The app UI is too small to inspect. Enlarge the product so users can see what they get.

The app UI is visible and inspectable, though some panels present it at a moderate-to-small scale inside the mockups.

The screenshot style feels less polished or category-aligned than users may expect. Make the visual treatment more coherent and grounded in the category.

Polished and on-category for maps/navigation, but the creative is basic rather than distinctive.

Key screenshot text may have low contrast. Increase text/background contrast so captions scan clearly.

Image contrast check sampled 8 text-bearing screenshots. · AI readability analysis did not identify low-contrast key text, so global image edge samples were not used as a text contrast warning.

Screenshots feel visually cluttered. Make the headline and product UI easier to scan.

Clear headline-to-phone hierarchy with strong contrast and readable focus areas.

Average rating

No public average rating is available yet.

Rating volume is still building, so the score may carry less trust than a larger review base.

No public rating count was supplied by the listing provider.

The screenshots are not using available trust proof. Test truthful proof cues such as rating/review badges, awards/laurels, press, user-count proof, no-ads/privacy cues or other credible proof where they help users trust the app.

Screenshots themselves do not surface badges, ratings, testimonials, or awards; the app UI provides functional proof only.

Title/secondary metadata keyword overlap

It introduces offline use and Sentosa route planning, so it is not merely duplicative.