<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mobile-First on A blog</title><link>https://blog.vfiles.no/tags/mobile-first/</link><description>Recent content in Mobile-First on A blog</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-sa/4.0/deed.en" target="_blank" rel="noopener"&gt;CC BY-SA 4.0&lt;/a&gt;, except where indicated otherwise</copyright><lastBuildDate>Mon, 10 Aug 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://blog.vfiles.no/tags/mobile-first/index.xml" rel="self" type="application/rss+xml"/><item><title>Thumb First, Screen Second: Designing a Music Review Site</title><link>https://blog.vfiles.no/posts/mobile-first-designing-music-reviews/</link><pubDate>Mon, 10 Aug 2026 09:00:00 +0200</pubDate><guid>https://blog.vfiles.no/posts/mobile-first-designing-music-reviews/</guid><description>&lt;p&gt;I built &lt;a href="https://music.vfiles.no"&gt;music.vfiles.no&lt;/a&gt; as a place to publish music reviews, artist pages, and yearly top lists. It&amp;rsquo;s a Gatsby and React site under the hood, but this post isn&amp;rsquo;t really about the stack. It&amp;rsquo;s about a decision I made before writing a single component: design for the phone first, and let the computer screen catch up later.&lt;/p&gt;
&lt;h2 id="why-mobile-first-actually"&gt;Why mobile first, actually&lt;/h2&gt;
&lt;p&gt;Everyone says &amp;ldquo;mobile first&amp;rdquo; until it&amp;rsquo;s inconvenient. Then the moodboard becomes a 1440px Figma frame, the hero image gets a 21:9 crop, and the phone version turns into &amp;ldquo;well, it&amp;rsquo;ll probably wrap fine.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>