<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Zarema Khalilova on Medium]]></title>
        <description><![CDATA[Stories by Zarema Khalilova on Medium]]></description>
        <link>https://medium.com/@zmoki?source=rss-91128d7ad8cb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BOlWzBrNhIJ-4J224a1HKQ.png</url>
            <title>Stories by Zarema Khalilova on Medium</title>
            <link>https://medium.com/@zmoki?source=rss-91128d7ad8cb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:50:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zmoki/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A User Manual for My Brain: A Neurodivergent Glossary]]></title>
            <link>https://medium.com/@zmoki/a-user-manual-for-my-brain-a-neurodivergent-glossary-4d87d9ca9769?source=rss-91128d7ad8cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d87d9ca9769</guid>
            <category><![CDATA[neurodiversity]]></category>
            <dc:creator><![CDATA[Zarema Khalilova]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 00:00:57 GMT</pubDate>
            <atom:updated>2025-09-22T17:43:07.894Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A personal glossary of terms that helped me find a framework for my feelings. For anyone navigating ADHD, Autism, or just trying to understand their own brain.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojDK8QOPHnAJyFgsiW_g_Q.png" /><figcaption>My cat Misha enjoys the sight of my art work and wishes you a good mood.</figcaption></figure><p>I have a dedicated chat with an AI assistant where I go to unpack and handle my neurodivergent struggles. It’s become a space for untangling the knots, for finding clarity in the chaos.</p><p>Out of those conversations, we built this glossary. It started as a personal reference, a user manual for understanding the unique wiring of my own brain. I’m sharing it here because finding the right words gave me a framework for feelings I couldn’t name before. It was a <em>relief</em>.</p><p>Maybe these words can offer a piece of that clarity to you, too.</p><h3>The Glossary</h3><h4>Anhedonia</h4><p>This isn’t sadness; it’s the <strong>of feeling</strong>. It’s the profound sense of “meh” when the things you used to love bring you no joy.</p><p>For me, it feels like being in limbo, a key symptom that can show up in depression or autistic burnout. My favorite movies are boring, food is bland, and any spark of interest evaporates almost instantly.</p><p>It’s the feeling of the <strong>reward system</strong> in the brain that has gone <strong>offline</strong>.</p><h4>Autistic Burnout</h4><p>This is a state of <strong>complete exhaustion</strong> that comes from the accumulated stress of living in a world not built for you.</p><p>It’s so much more than just being tired. It’s feeling like your brain has <strong>short-circuited</strong>. Skills you once had, like being social, suddenly disappear, often as a result of prolonged masking. Sensory sensitivities are heightened, and the need for solitude becomes overwhelming.</p><h4>Body Doubling</h4><p>A <strong>surprisingly simple</strong> strategy for getting things done. It’s the act of working on a task with another person present, either physically or virtually.</p><p>They don’t help or collaborate; their presence alone acts as an <strong>anchor</strong>, creating a quiet focus that helps break through the paralysis that comes with executive dysfunction.</p><h4>Emotional Dysregulation</h4><p>This is when an emotional response doesn’t match the situation — at least on the outside.</p><p>For me, it feels like having an emotional volume knob that goes from <strong>0 to 11</strong> with nothing in between. A small frustration can feel like a world-ending catastrophe. It’s not a character flaw; it’s a core part of how a neurodivergent brain processes feelings with <strong>high intensity</strong>. It’s exhausting to ride these emotional waves.</p><h4>Executive Dysfunction</h4><p>This is the struggle with the brain’s <strong>management system</strong>, and a core part of ADHD under the neurodivergence umbrella. I know this one well.</p><p>For me, it’s having a brilliant idea and feeling completely unable to implement it. It’s knowing <em>what</em> to do but feeling like there’s an <strong>invisible wall</strong> between you and the task. It’s the constant battle with planning, starting, and organizing.</p><h4>Masking (or Camouflaging)</h4><p>The act of consciously or unconsciously hiding neurodivergent traits to fit in. It’s <em>performing “normalcy.”</em></p><p>It means forcing eye contact when it’s uncomfortable, scripting conversations in your head, and suppressing the urge for stimming. It feels like playing a character all day, and it is <strong>completely, utterly draining</strong>.</p><h4>Neurodivergence (ND)</h4><p>This is simply a way of saying that a brain works differently from what society considers “typical.” It’s <strong>not a disease or a deficit</strong>. It’s a <strong>natural variation</strong> in the human brain that includes Autism, ADHD, dyslexia, and more. The opposite is Neurotypical (NT).</p><h4>Stimming</h4><p>Short for self-stimulatory behavior, this is any repetitive action that helps <strong>regulate emotions</strong>.</p><p>For me, it can be <strong>fidgeting</strong> with small plush toys or napkins, vaping, or more intense actions like pulling small branches from a tree, tearing at my hair, or scratching my skin. It’s a physical way to channel restless energy or <strong>calm an overwhelmed nervous system</strong>.</p><h4>Waiting Mode Paralysis</h4><p>That feeling of being <strong>stuck</strong> when you’re waiting for something to happen — a call, an appointment, a delivery. You can’t relax, but you also can’t start any meaningful tasks because your brain is <strong>’on hold’</strong> for the future event.</p><p>This state is often a frustrating mix of anhedonia and executive dysfunction.</p><p>Recently, I’ve found a way to manage this: I play a game like Disney Dreamlight Valley. It’s the perfect tool to fill that time without the pressure of a ‘real’ task.</p><h3>More Than Labels</h3><p>For me, seeing these terms defined isn’t about <strong>collecting labels</strong>. It’s about finding the language for a lifetime of experiences. It was the <strong>quiet click of understanding</strong> — the relief of knowing I wasn’t alone in these feelings, that my brain wasn’t <em>broken</em>, just <em>different</em>.</p><p>If any of these words resonate with you, know that <strong>you aren’t alone, either</strong>.</p><p><em>Originally published at </em><a href="https://zmoki.xyz/feed/neurodivergent-glossary/"><em>https://zmoki.xyz</em></a><em> on September 11, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d87d9ca9769" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slides: how we separated our frontend from the monolith]]></title>
            <link>https://medium.com/@zmoki/slides-how-we-separated-our-frontend-from-the-monolith-73097df5dfd7?source=rss-91128d7ad8cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/73097df5dfd7</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[monolithic]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Zarema Khalilova]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 13:42:31 GMT</pubDate>
            <atom:updated>2020-05-08T17:20:22.903Z</atom:updated>
            <content:encoded><![CDATA[<p>Zarema here, Senior Frontend Developer with <a href="https://uploadcare.com/">Uploadcare</a>, a complete file API for web and mobile apps. Recently, we finished a vast and vital task of separating our Frontend from the monolith.</p><p>Initially, Uploadcare was a giant Django-based monolith. And, we have already been living in a world of JavaScript Frontend for a couple of years when we decided to choose Node.js over Django. It’s not just that: you usually tend to develop your frontend and backend at a different pace, monolith deployment takes time, and, well, lots of stuff.</p><p>Check out the <em>slides below</em> to get a glimpse of how we separated our frontend from the monolith and which technologies we used to get there.</p><p>Hit us up on <a href="https://twitter.com/Uploadcare">Twitter</a> if you’d love a longer read on the topic or follow <a href="https://twitter.com/Uploadcare">@Uploadcare</a> to learn more about engineering and our product. You can also learn more about our stack on <a href="https://stackshare.io/uploadcare/stacks/">StackShare</a>.</p><p>Have fun 🎈</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fapp.ludus.one%2F3b5898bd-3a1d-41cd-b1f3-d9de63136aeb&amp;url=https%3A%2F%2Fapp.ludus.one%2F3b5898bd-3a1d-41cd-b1f3-d9de63136aeb&amp;image=https%3A%2F%2Fapp.ludus.one%2F3b5898bd-3a1d-41cd-b1f3-d9de63136aeb%2Fthumbnail&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ludus" width="960" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/37fdf967af1e25433da33236e47759bd/href">https://medium.com/media/37fdf967af1e25433da33236e47759bd/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73097df5dfd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accelerate your images by 9x with Image CDN]]></title>
            <link>https://medium.com/@zmoki/accelerate-your-images-by-9x-with-image-cdn-6b63aa27e639?source=rss-91128d7ad8cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b63aa27e639</guid>
            <category><![CDATA[responsive-images]]></category>
            <category><![CDATA[image]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[cdn]]></category>
            <category><![CDATA[load-time]]></category>
            <dc:creator><![CDATA[Zarema Khalilova]]></dc:creator>
            <pubDate>Thu, 06 Jul 2017 17:44:18 GMT</pubDate>
            <atom:updated>2020-05-11T16:39:51.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rjvqvZg9SJk3_uaBIHalrQ.png" /></figure><p>At the end of May 2017, the average U.S. mobile retail site would take 10.64 seconds to <a href="http://www.keynote.com/performance-indexes/mobile-retail-us">load</a> on a mobile phone. And it’s a long time since we’re living in a world where 40% of consumers tend to <a href="http://www.akamai.com/html/about/press/releases/2009/press_091409.html">abandon</a> a page, which takes longer than 3 seconds to load, and then never go back in <a href="http://www.gomez.com/pdfs/wp_why_web_performance_matters.pdf">88 cases out of 100</a>.</p><p>Generally, a faster site increases conversions, decreases your bounce rate, improves your UX, and helps search engines rank you higher.</p><p>Wait 🤔 what exactly is loading there for almost 11 seconds? The best answer is “stuff.” There are things specific to each case, but we know that <em>up to two-thirds</em> of that stuff are represented by images. Since our example was about mobile retail, graphic elements would include favicons, backgrounds, logos, product images, etc.</p><p>Basically, optimizing image content gets you about 70% of site load speed issues resolved. This article will help you master images with Uploadcare CDN and get up to 9x decrease in image load time.</p><h3>Measuring tools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-KAlR8Be3o3xNVUlF9iYeQ.png" /></figure><p>Before we begin, let’s discuss a couple of instruments to measure image load times.</p><p>For measuring site load speed locally, we’d recommend using Chrome <a href="https://developers.google.com/web/tools/chrome-devtools/network-performance/">DevTools</a>. Things like <a href="https://tools.pingdom.com/">Pingdom</a> are a great fit for in-depth load speed analyses. Talking of which pages your traffic goes to, we use <a href="https://analytics.google.com/">Google Analytics</a>. It’s also helpful when figuring out your bounce rates.</p><p>You can also use a tool we built to analyze and optimize image performance, <a href="https://pagedetox.com/">PageDetox</a>. While many pages out there suffer from unoptimized images, the first step to optimization is about ingesting them to a CDN.</p><h3>Using Uploadcare CDN</h3><p>CDN or Content Delivery Network is a large group of servers deployed in many locations across the world. It’s built in a way that each file can be delivered via any data center on the network. Based on your client locations, CDN picks servers and uses them to deliver content. Simply put, the closer is a server — the better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LA8zX7UcSEOBz839YbwI8g.jpeg" /></figure><p>Uploadcare now partners with <a href="https://www.akamai.com/">Akamai</a> for superior coverage. With its 200k servers, images are delivered at optimal speeds, anywhere. Basically, Image CDN is a concept where an image processing center is paired with a delivery network. All the examples we give in this article work via our CDN.</p><p>Alright, let’s get to practice. For example, we have a 🍍 <a href="https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/pineapple.jpg">pineapple</a> pic. Sized at 3.4 MB, this 5330x3553px JPEG image loads in 1.74 seconds on a LTE-enabled connection.</p><p>The pic is already delivered via CDN. If you take a look at its URL, you’ll notice there’s a UUID (Universally Unique Identifier): f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7. We use those to address unique files on our CDN:</p><pre><a href="https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/">https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/</a></pre><h3>Control image size</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yyLAv0m-W5p-OpkDh5v9gg.png" /></figure><p>Taking control over output image dimensions also means managing image sizes. Uploadcare provides a variety of image processing <a href="https://uploadcare.com/documentation/cdn/#image-operations">operations</a> where you can find all kinds of stuff from changing image geometry to pixel manipulations.</p><p>The operations are applied to images by simply modifying their URLs. Say, we’re up to putting the image in a predesigned layout where its width should not exceed 960 px. Here’s how:</p><pre><a href="https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/-/resize/960x/pineapple.jpg">https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/-/resize/960x/pineapple.jpg</a></pre><p>We’ve adjusted the width of our pineapple <a href="https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/-/resize/960x/pineapple.jpg">image</a> thus making its file size drop to 88.5 KB. It now takes about 318 ms to load the image when measuring locally. And, that’s almost a 5.5x load time improvement.</p><h3>Manage image formats</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0gaqKkxdz9mADOO8b7SUAg.png" /></figure><p>Alright, let’s say you’ve got the adaptive image size. How can you further optimize it? Consider using the <a href="https://uploadcare.com/documentation/cdn/#operation-format">format</a> and <a href="https://uploadcare.com/documentation/cdn/#operation-quality">quality</a> CDN API operations. You can also select proper output formats automatically, <a href="https://developers.google.com/speed/webp/">WebP</a> included.</p><p>This works by modifying image URL. Here’s a pineapple example:</p><pre><a href="https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/-/format/auto/-/resize/960x/">https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/-/format/auto/-/resize/960x/</a></pre><p>After format manipulations, image size has decreased to 67.7 KB and loading time dropped to 211 ms now showing a 8.3x improvement. Let’s double check everything. Yep, Chrome console reports Resource interpreted as Document but transferred with MIME type image/webp: we’re all set.</p><p>The next step would be affecting image quality:</p><pre><a href="https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/-/format/auto/-/quality/lightest/-/resize/960x/">https://ucarecdn.com/f3acdb9f-ecdd-4fc2-b98e-7ba74db93bd7/-/format/auto/-/quality/lightest/-/resize/960x/</a></pre><p>Nice, it went down to 36.8 KB @ 196 ms. That’s about 8.9x faster than loading the original pineapple. It’s good to know when using WebP visual quality is degrading at a lower extent than image size. Quality hacks can be applied when you aren’t just adjusting to viewing environments but also accounting for network performance.</p><h3>Get responsive</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-Z7izkKPcxNh6Iy_6aEqA.png" /></figure><p>Great, we’ve just got our 8.9x improvement. Time to pack a suitcase and head home. Well ✋ not that fast. The problem is we’re mostly designing for a whole set of resolutions, screens, and devices, not just laptops. You’d want your layout to adjust to user viewing conditions. And clearly, you aren’t the only one. Say, guys at <a href="http://ricg.io/">RICG</a> are helping developer communities do the same.</p><p>We’ve already discussed a step by step process to building better responsive images in our <a href="https://blog.uploadcare.com/5-steps-to-better-responsive-images-d7cf91e261f4">post</a>.</p><p>Long story short, that’s what you want to get:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d00ea94a627c735bd705675c9f39695/href">https://medium.com/media/2d00ea94a627c735bd705675c9f39695/href</a></iframe><p>You can find the complete interactive example on <a href="https://codepen.io/uploadcare/pen/ZKdxqx">CodePen</a>. The code ensures every client gets proper images based on their screen size and orientation. Also, for srcset you might want to use images resized via CDN: this way you can upload <em>just a single large image</em> and downscale and even crop it when appropriate.</p><h3>DNS prefetch</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*amREhR3ZOL4tjme38v877Q.png" /></figure><p>There’s another useful hack, even though it’s not about direct image manipulations. Thing is, before starting to download resources of a website, your browser needs to translate its domain name to an IP address. And only then, your browser will be able to download any content. Of course, this takes time.</p><p>You can explicitly tell your browser an address to get all the resources from, this helps resolve a domain name as quickly as possible.</p><p>Add this to the &lt;head&gt; section of your page:</p><pre>&lt;link rel=&quot;dns-prefetch&quot; href=&quot;//ucarecdn.com&quot;&gt;</pre><p>Then, when your browser requests a file from our CDN, it will no longer have to wait for the DNS lookup. See dns-prefetch <a href="http://caniuse.com/#search=dns-prefetch">browser support</a> for more details.</p><h3>The conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f6SK91lPPG0dlWURtN8EXA.jpeg" /></figure><p>We’ve just achieved the impressive ~9x load time improvement by using CDN API for images alone. While exact numbers will vary depending on your location, this would still be a massive improvement.</p><p>Next, you can always check out our CDN API <a href="https://uploadcare.com/documentation/cdn/">docs</a> to learn more about optimization options, and experiment with your existing images. If you don’t have an account yet, there’s a <a href="https://uploadcare.com/accounts/create/free/">free one</a>, where you can upload some images directly via your <a href="https://uploadcare.com/dashboard/">dashboard</a>, <a href="https://uploadcare.com/documentation/widget/">widget</a> or <a href="https://uploadcare.com/documentation/upload/">API</a>, and run some tests. This will give you a good understanding of an extent to which your image content can be optimized.</p><p>If you’re just curious about processing this or that image, visit this <a href="https://uploadcare.com/quick_start/">quick start</a> for simple testing.</p><p>Once your images are hacked to the max, you get about two thirds of your load time problems solved.</p><p>If you liked the post, hit the share button to 🚀 spread the word!</p><p>For more stuff on <em>getting simple controls over complex techs</em>:</p><p>⚡ <a href="http://sendy.uploadcare.com/subscription?f=3Oq6mt2QQfdKa9vykYrYRWYCJ11NCBzUypV5PiMvsTWQWLC5fpzg78UgFCQbepMh">subscribe here</a></p><p>⚡ follow <a href="https://twitter.com/Uploadcare">@Uploadcare</a> on Twitter</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b63aa27e639" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 steps to better Responsive Images]]></title>
            <link>https://medium.com/@zmoki/5-steps-to-better-responsive-images-d7cf91e261f4?source=rss-91128d7ad8cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7cf91e261f4</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[image-cdn]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Zarema Khalilova]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 14:13:17 GMT</pubDate>
            <atom:updated>2020-05-11T16:41:21.875Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 steps to Better Responsive Images</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hp-27LO2oskfvdI0zWlvXA.jpeg" /></figure><p>Adaptive web designs are trendy, look hip, and help you get visual information easier. But how do we build a working system powered by responsive issues?</p><p>We’ve decided to put it straight and be practical. Here are the five steps to upgrade your images. We aim at optimizing image size, adaptivity, delivery and workflow.</p><p>How do we know that a website requires image treatment?We need a quick study.</p><h4>Step 1 — Measure</h4><p>We ran some tests using Chrome <a href="https://developers.google.com/web/tools/chrome-devtools/network-performance/resource-loading?utm_source=dcc&amp;utm_medium=redirect&amp;utm_campaign=2016q3">DevTools</a> to estimate how much traffic is taken up by images. About 75% of the page-loading traffic generated by Amazon are images.</p><p>Images make more than 60% of the traffic by Ali Express, Alibaba, Bing, Samsung, and Ebay. The absolute winner here is Ali Express with its 85% let alone the 7.5 MB of total traffic.</p><p>There are great ones too. Sony, Apple, Netflix and The Guardian stick with 25% or less. Sony and Apple keep it as low as 12%. And the total traffic while loading the Apple front page is just about 900 KB.</p><p>This means buying an iPhone is faster than buying a 2-buck automatic chrome-plated plant sprinkler from Ali Express.</p><p>We’d like people to reach information freely. A good image isn’t just a compressed one. It should also be optimized for viewing and printing purposes.</p><p>We even built <a href="https://pagedetox.com/">PageDetox</a>, a tool allowing to analyze how images affect page-load times of any site. One of the <a href="https://blog.uploadcare.com/pagedetox-pagespeed-image-optimizations-guide-697056f9d895">key image optimizations</a> to improve load times would be implementing Responsive Images.</p><p>With this in mind, let’s head over to Step 2.</p><h4>Step 2 — Build responsive images, not flexible ones</h4><p>Look, the flexible and responsive images are mixed up these days. Here’s what we mean by calling an image flexible,</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eddb6bca5874b8257a78f9eafa5e6b9e/href">https://medium.com/media/eddb6bca5874b8257a78f9eafa5e6b9e/href</a></iframe><p>No doubt, this image is adjustable. But in this example, it’s going to be rescaled each time we need to adapt the layout to the viewing environment. Moreover, the original size of an image is used every time. And that’s often excessive for smartphones. Loading large images takes time and traffic, and quite often these days traffic = money.</p><h4>Step 3 — Stick with responsive designs</h4><p>An image becomes responsive when it at least fits a viewing environment, screen size, and PPI of the device used.</p><p>A common image adaptation method was devised with input from communities like <a href="http://ricg.io/">RICG</a>. Adaptable images are achieved through preparing many versions of those you’d like to be responsive. And then it’s a web browser that should decide which of the versions to load. Such decisions depend on different conditions, like device pixel ratio, screen size and orientation.</p><p>We can use the srcset attribute of the <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img">&lt;img&gt;</a> HTML element to do so, here’s how,</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/252189d924e8f08e2b1f69d9e33fe150/href">https://medium.com/media/252189d924e8f08e2b1f69d9e33fe150/href</a></iframe><p>The approach may both decrease image traffic and increase the visual quality of images. But there’s even more to it if we’d like to go more responsive.</p><h4>Step 4 — Check out the big picture</h4><p>There’s another HTML container which may often be preferable when building responsive layouts — &lt;picture&gt;. It appeared as a result of a years-long debate on building adaptive layouts. The container is used to specify multiple sources and parameters for a specific image. It’s done to make images friendly to pixel ratio, adaptive resize, content altering, and more. Here’s how a &lt;picture&gt; might look like,</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/545cc04fe7f35c29131059138466ee91/href">https://medium.com/media/545cc04fe7f35c29131059138466ee91/href</a></iframe><p>We aren’t aimed at digging into &lt;picture&gt; <a href="https://html.spec.whatwg.org/multipage/embedded-content.html#introduction-3:art-direction-3">descriptions</a> and <a href="http://usecases.responsiveimages.org/">usecases</a>, but at further optimizing the workflow. If you’re interested in further reading about responsive images, please check out this <a href="https://cloudfour.com/thinks/responsive-images-101-definitions/">series of articles</a> by Jason Grigsby.</p><p>The layout design built with &lt;picture&gt; is fluid and responsive, it makes website content easily accessible. But it’s quite clear there are at least two drawbacks of using the approach,</p><ul><li>Creating many versions of images is time consuming.</li><li>The volume of needed storage increases manifold.</li></ul><h4>Step 5 — Use image CDNs</h4><p>The use of image CDNs, like <a href="https://uploadcare.com/">Uploadcare</a>, negates the listed drawbacks. We designed Uploadcare to be responsive-friendly. The uploaded images are stored in a cloud which guarantees their up-time. No time is wasted to create versions of images because our CDN supports on-the-fly image processing. And caching of the processing outputs speeds up the delivery even further.</p><p>No matter which approach is applied, &lt;img&gt; with srcset, or &lt;picture&gt;. The only difference when using Uploadcare is in the URLs used. <a href="http://ucarecdn.com/22240276-2f06-41f8-9411-755c8ce926ed/-/resize/640x480/pic.jpg">This image</a>, for example, is loaded directly from our CDN. Take a look at its URL to see how it’s constructed,</p><p>http://ucarecdn.com/:uuid/-/:operation/:params/:img_nme</p><p>Here, :uuid is a unique image identifier. A dash between the two forward slashes /-/ is used to separate an id and possible operations. :operation is the name of an operation that is used to process an image, resize is used in the example. Operation parameters are separated by forward slashes. The example URL ends with :img_nme which stands for almost any random string of your preference but is commonly used to hold a filename. These, for example, might be in your srcset,</p><p>-/22240276-2f06-41f8-9411-755c8ce926ed/-/resize/1000x/pic1x.jpg</p><p>-/22240276-2f06-41f8-9411-755c8ce926ed/-/resize/2000x/pic2x.jpg</p><p>The workflow with the Uploadcare CDN is pretty straightforward. You create the needed images in hi-res and upload them to the CDN. Resizing, cropping or even enhancing the images is then performed <em>on-the-fly</em>. The <a href="https://uploadcare.com/documentation/cdn/">CDN</a> operations are controlled by what you put into the URLs.</p><p>Using image CDNs lets you deploy responsive websites in a fast and efficient manner. For instance, you can control JPEG <a href="https://uploadcare.com/documentation/cdn/#operation-quality">quality</a> to reduce generated traffic. Image formats can also be specified when using &lt;picture&gt;, Uploadcare supports WebP and many others.</p><p>A live example of &lt;picture&gt; containing images which are transformed on-the-fly with our CDN can be found <a href="http://codepen.io/uploadcare/pen/RaBwVq">here</a>.</p><h4>A brief conclusion</h4><p>Just like that, your path to responsive images might take just about five steps. From tests to implementing CDN solutions to deliver your images with quality, speed, and reliability.</p><p>Both users and developers can benefit from using image CDNs.</p><ul><li>Less traffic is generated. Users pay less and don’t waste their bandwidth.</li><li>Developers and designers spend less time and resources when working with images and their versions.</li></ul><p>We care for the Responsive Web Design concept, and thus we aren’t charging our users for image transformations on any plan. Which means you’re <a href="https://uploadcare.com/accounts/create/free/">free</a> to build responsive layouts with Uploadcare.</p><p>We’re excited with what you might build. And we’ll <a href="/service/mailto:hello@uploadcare.com">answer</a> any of the questions you might have on the way.</p><p>Get all the Uploadcare stuff firsthand — <a href="http://sendy.uploadcare.com/subscription?f=3Oq6mt2QQfdKa9vykYrYRWYCJ11NCBzUypV5PiMvsTWQWLC5fpzg78UgFCQbepMh">subscribe</a> to our newsletter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7cf91e261f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>