<?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[Aras™ Digital Products - Medium]]></title>
        <description><![CDATA[Software and Data Engineering - Medium]]></description>
        <link>https://medium.com/arasdigitalproducts?source=rss----f171b2c44fe7---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Aras™ Digital Products - Medium</title>
            <link>https://medium.com/arasdigitalproducts?source=rss----f171b2c44fe7---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:32:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/arasdigitalproducts" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[“Artificial, but ours”: A Hackathon Where the Best Prompt Wins]]></title>
            <link>https://medium.com/arasdigitalproducts/artificial-but-ours-a-hackathon-where-the-best-prompt-wins-8690fbbc7efd?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/8690fbbc7efd</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Aras™ Digital Products]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 10:27:05 GMT</pubDate>
            <atom:updated>2025-04-18T11:06:59.024Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2jhfGtm6IcOPQkLaGTxeA.png" /><figcaption>Vibecoding</figcaption></figure><p>Last week, something special happened. In a cozy afterwork setting filled with pizza, snacks, and just the right amount of healthy competition, teams from <a href="https://pseudocode.agency/"><strong>Pseudocode</strong></a> and <a href="https://www.instagram.com/_arasdigital/"><strong>Aras™ Digital Products</strong></a><strong> </strong>came together for a vibecoding session we called <strong>“</strong>Artificial, but ours<strong>”</strong> — a nod to the growing power of AI that still feels uniquely human when we put our own spin on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cpbsj3NrdjVdxqiisT2vzw.png" /><figcaption>AI Hackathon: “Artificial, but ours”</figcaption></figure><p>This wasn’t just your regular hackathon. It was <strong>a cross-disciplinary sprint</strong> where developers, designers, and curious minds from both companies joined forces to explore what AI tools can do when they’re put to creative and practical use. And wow — did the teams deliver.</p><h3>Projects That Made Us Go: “Wait, AI Did That?”</h3><p>The vibe was loose but the ideas were sharp. Some teams went full fun-mode, developing games like <em>Sinking Ships</em> and chess with AI-assisted logic and user experience. Others went practical: one team created a tool to help project managers build ideal teams by analyzing project requirements, team skills, and availability — a kind of AI-powered matchmaking for better delivery.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0bzasUoVQ3A%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0bzasUoVQ3A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0bzasUoVQ3A%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c69cf5ac9b5146e869ab83d7d540c48f/href">https://medium.com/media/c69cf5ac9b5146e869ab83d7d540c48f/href</a></iframe><p>There was even a team that tackled a very real office dilemma with a lighthearted twist: a reward system for keeping the toilet clean (we’re not saying it’s glamorous, but it’s genius in its own way).</p><p>And then there was <strong>the showstopper</strong>: the winning project, a tool designed to support hospitals by tracking patient data and improving communication between families and medical staff developed by Romano Baturina. A real-world use case with real impact — and a great example of AI being more than just hype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVYcyWqmizWN-U2nHRGJzA.png" /><figcaption>The winning project</figcaption></figure><p>“AI tools are breaking down the barriers between roles — today, designers can stand shoulder to shoulder with senior developers. The only real limit is our creativity. <strong>AI won’t replace people, but people using AI will replace those who don’t.</strong> And it’s not taking our jobs — it’s freeing us up to focus on more meaningful work. Honestly, if AI ever takes mine, I’d love to see it try pouring concrete or laying tile.” Romano Baturina, Product Designer at Aras™ Digital Products</p><h3>Collaboration Over Competition (But Also… Pizza)</h3><p>The competitive spirit was definitely alive — but so was the sense of collaboration. <strong>This wasn’t about who could code the fastest, but about</strong> <strong>learning from each other, pushing ideas further, and seeing how AI can enhance workflows and creativity</strong>.</p><p>We rounded off the evening with a conversation about <strong>integrating AI into daily dev work</strong>, and what the future might hold. It was honest, a little philosophical, and very much needed.</p><p>“I envision a future where AI doesn’t make us do less, but more. More meaningful things. <strong>The focus will shift to ideas, big-picture thinking, and connecting dots that aren’t immediately obvious</strong>. AI’s already doing a pretty good job with the obvious ones.” Ivan Aras, Head of Design at Aras™ Digital Products</p><p>“<strong>It’s incredible to think that just a few months ago, building something like this wouldn’t have been possible</strong>. Congratulations to the winner for such a thoughtful and innovative use of AI tools.” Aron Mišerda, Managing Director at Pseudocode</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ww1Ke1PfbYCwzZhohid0cA.png" /><figcaption>Pseudocode x Aras™ Digital Products</figcaption></figure><h3>What We Took Away</h3><p>More than just cool projects or good snacks, the hackathon gave us a glimpse into what’s coming: <strong>a world where knowing how to prompt AI might just be as important as knowing how to code</strong>. And as always, good prep is more than half the work.</p><p>This event was also a reminder that when smart, curious people come together — whether it’s to solve problems, build games, or ensure the toilets are clean (seriously) — the results can be surprising, inspiring, and sometimes a little bit weird. And that’s exactly how we like it.</p><p>Also, even this blog post was created using Chat GPT. <strong>Practice what you prompt.</strong></p><p>Photo credits go to <a href="https://www.instagram.com/skicaphoto?igsh=MXJmcXdxM2Fvd3ZqYw==">Skica Photo</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8690fbbc7efd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/artificial-but-ours-a-hackathon-where-the-best-prompt-wins-8690fbbc7efd">“Artificial, but ours”: A Hackathon Where the Best Prompt Wins</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility Is Good UX for Everyone]]></title>
            <link>https://medium.com/arasdigitalproducts/accessibility-is-good-ux-for-everyone-6875c64fd13b?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/6875c64fd13b</guid>
            <category><![CDATA[digital-accessibility]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[accessible-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Aras™ Digital Products]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 10:25:57 GMT</pubDate>
            <atom:updated>2025-08-01T13:26:11.946Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-2lRVOr0fOm6q2jEEGHhw.png" /><figcaption>Accessibility is more than good practice</figcaption></figure><p>Accessibility is the backbone of inclusive, resilient design which enables us to create experiences that are usable, flexible, and robust for everyone. It’s not just good practice, it’s great UX. Unfortunately, accessibility is still often misunderstood as something only relevant to people with disabilities.</p><h3>Accessibility Means Better UX for All</h3><p>Designing for accessibility makes our products more usable for more people, in more situations. Whether someone is using a product in low light, on a shaky connection, or without sound, accessible design holds up.</p><p>Inclusive design doesn’t only help people with permanent disabilities; it helps those with temporary or situational limitations like a broken arm, an eye infection, or a baby on one arm and a phone in the other.</p><p>Accessibility is so much more than a niche concern. It’s a broad usability principle that strengthens the entire user experience making our products more adaptable and more scalable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OS-ECnln94uNMhZ2ObYgAg.png" /><figcaption>Accessibility is a broad usability principle strengthening the entire user experience</figcaption></figure><h3>Real-World Examples of Universal Benefits</h3><p>Many accessibility features solve real-world problems for a wide range of users, so they have, in turn, become mainstream. Captions, for one, were originally designed for the hearing impaired and are now essential in noisy environments or when watching content without sound.</p><p>Motor impaired users benefit from keyboard navigation, just like power users, gamers, developers, and anyone with repetitive strain injuries who also get a productivity boost. High contrast modes support aging eyes, but are also invaluable for all users in bright sunlight.</p><p>Clear structure and semantic HTML improve screen reader usability and SEO, while benefiting users and discoverability. Alt text supports screen readers and at the same time improves content indexing and voice search. And this is just to name a few.</p><h3>Accessible Interfaces Are More Intuitive and Drive Innovation</h3><p>The bottom line is that designing for edge cases pushes us to build smarter solutions for everyone. Accessible interfaces prioritize clarity with straightforward labels, meaningful instructions, visual hierarchy, consistency with predictable interactions and behavior, and feedback with helpful error messages, confirmations, and cues. The principles outlined here help everyone navigate digital experiences easily and confidently.</p><p>Moreover, some of today’s most familiar tech features were created from accessibility needs, e.g., voice control as an assistive technology, predictive typing as a motor impairments support, or touch interfaces as a barrier removal effort. Good accessibility always overlaps with good usability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vzhVBTqYW5u3nIWP93FtSw.png" /><figcaption>Many accessibility features solve real-world problems</figcaption></figure><h3>Reducing Cognitive and Emotional Load with Empathy in Action</h3><p>Accessibility often results in simpler, more intuitive experiences. That helps reduce decision fatigue, support neurodiverse users, and streamline mobile interactions.</p><p>Tools like plain language, clear user flows, and structured layouts help everyone understand what to do with more speed and confidence. The thing to keep in mind is that designing for accessibility is designing for real life, it’s not “extra work”. It’s just good design that goes a long way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCgxgMBywrO7dVqdU8aMww.png" /><figcaption>Accessible products make business sense</figcaption></figure><h3>The ROI of Accessibility</h3><p>Accessible products don’t just perform better. They make better business sense. They reduce the number of support tickets, increase conversion rates, extend audience reach, and build strong brand loyalty by making users feel seen, included, and respected.</p><p>When you invest in accessible design, you’re investing in quality, resilience, and trust. Better design for some means better design for everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6875c64fd13b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/accessibility-is-good-ux-for-everyone-6875c64fd13b">Accessibility Is Good UX for Everyone</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Simple Take on WCAG/EAA Rules]]></title>
            <link>https://medium.com/arasdigitalproducts/a-simple-take-on-wcag-eaa-rules-e7c12f4d62d7?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/e7c12f4d62d7</guid>
            <category><![CDATA[accessibility-act]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[digital-product-design]]></category>
            <dc:creator><![CDATA[Aras™ Digital Products]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 10:25:40 GMT</pubDate>
            <atom:updated>2025-07-01T12:49:08.487Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B7OdxVOqjTi4UA8pUmofEQ.png" /><figcaption>Accessibility is the foundation of creating great digital experiences.</figcaption></figure><p>When you hear the term <em>accessibility</em>, do you picture a list of rules to check off before launch? Or maybe a set of legal requirements to avoid any related trouble? It’s high time to flip that script. Accessibility isn’t just a box-ticking exercise; it’s the <strong>foundation of creating great digital experiences</strong>.</p><h3>Accessibility Is a Mindset, Not a Milestone</h3><p>It’s easy to get caught up in acronyms like WCAG and EAA, or to view accessibility as a legal obligation. Only these guidelines aren’t just bureaucratic hurdles, but practical tools that help us create products that are flexible, robust, and welcoming to all users.</p><p>Before taking a closer look at the implications, let’s revisit the meanings of WCAG and EAA.</p><p><strong>WCAG</strong> is a set of international guidelines that help us create web content that’s accessible to people with disabilities. Think of it as a handbook for building websites that work for everyone. On the other hand,<strong> EAA</strong> is a European law that ensures digital products and services are accessible to all, including people with disabilities. It’s about making accessibility a legal right, not just a nice-to-have.</p><p>Now, <strong>true accessibility is a continuous process</strong>. It means considering a wide range of needs at every stage: from brainstorming and wireframing to coding, testing, and beyond. It’s about asking who might be left out and then designing solutions that include them as well, whether that’s through better color contrast, keyboard navigation, or clear instructions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5SqUMFcDWffCIIcTk0G9w.png" /><figcaption>WCAG and EAA rules are practical tools that help us create flexible, robust products welcoming for all users.</figcaption></figure><h3>Accessibility Principles Ensure Universal Usability</h3><p>The <strong>core ideas</strong> behind WCAG and the EAA are simple:</p><ul><li>Make content <strong>perceivable</strong>: Everyone should be able to see, hear, or otherwise sense your content.</li><li>Make interactions <strong>operable</strong>: Everyone should be able to use your site, whether they’re using a mouse, keyboard, or assistive technology.</li><li>Make information <strong>understandable</strong>: Clear language and logical structure help everyone, not just people with cognitive disabilities.</li><li>Make technology <strong>robust</strong>: Your website or app should work both now and in the future, with all kinds of devices and tools.</li></ul><p>While the principles of <strong>Perceivable</strong>, <strong>Operable</strong>, <strong>Understandable</strong>, and <strong>Robust</strong> <strong>(POUR) </strong>are at the heart of WCAG and the EAA, it can help to see how these translate into real-world design decisions. Here’s a simple breakdown with practical examples.</p><h3>1. Making Content Perceivable</h3><p>Everyone should be able to access your content, regardless of how they perceive it.</p><p><strong>Examples:</strong></p><ul><li>Alt text for images: Describe images so screen readers can convey the information.</li><li>Captions and transcripts: Provide captions for videos and transcripts for audio content.</li><li>Color contrast: Ensure text stands out clearly against its background (use tools to check contrast ratios).</li><li>Text alternatives: Offer text versions of non-text content (like charts or infographics).</li></ul><h3>2. Making Interactions Operable</h3><p>All users should be able to navigate and interact with your site, using any input device.</p><p><strong>Examples:</strong></p><ul><li>Keyboard navigation: Make sure all interactive elements work with a keyboard (no mouse required).</li><li>Skip links: Allow users to skip repetitive navigation and go straight to main content.</li><li>Predictable focus: Keep focus visible and logical as users tab through the page.</li><li>No time limits: Avoid content that disappears or changes without user control, or allow users to adjust or turn off time limits.</li></ul><h3>3. Making Information Understandable</h3><p>Content should be clear and easy to comprehend for everyone.</p><p><strong>Examples:</strong></p><ul><li>Simple language: Use plain language and avoid jargon.</li><li>Consistent navigation: Keep menus and buttons in predictable places.</li><li>Clear instructions: Provide helpful, concise instructions for forms and interactive elements.</li><li>Error messages: Explain what went wrong and how to fix it.</li></ul><h3>4. Making Technology Robust</h3><p>Your site should work across all devices, browsers, and assistive technologies.</p><p><strong>Examples:</strong></p><ul><li>Valid HTML: Use clean, semantic code that browsers and assistive tech can interpret.</li><li>ARIA landmarks: Use ARIA roles to help screen readers understand page structure.</li><li>Future-proof design: Avoid features that only work on specific devices or browsers.</li><li>Graceful degradation: Ensure your site works even if some features aren’t supported.</li></ul><h3>Accessibility Is Just Good Design</h3><p>At the end of the day, WCAG and the EAA aren’t just rules. Rather, they’re a <strong>roadmap to digital experiences </strong>that are welcoming, usable, and enjoyable for everyone. When we design with accessibility in mind, we’re not just following the requirements. We’re creating better products for real people, in the real world. You can read more about it in our article <a href="https://medium.com/@arasdigital/accessibility-is-good-ux-for-everyone-6875c64fd13b"><strong>here</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AtQTG0E9pPDS459xmsyefQ.png" /><figcaption>Accessibility should be considered a mindset, not a milestone.</figcaption></figure><h3>The Takeaway</h3><p>Investing in making digital products accessible isn’t just about compliance. It’s about quality, innovation, and respect. And if you remember one thing, let it be the fact that <strong>accessibility isn’t extra work</strong>. It’s just <strong>good design done right</strong>. By making accessibility a process, not a checkbox, you create digital experiences that are resilient, flexible, and welcoming to all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7c12f4d62d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/a-simple-take-on-wcag-eaa-rules-e7c12f4d62d7">A Simple Take on WCAG/EAA Rules</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who Owns Accessibility?]]></title>
            <link>https://medium.com/arasdigitalproducts/who-owns-accessibility-5c113bc13b7f?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/5c113bc13b7f</guid>
            <category><![CDATA[ownership]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[accessible-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Aras™ Digital Products]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 10:25:22 GMT</pubDate>
            <atom:updated>2025-07-11T09:27:54.817Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iMzQ6pJJjTXM2bTzyD1B1w.png" /><figcaption>Accessibility is a shared responsibility.</figcaption></figure><p>Accessibility isn’t just a checklist, a single task on a project board, or the responsibility of one specialist. Accessibility is what makes digital products usable for everyone. But to make it happen, it has to be a shared responsibility across every team, starting from first sketches leading up to final tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1ZQ8w9ZeBDM-Lpjx9yJdw.jpeg" /><figcaption>Inclusive user experiences start with designers, but it doesn’t stop there.</figcaption></figure><h3>Designers, Inclusion Starts with You</h3><p>Good design is accessible design. It starts with clear text, strong contrast, readable fonts, and simple, intuitive flows. These are the foundation of inclusive user experiences. Every design decision either opens doors for more people or quietly closes them. Inclusion starts with intention, right in your court. Own it.</p><h3>Developers, Build Like Everyone’s Counting on You</h3><p>Because everyone is. Here’s the thing: developers turn vision into reality. And accessibility lives in the details of the code, from semantic HTML and meaningful labels to keyboard-friendly interactions. To paint a picture, a feature that only works with a mouse simply isn’t complete. It’s not just about meeting technical standards, but ensuring everyone can use what you’ve built, however they steer their digital experience.</p><h3>Product Managers, Keep It on the Roadmap</h3><p>Accessibility doesn’t survive or thrive by accident. It needs to be prioritized, scoped, and defended. Especially when deadlines get tight. That’s where PMs come in. By embedding accessibility into requirements, timelines, and team priorities, product managers ensure it’s treated as core functionality, not a nice-to-have. Because better access means more users, as well as a stronger, more resilient product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Sv6F8x80KKCcjLiwl_6sw.png" /><figcaption>Making accessibility a priority and a core functionality across teams is key.</figcaption></figure><h3>QA &amp; Testers, Catch What Others Miss</h3><p>Accessibility issues can hide in plain sight and that makes testing essential. And not just for catching bugs, but for making sure real people can actually use what’s been built. Can a screen reader navigate it? Can a user complete a specific flow using only a keyboard? QA teams who look for these answers matter greatly because they can save users from frustration on the one hand and save teams from costly rework later on the other.</p><h3>Writers &amp; Content Designers, Make Language Inclusive Too</h3><p>Words shape experience together with design decisions. Clear, human-centered language supports all kinds of cognitive needs and learning styles. Well-written alt text, helpful link labels, and clear headings all play a role in building accessible content, complementing design in the most comprehensive way possible. When you write for understanding, you write for everyone. Claim it, relentlessly.</p><h3>Leaders &amp; Managers, Model What Matters</h3><p>Without leadership support, accessibility efforts fade. Time, training, tooling, and budget all depend on leaders who back their teams and prioritize inclusive work. When managers care about accessibility, teams make it part of the process. When they don’t, it falls through the cracks. It’s just the way things are and, since it’s a fact, make sure to fully support your team in their accessibility endeavors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lso5djHFLpvegc3Y9OiOaw.jpeg" /><figcaption>Building better products for more people only works when everyone takes ownership.</figcaption></figure><h3>So… Who Owns Accessibility?</h3><p>It’s an important question, for sure. And the answer is extremely straightforward: we all do. It’s not a single person’s job. It’s not something to <em>tackle</em> later on. Teams that share the responsibility build better products for more people. And often, <a href="https://medium.com/@arasdigital/accessibility-is-good-ux-for-everyone-6875c64fd13b">when you design for the edges</a>, you improve the experience for everyone in the middle too. Keep this in mind as you go.</p><h3>It’s All About People, Not Just Compliance</h3><p>Beyond <a href="https://medium.com/@arasdigital/a-simple-take-on-wcag-eaa-rules-e7c12f4d62d7">compliance</a>, accessibility is about making sure real people with all kinds of abilities, contexts, and challenges can fully use and enjoy digital products. It’s more than good design or good business. It’s actually basic respect. And it only works when everyone takes ownership.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c113bc13b7f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/who-owns-accessibility-5c113bc13b7f">Who Owns Accessibility?</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility as a Business Advantage]]></title>
            <link>https://medium.com/arasdigitalproducts/accessibility-as-a-business-advantage-bdffc456c3ab?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/bdffc456c3ab</guid>
            <category><![CDATA[accessible-design]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[cost-optimization]]></category>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Aras™ Digital Products]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 10:25:11 GMT</pubDate>
            <atom:updated>2025-07-31T13:25:08.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*76Dqpnm4JNG-wr-QoAV1Cg.png" /><figcaption>Accessibility is a strategic advantage.</figcaption></figure><p>We’ve already discussed accessibility simply being <a href="https://medium.com/@arasdigital/accessibility-is-good-ux-for-everyone-6875c64fd13b">good UX</a>, seeing how designing for edge cases means designing for everyone. But now it’s time to stress the importance of accessibility for businesses. As a strategic advantage, businesses that invest in accessibility build trust that lasts, while staying ahead and ranking higher.</p><h3><strong>Accessibility Translates to Cost-Efficiency</strong></h3><p>Maybe you’re still not aware of the fact that accessibility lawsuits are real and very expensive. Consider <a href="https://www.lflegal.com/2021/06/dominos-june-2021/#article-updates">the Domino’s Pizza case</a>, where the company was sued for not having an accessible website. Legal fees aside, the reputational hit was significant. Retrofitting an inaccessible product can cost up to 100x more than getting it right from the start. Thus, making an accessible product from the get-go is much cheaper than fighting legal battles later (in 2023, <a href="https://www.adatitleiii.com/2024/01/plaintiffs-filed-more-than-8200-ada-title-iii-federal-lawsuits-in-2023/">over 8,200 ADA Title III</a> Federal lawsuits were filed in the US alone). Moreover, if you stay ahead of <a href="https://medium.com/@arasdigital/a-simple-take-on-wcag-eaa-rules-e7c12f4d62d7">regulations</a>, you’ll be more at ease once new rules drop. It’s as simple as that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dD8l6q9V8onTWuI3N9Rblw.png" /><figcaption>Staying ahead of regulations is both smart and cost-efficient.</figcaption></figure><p>To ace this part, it’s really important to embed accessibility in your digital experience from the very beginning. This actually costs less than fixing things after launch. Also, you will save a serious amount of time and money thanks to fewer support tickets, clearer UX, and smoother upgrades. If you’re wondering who owns accessibility, we’ve got that covered, too. Find your answer <a href="https://medium.com/@arasdigital/who-owns-accessibility-5c113bc13b7f">here</a>.</p><h3><strong>What About Branding and SEO?</strong></h3><p>Brands that care about accessibility really demonstrate that they see everyone. More than just good PR and reputation, it ensures your customers stay loyal longer since you chose to include them instead of ignoring them. When customers see themselves reflected in your product, they remember. Accessibility sends a welcoming message that builds emotional loyalty money can’t buy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3H6HpVFqw0xvKK46E2RnA.png" /><figcaption>Accessibility contributes to brand loyalty.</figcaption></figure><p>Additionally, there are SEO advantages that shouldn’t be overlooked. Fast-loading, keyboard-navigable sites rank higher in Core Web Vitals and proper use of headings, alt text, and labels boosts snippet accuracy too. Just like people, search engines prefer clean and well-organized content. Better usability means longer visits and lower bounce rates. That’s SEO gold you can find and cash in on simply by making your product accessible.</p><h3><strong>Resilience Through Inclusive Design</strong></h3><p>When you build with accessibility from day one, adapting to new technologies is much faster. Remember how curb cuts, originally designed for wheelchairs, turned out to benefit delivery carts, strollers, and travelers with luggage? The same is true in tech: accessible design often becomes universal design. Thanks to inclusive design, your product will be ready for what’s next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aVWeZV4pFMkyzSbXszJVqg.png" /><figcaption>Accessible design often becomes universal design.</figcaption></figure><p>Accessibility doesn’t slow you down. Rather, it sets you up to grow faster, reach further, and adapt more easily. It’s the smart thing to do for trust, innovation, and long-term resilience. Start early, stay committed, and build for everyone. Both your customers and your future will thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdffc456c3ab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/accessibility-as-a-business-advantage-bdffc456c3ab">Accessibility as a Business Advantage</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real-Life Magic in the Making: Meet the Apple Vision Pro]]></title>
            <link>https://medium.com/arasdigitalproducts/real-life-magic-in-the-making-meet-the-apple-vision-pro-2abf0331729d?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/2abf0331729d</guid>
            <category><![CDATA[apple-vision-pro]]></category>
            <category><![CDATA[visionos-app-development]]></category>
            <dc:creator><![CDATA[Marko Aras]]></dc:creator>
            <pubDate>Thu, 29 Feb 2024 20:43:58 GMT</pubDate>
            <atom:updated>2024-03-01T09:36:59.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GY9s1cTUnNDGcrCdaN4bCA.png" /></figure><p>The long-awaited spatial computer that seamlessly blends digital content and apps into physical space, enabling eyes, hands, and voice navigation, is finally here. And when we say here, we mean in our very own hands. We are so excited to use this revolutionary product, but we are even more excited about the opportunities that come with it.</p><p><strong>Features of the Future</strong></p><p>We’ll single out only some of them, not to overload you with the product details that Apple so beautifully outlined <a href="https://www.apple.com/apple-vision-pro/">here</a>. Building on the existing macOS, iOS, and iPadOS, the visionOS enables spatial experiences. This fantastic new computer provides you with an infinite canvas where you can move, arrange, and scale your apps to create a workplace you’ve always dreamed about while still staying present in the world surrounding you. The Apple Vision Pro camera is something else: it’s the first 3D camera from Apple, making spatial photos and spatial audio a reality. In addition, the Vision Pro offers more pixels than a 4K TV for each eye, so any space you’re in transforms into a personal theater to enjoy your video and audio content in the most magical way possible.<br> <br>According to <a href="https://www.forbes.com/sites/timbajarin/2023/08/29/how-long-has-apple-been-working-on-its-vision-pro-headset/">Forbes</a>, the first patent related to the technology used in Apple Vision Pro dates back to 2007, when the iPhone was introduced. In particular, it was a patent related to a head-mounted display, as <a href="https://www.patentlyapple.com/2023/08/apple-won-a-patent-today-covering-their-original-apple-vision-related-invention-dating-back-to-2007-the-year-of-the-iphone.html">Patently Apple</a> reports: Using one or more optical and digital components, the personal display device may adjust displayed media to overlay features of a theater, stadium, or concert facility, thus giving the user of the individual display device the impression of being in the facility. Since Apple Vision Pro has been in the works for well over a decade, dare we think what Apple might have in store for us for the next couple of decades? Whatever it may be, we’ll be ready for it just like we’re ready for this fantastic new spatial computer today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-VPT8jqFggXirS40yfqpEg.png" /></figure><p><strong>Creating New Realities with visionOS</strong></p><p>Our team couldn’t wait to get their hands on the <a href="https://support.apple.com/en-gb/guide/apple-vision-pro/tan39b6bab8f/1.0/visionos/1.0">Vision Pro</a>, but they are also more than ready to start building apps for it, considering the fantastic new features we now finally have a chance to use, explore, review, and build on. In addition, reimagining our client’s needs in the context of spatial computing is something that we’ve been looking forward to for a long time now, and it’s definitely a pathway for our clients to gain the upper hand.</p><p><em>At Aras™️ Digital Products, we don’t just peek into the future; we sculpt it. Our vision extends beyond screens and pixels — it dances in the ethereal glow of spatial computing. Imagine a symphony of code and light orchestrated by the Apple Vision Pro, our cosmic wand. This isn’t mere technology; it’s alchemy. With every line of code, we weave immersive tapestries that whisk our users across time and space. <br>Remember those dusty reels of old HNK Hajduk matches? Well, now you’re not just a spectator; you’re a time-traveling aficionado, reliving the crowd’s roar and the thrill of victory. And bathrooms? Oh, they’re no longer mundane. With a dash of spatial magic, you’ll design your Kohler sanctuary — a fusion of elegance and functionality. The tiles align, the faucets hum, and the mirror winks at your reflection, whispering secrets of serenity. But wait, there’s more. Buckle up because you’re about to test-drive a Porsche — not on asphalt, but in the nebulous expanse of our digital realm. Feel the purr of the engine, the wind tousling your virtual hair, and the thrill of acceleration. And when you step out, you’ll carry that exhilaration into the real world.<br>At Aras™️ Digital Products, we don’t ask what kind of app you need; we ask what universe you want to inhabit. The Apple Vision Pro is our stardust, and we’re here to make your cosmic dreams a pixel-perfect reality</em>. <br>– William Sullivan, Business Development, Aras™️ Digital Products</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1775pQWQ-5pRukBRa8SLMg.png" /></figure><p><strong>Reimagining Art</strong></p><p><em>The visionOS offers tremendous potential when it comes to every aspect of art. And that is where we step in to shape the future: we want to explore and build on the space in which art and technology meet, where they co-exist, intertwine, and blend. If you are an artist with ideas that go along these lines, you have to let us know so that we can start creating something fantastic together and make the most of the spatial computing era.</em></p><p><em>It will be exciting to see creativity and cutting edge technology come together with Apple Vision Pro. We passionately believe that uniting art and technology is a path to greatness and we are ready to take it. Our commitment to innovation is an important part of our work which keeps our imagination going, allowing us to see no boundaries when it comes to design and development.</em> <br>- Ivan Aras, Head of Design at Aras™ Digital Products</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZkdUfjpBWos_vXf9KbcrA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2abf0331729d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/real-life-magic-in-the-making-meet-the-apple-vision-pro-2abf0331729d">Real-Life Magic in the Making: Meet the Apple Vision Pro</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing MVVM with RxSwift code]]></title>
            <link>https://medium.com/arasdigitalproducts/testing-mvvm-with-rxswift-code-2f99ededea63?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/2f99ededea63</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[rxswift]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Marko Aras]]></dc:creator>
            <pubDate>Tue, 27 Jun 2023 11:23:03 GMT</pubDate>
            <atom:updated>2021-06-29T07:27:14.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBTVVbEqaFN-RbkECTs3JQ.png" /></figure><p>I don’t wanna waste your time explaining why writing tests is important since I suppose you already know enough about this if you came across this article.</p><p>I recommend reading the chapter about testing from Uncle Bobs <em>Clean Code</em> where he explains why is testing important in his own way, and why is it important to keep tests clean. He also explains five rules called F.I.R.S.T. in a bit more details. Let’s just keep in mind that test should be<strong> Fast, Independent, Repeatable, Self Validating, Timely.</strong></p><p>We are using MVVM architecture, and you can read more about it in my <a href="http://arsfutura.co/magazine/mvvm-with-rxswift/">blog post</a>.</p><p>There are many different types of testing but this article is going to focus on the <strong>unit</strong> and <strong>integration</strong> tests.</p><h3>My experience: <strong>How writing tests made me a better developer</strong></h3><p>You can absolutely skip this chapter if you are here just for the code or you want to see the way we implemented tests with RxSwift. I won’t even be mad, I just want to share my story about getting into writing tests and why it was useful to me.</p><p>I’m not ashamed to admit that this was my first big project where we decided that we are going to write tests. In the college, there were at least five courses where I was learning about the importance of testing, rules, benefits, etc., but I never fully understood how powerful testing can be. I even wrote tests for the several college projects but I was always writing them with just making them pass in mind, never have I thought about benefiting from them. They were there just so I can say “I’m writing test“ to make me look like a better developer or to meet the project requirements. How young and naive was I? And that was not that long ago.</p><p>With getting the new project we decided that this will be the project where we as a team want to take our skills to the new level, with great code coverage, unit, integration, and UI test, and same dedication for tests as for code, architecture, and design.</p><h4>Writing first tests</h4><p>So a decision was made and the time has come to start writing tests. We are not doing Test Driven Development so what I tried to do is write tests for the Login feature that I was working on already. The feature was almost done and I wanted to write tests for it to make sure if anything changes in the future, the changes don’t break anything, and if they do, to pinpoint to what is broken. Figuring out why would be much easier then.</p><ul><li>First time I created a new test class in the project using RxSwift I was pretty confused. I wanted to test observables in the view model, but I had no idea how to do it, how to make it a unit and not an integration test, how to simulate events from view controller etc.</li></ul><p>I tried to write <strong>unit tests</strong> for <strong>LoginViewModel</strong>. Let’s see what this means.</p><ul><li><strong>Unit tests</strong> — the lowest level of software testing where individual components — <strong>units </strong>are being tested. In this case, our unit is LoginViewModel, and writing tests for this unit mean that all the dependencies must be mocked and all the tests must depend <strong>only </strong>on LoginViewModel code.</li><li>What that means in our MVVM architecture is that we want to tests each layer and every component for itself. So each ViewController, ViewModel , and Model has to have its own tests. For each component in our architecture, we need to have an associated test suite. Basically, you want to isolate and test each of your classes separately. All the services, managers etc. should be tested on its own, and have mocks that can be injected into the class that is using them.</li><li>My LoginViewModel was depending on the few classes, like NetworkingService and ValidationService. Something like this.</li></ul><pre>class LoginViewModel {<br>    private let networkingService = NetworkingService()<br>    private let validationService = ValidationService()<br>    <br>    ...</pre><pre>}</pre><ul><li>Looking at the code above makes me sick in the stomach now, because this code is hardly reusable or testable. How do you write mocks for these dependencies? The answer is <strong>protocols </strong>and<strong> dependency injection</strong>!</li></ul><pre>class LoginViewModel {<br>    private let networkingService: NetworkingServiceProtocol<br>    private let validationService: ValidationServiceProtocol<br>    <br>    init(networkingService: NetworkingServiceProtocol,<br>         validationService: ValidationServiceProtocol) {</pre><pre>        self.networkingService = networkingService<br>        self.validationService = validationService<br>    }<br>    <br>    ...</pre><pre>}</pre><p>Swapping concrete implementations with interfaces allows us to write mocks much easier. Our mocks now just have to implement these protocols and we can do that with ease. And we no longer depend on the implementation of these services in our tests and now these tests can be called <strong>unit</strong> tests.</p><p>Once I wrote all the unit tests I start writing <strong>integration tests</strong> to see if different parts of the system work as they should when they interact with each other.</p><p><strong>Integration tests</strong> — the next level of software testing after unit testing, This is the place where you want to test the interaction between integrated components in your system. Take ViewController and ViewModel for example. After we wrote isolated tests for SomeViewController, and for SomeViewModel, we need to test do these components work as they should once they interact with each other. This interaction in our MVVM architecture is implemented using RxSwift.</p><p>Writing integration tests now should be easy, like playing with legos, since you just connect components that you want to connect and use mocks for the others.</p><p>We have testers dedicated to writing UI tests using Appium so I’m not going to write about that since I have very basic knowledge of this.</p><h3>Testing Rx code</h3><p>When we started writing tests for our architecture we got stuck immediately, and the reason for this were <strong>bindings</strong> of <em>View Controllers</em> and <em>View Models. </em>The way we used to implement these bindings is that we would initialize View Model with Observables we needed to handle, or we would just assign them along the way, something like this:</p><pre>class SomeViewModel {<br>    var counter: Driver&lt;String&gt;!</pre><pre>    init(increaseCounterTaps: Observable&lt;Void&gt;) {<br>        counter = increaseCounterTaps<br>            .flatMap<br>            ...<br>    }</pre><pre>}</pre><p>or like this:</p><pre>class SomeViewModel {<br>    var counter: Driver&lt;String&gt;!</pre><pre>    func setupIncreaseTaps(increaseCounterTaps: Observable&lt;Void&gt;) {<br>        counter = increaseCounterTaps<br>            .flatMap<br>            ...<br>    }</pre><pre>}</pre><p>Soon we figured out that it was a nightmare to write tests for something like this. A solution we came up with was to switch from Observables to PublishSubject since it is much easier to simulate event on PublishSubject as all you have to do is:</p><pre>let somePublishSubject = PublishSubject&lt;Bool&gt;()<br>somePublishSubject.onNext(true)</pre><p>Also, this allows us to just bind events from the View Controller to View Model, and we are still using Observables in View Model for events that View Controller can subscribe on.</p><h3>Example</h3><p>Let’s pretend we have a View Controller that shows one label with counter value and one button to increase that value. View Model is responsible for handling each tap, increasing the counter and letting View Controller know that label should be updated and what it should be updated with. Also, we are going to write unit tests for both, and integration test to make sure these two together are working as they should.</p><p>Download <a href="https://github.com/arasmarko/testing-mvvm-rx">example repo</a> and check it out so you can follow along easier.</p><p><em>testIncreaseButtonTaps_WithOneTapEvent_LabelTextShouldBeOne </em>method in <em>CounterViewModelTests </em>is the best example of simulating events from View Controller<em>.</em></p><pre>func testIncreaseButtonTaps_WithOneTapEvent_LabelTextShouldBeOne() {</pre><pre>    let observer: TestableObserver&lt;String&gt; = scheduler.createObserver(String.self)</pre><pre>    let correctResult: [Recorded&lt;Event&lt;String&gt;&gt;] = [next(0, &quot;0&quot;), next(1, &quot;1&quot;)]</pre><pre>    sut.counterValue<br>        .subscribe(observer)<br>        .disposed(by: disposeBag)</pre><pre>    let allEvents = scheduler.createHotObservable([next(1, ())])</pre><pre>    allEvents<br>        .bind(to: sut.increaseButtonTaps)<br>        .disposed(by: disposeBag)</pre><pre>    scheduler.start()<br>    XCTAssertEqual(correctResult, observer.events)</pre><pre>}</pre><p>Here we are creating <em>TestableObserver </em>that we are going to use to compare with some result of type <em>[Recorded&lt;Event&lt;String&gt;&gt;]. </em>Next thing we have to do is simulate some events, and we have to do it at exact time.</p><p>As you can see, we are simulating a new tap event at timestamp 1. The expected result is the label to have text “0” at the start and text “1” after the simulated tap. Run tests and check if everything is passing.</p><p>Check out <em>CounterViewControllerTests </em>to see how easy it is to inject <em>Mock </em>of a View Model.</p><p>Also look at integration tests for this screen to see the way I implemented it.</p><p>Thank you for your attention and please let me know if you have a better solution for anything above.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f99ededea63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/testing-mvvm-with-rxswift-code-2f99ededea63">Testing MVVM with RxSwift code</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a custom keyboard for sharing custom content in chat applications]]></title>
            <link>https://medium.com/arasdigitalproducts/creating-a-custom-keyboard-for-sharing-custom-content-in-chat-applications-6fa605db9b05?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/6fa605db9b05</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[anroid-app-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Domagoj Kolega]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 13:42:36 GMT</pubDate>
            <atom:updated>2022-12-06T13:42:36.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ifJAjia8iedW8FTrJZhpg.png" /></figure><h3>Introduction</h3><p>Are you building an app for sharing custom content to chat applications? Then you are in the right place because in this tutorial we will show how to create a custom Android keyboard that supports sending custom-rich content such as images, videos, sounds, gifs, etc. Custom soft keyboard, such as the one you will make with the help of this tutorial, can be used in every application where data, other than text, can be shared. The best example of such a keyboard is the Giphy keyboard.</p><p>In this tutorial, we will build a custom keyboard for sharing animal pictures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*y5a8DVB96Bq5jQzrIE0kwQ.gif" /></figure><h3>Step 0: Getting started</h3><p>Soft keyboard is an input method meaning that it opens when an <em>EditText</em> comes in focus and provides content that’s inserted into the <em>EditText</em>. However, input fields of most chat applications support only simple mime-types, such as image/jpeg and image/gif. Supported mime types for text fields can be found with this line of code:</p><pre>val supportedMimeTypes: Array&lt;String&gt; = EditorInfoCompat.getContentMimeTypes(editorInfo)</pre><p>To get around that, we are going to share content with an <a href="https://developer.android.com/reference/android/content/Intent"><em>Intent</em></a><em>.</em></p><p>Basically, we are building a<em> </em><a href="https://developer.android.com/reference/android/app/Service"><em>Service</em></a>. According to the official Android documentation, it represents an application component representing either an application’s desire to perform a longer-running operation while not interacting with the user or to supply functionality for other applications to use — we will be using the latter. Since our app will provide the keyboard to other applications, our service class will extend <a href="https://developer.android.com/reference/android/inputmethodservice/InputMethodService"><em>InputMethodService</em></a>, a subclass of a <em>Service</em>. Before we start coding the input method service, we need to add an<em> &lt;service&gt;</em> entry in <em>AndroidManifest.xml</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c57f70b2660945d2467d43e0d4837cc5/href">https://medium.com/media/c57f70b2660945d2467d43e0d4837cc5/href</a></iframe><p>In order to enable our device to recognize our service as an input method, it is necessary to add the meta-data tag and set the resource attribute to @xml/method (even though that file is empty), because the meta-data tag won’t work without that attribute set.</p><p>For <em>android:name</em> attribute, you need to set a fully-qualified name of your implementation of InputMethodService, in this case, that is <em>studio.codable.customkeyboard.CustomKeyboardInputService. No need to worry about spelling, </em>the Android Studio will auto-complete it for you. :)</p><p>Other interesting attributes are <em>android:label</em> and <em>android:permission</em>. The label represents the name of your keyboard, which will be displayed in the input method chooser, and the permission is the permission that we need for our service, in this case, for the bind input method.</p><h3>Step 1: Set up the layouts</h3><p>Talking about the UI, we will create two layout files: one for the keyboard and for the animal list item.</p><p>The keyboard layout is placed in<em> the custom_keyboard.xml:</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2e8e6e180892af3558ea4a765d17952b/href">https://medium.com/media/2e8e6e180892af3558ea4a765d17952b/href</a></iframe><p>While the animal list is loading, a progress bar will be displayed for a better user experience.</p><p>The layout for the list item used in the <em>RecyclerView</em> is placed in <em>custom_keyboard_item.xml</em>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b02e1ff75ed141f97a18013fe11d727/href">https://medium.com/media/2b02e1ff75ed141f97a18013fe11d727/href</a></iframe><h3>Step 2: Adding the adapter</h3><p>Since we are using a <em>RecyclerView</em> for displaying the animal list, we will need an adapter. So we will create a <em>CustomKeyboardAdapter</em> for inflating recycler view items and handling click events on those items.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/871e4c7ebef668d12dc8ab0c3deebd84/href">https://medium.com/media/871e4c7ebef668d12dc8ab0c3deebd84/href</a></iframe><blockquote>If you had any problems inflating <em>CustomKeyboardItem</em>, as I had, make sure that you set <em>android:theme</em> attribute of the <em>MaterialCardView</em> to the theme of your application.</blockquote><h3>Step 3: DataManager</h3><p><em>DataManager</em> is a class that helps us work with raw data, and here the raw data are images. I would say that this class is the heart of how this custom keyboard works. We are working with sharing files and <em>DataManager</em> is a class that has methods for data management. <em>DataManager</em> has two methods: <em>shareAnimal</em> and <em>getKeyboardSharingIntent</em>.</p><p><em>ShareAnimal</em> is a method that downloads a certain file or takes it from cache if it’s been previously downloaded. Then, it returns the file through a callback function.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/07be852fadfc56e55337eb171f0268e1/href">https://medium.com/media/07be852fadfc56e55337eb171f0268e1/href</a></iframe><p><em>GetKeyboardSharingIntent</em> is a method that creates an URI from the provided image file and passes it to a newly created Intent, which this method then returns.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b10407f046757ff75407abb45b825e97/href">https://medium.com/media/b10407f046757ff75407abb45b825e97/href</a></iframe><h3>Step 4: CustomKeyboardInputService</h3><p><em>CustomKeyboardInputService</em> is an implementation of <em>InputMethodService</em>.</p><p><em>InputMethodService</em> provides a standard implementation of an <a href="https://developer.android.com/reference/android/view/inputmethod/InputMethod"><em>InputMethod</em></a>, which final implementations can extend and customize its functionality. Also, even though it is a service, it has a user interface. In addition to the usual <em>Service</em> lifecycle methods, this class introduces some new, specific callbacks which we will use: <em>onCreateInputView</em> and <em>onStartInputView</em>. We use them to inflate <em>CustomKeyboardLayout</em> and to set everything up, respectively.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb4e49a6d2243a613760629da5513eca/href">https://medium.com/media/cb4e49a6d2243a613760629da5513eca/href</a></iframe><p>For handling animal list item clicks, we will create the: <em>startShareActivity </em>function. First, we call the <em>shareAnimal method </em>from <em>DataManager</em>, and then, with the resulting file, we invoke <em>getKeyboardSharingIntent</em> which will then return an Intent that will be used to start an activity.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/69268bfadd6cca68f4c75c3764828a42/href">https://medium.com/media/69268bfadd6cca68f4c75c3764828a42/href</a></iframe><p>Except for that, <em>startShareActivity</em>, after the intent is started, switches the keyboard to the previous input method.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ad6bfe897760d6b93b73d60efe956b1/href">https://medium.com/media/3ad6bfe897760d6b93b73d60efe956b1/href</a></iframe><p>And look what we created:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*SWuv-jwA77-CxXUfNbbgtA.gif" /></figure><h3>Step 5: Choosing the input method</h3><p>This keyboard has a little keyboard icon in the top right, if you click it, this will show up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*tbb6jnvzpMmbNJ_YlnYDdg.jpeg" /></figure><p>It is an input method chooser, where you can choose between all input methods that your device currently has installed.</p><p>It is also worth mentioning that some devices natively put the input method chooser somewhere on the screen, but some don’t so it’s our job to ensure that users can switch the keyboard if they decide not to share custom data.</p><p>Since we are not using regular content committing, but rather sending an intent to the application which opened the keyboard, we experience different behaviour across different chat applications. For example, <em>Whatsapp</em> or Facebook <em>Messenger</em> will show you a default screen for sharing something in that application, and Slack will also open a default screen for sharing, but it will then recognize that you want to share that content where the current edit text is and it will set that content there.</p><h3>Conclusion</h3><p>In this tutorial you made a custom keyboard for sharing animal images in chat applications.</p><p>Congratulations!</p><p>If you are interested more in our work and what we do, go check out or <a href="https://codable.studio/">website</a>!</p><p>Link for Github project: <a href="https://github.com/kolegad/custom-keyboard">https://github.com/kolegad/custom-keyboard</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fa605db9b05" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/creating-a-custom-keyboard-for-sharing-custom-content-in-chat-applications-6fa605db9b05">Creating a custom keyboard for sharing custom content in chat applications</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making your life easier with Xcode shortcuts, snippets and templates]]></title>
            <link>https://medium.com/arasdigitalproducts/making-your-life-easier-with-xcode-shortcuts-snippets-and-templates-9f44496a67b1?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/9f44496a67b1</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-development]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[xcode]]></category>
            <dc:creator><![CDATA[Marko Benacic]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 13:41:49 GMT</pubDate>
            <atom:updated>2022-12-06T13:41:49.066Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cjm1LJFt0sDnUnUgfwCumQ.png" /></figure><h3>Making your life easier with Xcode snippets, shortcuts, and templates</h3><h4>Tips and tricks to make you a more productive iOS developer — Part 1</h4><p>Typing a lot of code and smashing that mechanical keyboard a bunch surely can be satisfying. But at the same time, we can all agree that writing boilerplate code takes up a big chunk of our precious time. Since every self-respecting developer strives to be as efficient as possible, it is important to master the tools provided by Apple’s <em>Xcode</em> if you wish to take your productivity to the next level.</p><p>This article is part 1 of a three-part series about X<em>code’s</em> snippets, shortcuts, and templates. <a href="https://medium.com/codablestudio">Part 2<strong> </strong>— <em>Xcode </em>Shortcuts</a> and <a href="https://medium.com/codablestudio">part 3 — <em>Xcode </em>Templates</a> are coming soon so make sure to come back and check on them!</p><h3>#Snippets</h3><p>Snippets are X<em>code’s</em> tool used for creating templates of frequently used boilerplate code. You have probably been using snippets without even knowing about them! For example, if you start typing func, you will see a suggestion like the one in the picture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/0*QrwCMyy1nUqDZWV2" /></figure><p>If you then proceed to hit <strong>enter</strong>, X<em>code</em> will generate a skeleton where you can easily input function name, parameters, return type, and a function body. Once you’ve filled in a field (also known as<em> placeholder token)</em>, you can press <strong>tab</strong> to switch to another one like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*Tv0jAiWdvCF7jn_TE7EVpw.gif" /></figure><h3>#How to find snippets</h3><p>You can find available snippets in 3 ways:</p><ul><li>Using the keyboard shortcut command (<strong>⌘</strong>) + shift(<strong>⇧</strong>) + L</li><li>Using the bar menu on the top: <strong>View -&gt; Show library</strong></li><li>Pressing the + button at the top right</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/231/0*w6rjS_V-8TU8G3ep" /><figcaption>Open snippets button</figcaption></figure><p>After you’ve found the one you want to use, you can press <strong>enter</strong> or drag and drop it into your code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*-j_KuUIZd8jaGYMVOVpKhQ.gif" /></figure><p>There are many useful predetermined snippets already included such as <em>docatch, guardlet, ifelse, available</em>,<em> </em>etc. Feel free to look around the library and try incorporating the ones you think would be the most useful to you.</p><h3>#Adding your own snippet</h3><p>Here comes the useful part. Let’s say you’re writing a lot of closures that are using references to <strong>self</strong>. One way of avoiding <a href="https://www.swiftbysundell.com/questions/is-weak-self-always-required/">retain cycles</a> is by using [weak self]. If we then wish to use that <em>self</em> reference in our closure, we must first make sure the reference even exists (that it is not <strong>nil</strong>). One way of doing that is by using guard: guard let self = self else { return }.</p><p>Here’s an example:</p><pre><strong>class</strong> ViewController: UIViewController {</pre><pre><strong>   private</strong> <strong>var</strong> someText: String = &quot;Peanut butter&quot;</pre><pre><strong>   override</strong> <strong>func</strong> viewDidLoad() {<br><strong>      super</strong>.viewDidLoad()<br>      <br>      <strong>let</strong> someClosure = { [<strong>weak</strong> <strong>self</strong>] <strong>in<br>         guard</strong> <strong>let</strong> self = <strong>self</strong> <strong>else</strong> { <strong>return</strong> }<br>         self.someText = &quot;bananas&quot;<br>      }<br>      print(someText)<br>      someClosure()<br>      print(someText)<br>   }</pre><pre>}</pre><p>Output:</p><pre>Peanut butter<br>Bananas</pre><p>Since we are probably going to repeat those two little lines of code lots of times throughout our apps, let’s create two snippets for them:</p><p>Highlight [weak self]with your mouse -&gt; <strong>right click</strong> -&gt; <strong>Create code snippet</strong>.</p><p>Change the title to <em>Weak self</em> and in completion write “ws” like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*_E_6LYlMZApODIruc_omwQ.png" /></figure><p>There are some other options to set for our snippet such as changing the preferred language (any language that is supported by X<em>code</em>), platform (iOS, macOS, tvOS, watchOS, or All), and scope availability, as well. Feel free to test them out!</p><p>If we now proceed to write our shortcut (in this case “ws”), code completion will keep suggesting our snippet and pressing <strong>enter</strong> will write it out for us. Now we do the same procedure for the next line of code containing <strong>guard let self</strong>.</p><p>Using our newly created snippets should look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*H8__w4He2uXcVozSsHmvOg.gif" /></figure><p>Wow! That was fast!!</p><h3>#Placeholder tokens</h3><p>I often use mark comments (and so should you!) to help me read through my code better.</p><p>To create a mark comment snippet with a <em>placeholder token </em>just type your placeholder name (eg. <em>content</em>) between &lt;# and #&gt; in your code, and create a snippet as shown above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/514/1*DXQ2PEPhPtQtJ5bYB4OoAg.gif" /></figure><h3>#Sharing your snippets</h3><p>What if you want to share your super cool snippet with a friend? All of your snippets are located at ~/Library/Developer/Xcode/UserData/CodeSnippets. They are saved as <em>plist</em> file format and you can copy and paste them directly into the CodeSnippets folder at the file path shown above. Unfortunately, they are given a random UUID name, but you can simply open them with a text editor to find the one you want to share.</p><h3>#That’s all…</h3><p>Congrats! You’ve successfully created your first code snippet and made yourself a more efficient iOS developer!</p><p>In the next part of this mini-series, we will share more about using the best <a href="https://medium.com/codablestudio"><em>Xcode </em>shortcuts that can help you become an even more efficient iOS developer</a>.</p><p>If you liked this article, check out our <a href="https://codable.studio/">website</a> for more content!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f44496a67b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/making-your-life-easier-with-xcode-shortcuts-snippets-and-templates-9f44496a67b1">Making your life easier with Xcode shortcuts, snippets and templates</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Screenshots automation for iOS with Bitrise & Fastlane]]></title>
            <link>https://medium.com/arasdigitalproducts/screenshots-automation-for-ios-with-bitrise-fastlane-5899eeb3d6b?source=rss----f171b2c44fe7---4</link>
            <guid isPermaLink="false">https://medium.com/p/5899eeb3d6b</guid>
            <category><![CDATA[fastlane]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[screenshots]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[bitrise]]></category>
            <dc:creator><![CDATA[Marko Aras]]></dc:creator>
            <pubDate>Fri, 17 Apr 2020 09:20:32 GMT</pubDate>
            <atom:updated>2022-01-20T09:13:59.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04zvAMwXKFvctzA1n7g66Q.png" /></figure><h3>Screenshot automation on iOS with Bitrise &amp; Fastlane</h3><p>Screenshot automation is an important feature if you need to make sure everything is displayed properly on all the variations of languages and screen sizes. This can save you a huge amount of time testing all these cases.<br>I spent some time trying to find the best tool to do this and since I’m using Bitrise for CI/CD I wanted to keep everything in the same channel.</p><p>For running UI Tests on real devices, I’m using Firebase Test Lab, but it doesn’t support making screenshots for iOS (for Android apps FTL is a good solution).</p><p>I’m going to use the iOS project named <em>ScreenshotAutomation</em> with UITests included for this example and a new Bitrise project named <em>ScreenshotAutomation</em>.</p><h3>Fastlane</h3><p>The first step we need to do is add the Fastlane to this project and set it up for making screenshots.</p><p>Make sure you have the <a href="https://docs.fastlane.tools/getting-started/ios/setup/">Fastlane installed</a> and in the terminal just run `<em>fastlane</em>` in the project root folder.</p><p>This will start to configure Fastlane for your project, you just have to follow the steps provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*HBI4zZuDX9CZtrs9DXdb9g.png" /><figcaption>Fastlane setup</figcaption></figure><p>Don’t forget to <a href="https://www.talentica.com/blogs/ios-build-management-using-custom-build-scheme/">create a new Schema</a> and mark it as <em>Shared</em>. I named it <em>FastlaneScreenshotAutomation</em>.</p><blockquote>Your project should look like this</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D_AsDoOPywXYVyx4OxbVYw.png" /><figcaption>Project layout</figcaption></figure><p>Now you can continue with Fastlane setup. Select the new schema you created.</p><p>I’m not going to use these screenshots for App Store Connect so I’ll skip this step.</p><p>This will create a new <em>Fastlane</em> directory in your project. There are two here that we are going to need.</p><p><strong>Snapfile</strong> — configuration for our screenshots</p><p><strong>Fastfile</strong> — defines the <em>lanes</em> that Fastlane can use</p><p>In the Snapfile, I’m only going to set up the English language and a few screen sizes. However, this file allows for more configuration and I encourage you to check it out.</p><p>This is what my Snapfile and Fastfile look like</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/0*yGXAPHRNo8wJ8bgV" /><figcaption>Snapfile and Fastfile</figcaption></figure><p>You can always check available Lanes with `<em>fastlane lanes</em>` command and run the lane with `<em>fastlane [lane_name]</em>`. We have just one lane, named `<em>screenshots</em>` as you can see in the `<em>Fastfile`</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*BJM8xt7w-2YOoYLgIaNSxg.png" /><figcaption>Available lanes</figcaption></figure><p>Run this lane and it will create your first screenshots. Make sure your iOS version is properly set for <em>ScreenshotAutomationUITests</em> target (<em>Build Settings -&gt; iOS Deployment Target</em>) and that your Schema looks like this. Also, I opted out of using Scene Delegate since that can cause some problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ap3MmLy6W2nyt0m_6L3Xg.png" /><figcaption>Schema</figcaption></figure><p>This is our final result</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/0*eeDouYbBTBiOJFXd" /><figcaption>Screenshots directory</figcaption></figure><p>You can also add some more options to Snapfile. You can find the list of the options by running <em>fastlane action</em> <em>snapshot</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ZSoIvxAImRVGsM0y6JbDQQ.png" /><figcaption>Snapfile configuration</figcaption></figure><p>I suggest that you add screenshots directory to <em>.gitignore</em> as this is not something you would need in your repo.</p><h3>Bitrise</h3><p>For the Bitrise part, I created a new project, connected my <a href="https://github.com/arasmarko/ScreenshotAutomation">GitHub repo</a> (make sure you pushed all the changes from above).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eb0tyl8DciHaksri" /><figcaption>Project build configuration</figcaption></figure><p>You can skip adding the app icon and webhooks in project setup.</p><p>Now we have to create a workflow for screenshots on Bitrise. This should already be done by default and it should look like the image below. I also like to enable verbose logging on the fastlane step until I make sure everything is working fine. To make sure our screenshots are exported correctly we have to try out a build.</p><p>This should be in <strong>Build - Apps &amp; Artifacts</strong>. If you can’t find your screenshots make sure you add the correct <em>Input variables </em>in the <em>Deploy to Bitrise </em>step. I like to compress my artifacts so I set this to true. You can find the exact value for <em>Deploy directory or file path</em> by checking where your screenshots.html is stored in your build log. For me it us <em>/Users/vagrant/git/screenshots</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*-O3LYEOQz8-2DhTy21ud3A.png" /><figcaption>Deploy to Bitrise Step</figcaption></figure><p>In the end, it should look something like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*2wIQNUDEQpbsf_5_RUxGGw.png" /><figcaption>Final result</figcaption></figure><p>Your build will take some time, so be patient, but your final results will be worth it and this could save you quite some time in the future. You can also add triggers to this build whenever you want so make sure you investigate all that Bitrise offers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5899eeb3d6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/arasdigitalproducts/screenshots-automation-for-ios-with-bitrise-fastlane-5899eeb3d6b">Screenshots automation for iOS with Bitrise &amp; Fastlane</a> was originally published in <a href="https://medium.com/arasdigitalproducts">Aras™ Digital Products</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>