Appy

The design came as a Photoshop file: one width, everything in position, nothing about what happens at 375 pixels or what any of it does when touched. An app landing page also has a single conversion — the download — and a visitor who will not read far to reach it, so the order the argument arrives in matters as much as the pixels. Both of those are build decisions the PSD leaves open.

I converted the PSD into HTML, CSS and JavaScript by hand, and kept the layout running the argument the way a sceptical visitor asks for it: what the app is, proof that it works, what it looks like, what it costs, and the questions people ask before installing anything. Store buttons sit in the hero and again at the download call to action, so the conversion is never more than a scroll away.

• Hero and download call to action both carrying App Store and Play Store buttons
• Six feature cards, a video demonstration and a statistics band as proof
• Screenshot gallery, three pricing tiers and an FAQ, in that order
• Every section taken down to phone width deliberately, which the PSD did not cover

Static HTML on Bootstrap with its own stylesheet, and no jQuery — only the libraries the page genuinely uses: a slider for the gallery, a lightbox for the video, scroll animation, and an icon set. A template buyer should be able to open it and recognise everything:

• HTML5
• CSS3
• Bootstrap
• Swiper
• GLightbox
• AOS
• Linearicons

The PSD became a working template rather than a one-off page: content-agnostic sections, markup a buyer can open and extend, and responsive behaviour decided rather than inherited. It was later provided to Colorlib and has been hosted on their demo site since.