<?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[Mo Mozafarian - Medium]]></title>
        <description><![CDATA[Designer by trade. Hacker by night. Entrepreneur by passion. - Medium]]></description>
        <link>https://medium.com/momozafarian?source=rss----9008c021c768---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Mo Mozafarian - Medium</title>
            <link>https://medium.com/momozafarian?source=rss----9008c021c768---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:05:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/momozafarian" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing iXpand Base Mobile App]]></title>
            <link>https://medium.com/momozafarian/case-study-designing-sandisk-ixpand-base-mobile-app-7b72a9a44172?source=rss----9008c021c768---4</link>
            <guid isPermaLink="false">https://medium.com/p/7b72a9a44172</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Tue, 09 Jan 2018 17:01:25 GMT</pubDate>
            <atom:updated>2018-01-10T00:41:09.658Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rIPMvYCT3M1VNvFTwRMq5g.png" /></figure><h4>Case Study &amp; Design Process</h4><p>SanDisk iXpand Base charging device allows users to automatically back up their iPhone’s photos, videos, and contacts with each charging. The process is managed with an iOS mobile app, that I was lucky to work on as a designer. Here’s a brief case study of my design process as well as some of the challenges I faced on this project.</p><h3>Context</h3><p>Mobile data storage limitation is a common problem. There is just not enough space on our phones to store all the memories, photos and videos we take everyday. For many users, cloud-based services like iCloud, google photos and Dropbox solve that problem. But not everybody is a fan of cloud-based solutions. Whether it is the privacy concerns or a general preference of having a physical copy of your data, there seems to be a need for such solution.</p><h3>Challenges</h3><p>Most solutions in the data storage category are designed to backup/restore a specific type of content like Media (Photos &amp; Videos). However, with iXpand Base, we wanted to create a solution that would give users the ability to store all types of data such as contacts, health data, notes,… in addition to Media content.</p><p>This was a unique challenge given that different types of content require to be shown differently. This meant we needed to create dedicated views for each type of data.</p><p>We also wanted to make the process of restoring different data types as easy as possible and let users restore selective content in one take.</p><h3>Landscape Research</h3><p>To better understand the product category I started by studying competitors’ products in a typical landscape analysis. When done right this desk research tool help designers discover valuable category insights.</p><p>Some questions to ask when analyzing other products in the category:</p><ul><li>What is the problem these products are trying to solve? How are they solving it?</li><li>What makes the product I am working on unique and different from others and what makes them similar?</li><li>What are my specific design challenges/restrictions?</li></ul><p>Such structured approach to competition analysis helps avoid blindly copying others, and helps further clarify the problem specific to the product in hand.</p><h3>Design Considerations</h3><p>While the first version of the product had supports for media and contacts, we still needed to consider ways for adding new data types without making major changes to the flow.</p><p>Also, given the target group was characterized as less tech-savvy seniors, we wanted to keep the experience as close as possible to the general iOS UX patterns. Therefore removing the learning curve from the overall experience.</p><p>For the look and feel, the goal was to keep the visuals similar to the other SanDisk products yet different enough so the product would stand out.</p><h3>Design Process</h3><p>We started by exploring high-level user flows and trying to locate potential frictions in the overall experience using flow diagrams. This helped us to create a strong foundation around the user journey before getting into the details of how each view would be displayed and would function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*xFh-exUBVwpQAoyO_T1ppQ.png" /></figure><p>We then started to remove unnecessary screens from the flow to simplify the steps taken for key actions. This is a great exercise for creating intuitive user experiences (Explained in details on Linear UX).</p><p><a href="https://uxdesign.cc/linear-ux-ad7dc634b5b1">Linear UX</a></p><p>As a part of this process, we removed the dedicated section we had originally considered for notifications and used a custom overlay view instead. This way we would only show the notifications when needed and avoided having unnecessary empty state screens.</p><p>As a result of this design decision, we put a floating button for the notifications which would only appear when users needed to take actions.</p><p>Focusing on simplifying the product and removing unnecessary functionalities made the product more accessible and easier to use for less experienced users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/393/1*xar0l1eW0hgoMRDa49a1uQ.gif" /></figure><p>One other small and subtle detail was the color palette itself. Although we were restricted to use the specific colors provided in the Brand Guideline, we did make a small adjustment to the colors. That was to warm up the primary colours while keeping them close to the originals. The reason we did this was, in our research, it appeared the peak use of the app would be before sleep in a dark environment. Therefore, to avoid giving users restless eyes, we modified the colors slightly so they would appear warmer and give users a cozy feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EF6o9cUVHAKdwJ8Xv5qGfg.png" /><figcaption>Left: Provided colours. Right: Modified colours.</figcaption></figure><p>Here’s one of the prototype made using Principle. (The iOS app is also available on the App Store.)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F250280717&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F250280717&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F676330423_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/d941f6e668984e5c7263bc132dafbf65/href">https://medium.com/media/d941f6e668984e5c7263bc132dafbf65/href</a></iframe><h3>Side Notes</h3><p>When defining the main challenges, I had the opportunity to work closely with the stakeholders to scope out features and product specs. It is extremely important to keep an open line of communication to make sure visions are aligned, especially in the early days of the design process.</p><p>As a designer who works mostly remotely, a key part of my job is to create a process that facilitates and structures stakeholders-designer communications.</p><p>One great way to improve this is to provide clients with a visual user flow, instead of a list of written user scenarios. Unlike written scenarios, visual flowcharts show how users move throughout the entire experience and pinpoints UX flaws and shortcomings very early on.</p><p>This approach also helps keep the UX and UI conversations separate and brings the focus to the task at hand. Additionally, for engineers, user-flows are great starting points and allow them to draw up underlying IA and get started with coding the overall product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b72a9a44172" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momozafarian/case-study-designing-sandisk-ixpand-base-mobile-app-7b72a9a44172">Designing iXpand Base Mobile App</a> was originally published in <a href="https://medium.com/momozafarian">Mo Mozafarian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ProPosal — Design Process]]></title>
            <link>https://medium.com/momozafarian/proposal-design-process-9c64dc0a3f28?source=rss----9008c021c768---4</link>
            <guid isPermaLink="false">https://medium.com/p/9c64dc0a3f28</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Tue, 09 Jan 2018 15:13:15 GMT</pubDate>
            <atom:updated>2018-01-09T15:13:15.019Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*equ8ri947rnn56ZMURWchA.png" /></figure><p>The goal was to create a simple and modular digital tool for freelancers to use to generate quotes for client work. The main characteristics of any professional Proposals is that all follow a document format. Therefore we based the main theme of the product in a word processing like environment.</p><h3>UX &amp; Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fp-pePFcEG5sKtLWaf1bgg.png" /></figure><h3>The Fly-out menu</h3><p>To create a modular product we decided to use insertable templates for adding predefined sections into the document. Users can access these templates by tapping on the plus button which appears at the start of every new line. Users can choose to insert sections for images, invoice tables, timelines and signatures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EGceUGekYd4ax81CXSStOg.png" /></figure><h3>UI Design</h3><p>Overall the product portrays a minimalistic and easy to use application. Here’s a one pager mock up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*czmCUhqG5H4LeBLw6dWHGA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c64dc0a3f28" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momozafarian/proposal-design-process-9c64dc0a3f28">ProPosal — Design Process</a> was originally published in <a href="https://medium.com/momozafarian">Mo Mozafarian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hi.]]></title>
            <link>https://medium.com/momozafarian/hi-9541c66aa2d8?source=rss----9008c021c768---4</link>
            <guid isPermaLink="false">https://medium.com/p/9541c66aa2d8</guid>
            <category><![CDATA[about-me]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Tue, 09 Jan 2018 01:15:35 GMT</pubDate>
            <atom:updated>2018-01-10T00:49:11.525Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0dlWKBZalBS0l5bXt6ZDQw.png" /></figure><p>My name is Mo Mozafarian. I’m a multi-disciplinary designer, passionate about designing and building intuitive products. My experience includes leading product teams from ideation, user research, prototyping to defining product road-maps, execution and product roll-outs.</p><p>I have a strong background in visual design and am a self-taught front-end developer.</p><p>I’m a user-centred design advocate and the writer of Linear UX, a set of principles for creating intuitive products.</p><p><a href="https://uxdesign.cc/linear-ux-ad7dc634b5b1">Linear UX</a></p><h3>Freelance Experience</h3><p>I’ve been very fortunate to work with clients from agencies to start-ups and fortune 500 companies on product strategy, ideation and execution over the past 10 years.</p><p>Some noteworthy clients includes Star Alliance, SanDisk, American Express, Unicef, Canadian Curling Association.</p><h3>First Startup, Relevant AI</h3><p>In 2013, I started working on my very first start-up with a team of talented engineers in the pursuit of creating a more personalized internet experience.<br>The philosophy behind the idea and our approach is best explained here:</p><p><a href="https://medium.com/relevant-stories/a-little-taste-of-the-future-941cd18bdffd">A little taste of the future</a></p><p>Relevant, was a mobile product that was used and praised by tens of thousands of people worldwide. A mobile app accompanied by a series of dev tools including web platforms and a proprietary programming language (REL).</p><h3>Featured Work &amp; Case Studies</h3><p>Here are some of my work on dribbble:</p><p><a href="https://dribbble.com/M_Mozafarian">Mo Mozafarian</a></p><p>And my latest case studies are here:</p><ul><li><a href="https://momozafarian.com/when-design-engineering-mathematics-come-together-daf45a911258">When Design, Engineering &amp; Mathematics Come Together</a></li><li><a href="https://momozafarian.com/case-study-designing-sandisk-ixpand-base-mobile-app-7b72a9a44172">Designing iXpand Base Mobile App</a></li></ul><blockquote><strong>Have a look around and let me know what you think.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9541c66aa2d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momozafarian/hi-9541c66aa2d8">Hi.</a> was originally published in <a href="https://medium.com/momozafarian">Mo Mozafarian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts on Bots]]></title>
            <link>https://medium.com/momozafarian/thoughts-on-bots-2a31081d4b4f?source=rss----9008c021c768---4</link>
            <guid isPermaLink="false">https://medium.com/p/2a31081d4b4f</guid>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 19:13:43 GMT</pubDate>
            <atom:updated>2016-10-12T19:44:12.176Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_zNqq8hMHwazIwzswTRyQ.png" /></figure><h4><strong>Let the bots do the talking</strong></h4><p>Bots have been around for over 50 years but the recent hype around them is all because of the tremendous growth and the addictiveness of messaging apps.</p><p>By definition a bot is an automated or semi-automated software application that carries out repetitive and mundane tasks. When the input comes in a text format via a two way conversation channel, we refer to them as chatbots.</p><p>This form of bots is what the tech industry is so excited about. Regardless whether it is in China or the US messaging apps are the one experience with universal popularity.</p><h4>Why Now</h4><p>The growth of interests in the space would not be possible if other factors were not in place too. What are making the bot revolution possible in 2016:</p><ul><li><strong><em>Timing</em></strong>: Exponential growth in Natural Language Processing, Machine Learning and AI along with all the open source contribution from the community and not to be forgotten big companies giving access to their algorithms (Deep Mind by Google)</li><li><strong><em>Costs</em></strong>: Cloud Computation and development for bots is relatively cheaper compared to other channels like creating and maintaining mobile apps and websites</li><li><strong><em>Scalability</em></strong>: Easier to scale up software by adding more servers compared to getting bigger facilities and hiring more people</li><li><strong><em>Distribution channels</em></strong>: Facebook Messenger, Telegram, Kik and WeChat allowing potentially billions of highly engaged users to access services/businesses</li></ul><h3>Potential Winners</h3><p>Although it is still early days and the market needs to be proven I think there are 3 main areas that bots will have the most potential to be disruptive:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YuoYuCQdZUoyTacyH0fQxg.png" /></figure><h4><strong>Customer Support</strong></h4><p>This is an old and broken experience that a lot of companies are dealing with/spending money on. Things like help desks, messaging boards and FAQs fall in this category. A lot has been said on how the AI evolution will be the end of the customer service jobs and chatbots are on the forefront of that change.</p><h4><strong>Concierge Services</strong></h4><p>Till now difficult to scale, as nothing could replace a face-to-face experience with a sales associate/agent. The advances in Natural Language Processing and conversational commerce is about to change that. The fact that e-commerce giant Shopify has already acquired a<a href="http://venturebeat.com/2016/04/13/shopify-acquires-kit-the-artificially-intelligent-marketing-bot/"> bot company</a> proves the point. Brands will be experimenting with providing more relevant experiences and personalized recommendations for their customers via bots. There are already companies like Sephora and its concierge chatbot on Kik that are leading the pack.</p><h4><strong>Personal Assistants</strong></h4><p>While I think there is a lot of money to be made in the first two areas, in my view the biggest win (long-term) will be in bots as Personal Assistants in the consumer market. AI-powered existing assistants like Siri or Cortana are based on responsive user experiences that focus on understanding and fulfilling requests. But imagine a future where bots cooperate with each other and are managed by one personal assistant bot. One bot that is main focus is analyzing received data and making personalized recommendations.</p><p>That future assistant will be actively anticipating our requests and queries. It is tempting to think that such a personal experience is starting to be created in form of popular personal chatbots like <a href="https://chatbotsmagazine.com/bots-are-awesome-humans-not-so-much-7b2d62630668#.wme4m1s0m">Estherbot</a> or <a href="https://chatbotsmagazine.com/messinabot-office-hours-c578112bf7f#.qedaowz1u">MessinaBot</a>. However the more realistic scenario is that the platform owners like Facebook (Facebook M) will be the ones who create and monetize it.</p><h3>Hybrid that teaches itself</h3><p>What makes chatbots stand out as a software solution is how fluid the transition to human-to-human interactions can be when needed. All thanks to being based on a conversational user experience. In long term is mostly that bots will be responsible for customer service call and ultimately replace human agents.</p><p>Here’s an example of a help desk bot for a cable company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qUoErowG3insfupESOdmhg.png" /></figure><p>Like any good product it starts with a greeting to humanize the experience. If it’s a first time user the bot will ask some questions to verify the account and also to link up user’s social account with the one they have on their database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hmTMTPi3PQvI-kqqx9uNrQ.png" /></figure><p>Once the user is verified, the bot goes through a series of general troubleshooting suggestions providing rich media, interactive step by step guide. This process can be repeated a few times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*squUbPc_oxyXnAavc3E4sw.png" /></figure><p>If the suggestions didn’t solve user’s problem then the bot will fallback on a human agent and the human agent will take it from there. Once the human agent solves the problem he/she adds the results to the knowledge base. The more this process gets repeated the more data gets added to the knowledge base. Therefore the possibility of the bot being able to solve user’s problem without the human agents increases.</p><h4>So in a nutshell:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jPvMfndnLxil8yb-0JuTQg.png" /></figure><h4>Put it in perspective</h4><p>Let’s say if at the beginning the solutions offered by the bot only solved 10% of the cases, keeping the process in mind, over time with more and more cases added to the knowledge base the bot would get smarter and can solve more cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*9ToEO2fA85P076IGb7FaKg.png" /></figure><p>That means human agents will ultimately be supervising the process and solving fringe cases. Their roles at that stage will be mainly around feeding the knowledge base.</p><h3>Characteristics of successful bots</h3><p>While I think the success of bots will defer case by case and market by market, successful bots will share the same characteristics:</p><ul><li>They will imitate human but <strong>stay as bots</strong> —<em> Faking human is distasteful</em></li><li>They will clearly <strong>state tasks</strong> they can accomplish — <em>not leaving it open for user to ask anything</em></li><li>They will <strong>remove frictions</strong> not add one — <em>Minimizing the number of steps in user scenarios not adding new ones</em></li></ul><blockquote>In my view, the make it or break it for bots, like any other great product, will be in having a <strong>superior UX and UI</strong>. Where the UX is the user flow and bots’ capabilities and the UI is the voice and tone. (more on this in the next post)</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0AkhCp7EtcvKWKromqdH5A.png" /></figure><p>The question that only time will answer is “are bots here to stay?” This can only be determined with user adoption over time. Recent changes in the app economy are a great example of it. With the lock on the App Store now only the A-list players are winning. Will that also be the case for chatbots?</p><p>We’ll see.</p><p>M</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*xVXWVhL3QjUAZGByCnwf5A.gif" /><figcaption>Enjoyed the article? Click the ❤ below to recommend it to other interested readers!</figcaption></figure><figure><a href="https://docs.google.com/forms/d/e/1FAIpQLSfJDqeR7zbRBfQvx6mouQAhjK4lrCy3z9Z6Ppxln7f1xi12dg/viewform?c=0&amp;w=1"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*rRjUc6JW61AP1UWsa-yItQ.png" /></a></figure><figure><a href="https://chatbotsmagazine.com/be-featured-in-front-of-thousands-of-people-interested-in-bots-e7040c4080df#.hswzhzpp9"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*OGAA3ICxv3ds-RK2Sq4oxA.png" /></a></figure><figure><a href="https://chatbotsmagazine.com/want-to-receive-the-best-chatbot-related-content-in-your-medium-feed-20a9c11f11b6#.1t1yhwcyz"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*1XecGp_cGZ1wGLAldRHLWQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a31081d4b4f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momozafarian/thoughts-on-bots-2a31081d4b4f">Thoughts on Bots</a> was originally published in <a href="https://medium.com/momozafarian">Mo Mozafarian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A little taste of the future]]></title>
            <link>https://medium.com/momozafarian/a-little-taste-of-the-future-941cd18bdffd?source=rss----9008c021c768---4</link>
            <guid isPermaLink="false">https://medium.com/p/941cd18bdffd</guid>
            <category><![CDATA[cards]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 19:05:57 GMT</pubDate>
            <atom:updated>2015-10-09T17:03:20.921Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mlvuvgSLWT-ffM66lqMdJA.png" /><figcaption>A Day Made of Glass… Made possible by Corning. <a href="https://youtu.be/6Cf7IL_eZ38">https://youtu.be/6Cf7IL_eZ38</a></figcaption></figure><h4>Our quest for making the internet relevant</h4><p>For years the way we connect and interact with services on the internet has been through apps and websites.</p><blockquote>What if it wasn’t that way?</blockquote><p>What if every step between the time we need a service, and the time we access it on our smart screens, took only an instant? What if we didn’t need to download and set up apps just to be able to view a particular piece of information or interact with a service on our “smart” devices?</p><p>What if the entire process of discovering services and interacting with them was based on what we need and when we need them? What if the things we cared about didn’t require us to find them, rather they would find us? But most importantly, what if all of these great services on the internet could work together to provide us with a seamless and fluid experience regardless of the screen size or the device we’re using?</p><p>You see, when I think about the future of mobile and smart screens, I have a hard time accepting that we will always have to go through a grid of icons, and launch a bunch of apps, just to access what we want. Even typing in keywords to get a list of blue links which then require us to navigate through multiple web pages just to reach what we were looking for is cumbersome.</p><p>I mean, if I’m close to a restaurant at lunch time, I should be able to see their menu, today’s specials, customer reviews, and even ingredients and calories of each menu item at a glance. All without downloading/launching multiple apps or visiting a series of scattered websites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*bAzFaJFgd9fJXLgLp8-ryQ.png" /></figure><p>Taking it further, I wanna be able to walk into a shopping mall and be greeted with a curated list of items that I might be interested in, on my smart screen. I wanna be able to browse through them, pick the ones I wanna try on and get the stores to put them in the dressing room for me — or even go ahead and purchase them; then simply grab them from the pick up desk at the store. Again, all from my smart screen without downloading apps or launching websites.</p><p>I see a future where we can simply take out our smart screens and every relevant thing we need appears right in front of us, automagically. All without requiring us to search, download, or set up new apps.</p><h3>It’s not too far fetched…</h3><p>However, it is crazy to think that we can achieve such fluidity and seamless integration of multiple services within the current mobile paradigms — the SILOED apps and scattered websites. For starters, it makes no sense to launch an entire app in order to access a small piece of functionality or content inside the application.</p><p>Moreover, this paradigm entails the download and installation of a whole piece of software, just for the purpose of viewing one bit of information or tapping a button to request a service.</p><p>Achieving such user experience utopia requires a completely new way of thinking. A new medium/paradigm. A new method heavily structured around APIs and API integrations. A universal and adaptable presentation layer that displays information/data and also allows users to interact with the underlying service regardless of the device, screen-size or even the OS.</p><p>We call it the Card Paradigm.</p><h3>The Card Paradigm</h3><p>We’ve already seen some implementations of cards in our favourite apps. Facebook uses cards. Twitter uses cards. Pinterest, Groupon, you name it. Even the entire Google search has now transitioned to cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y38jjlqxtBB33itpDJ5AAg.png" /></figure><p>However, by cards I don’t mean cards just as design patterns. I mean cards more as atomic units. Units that act as the presentation medium for accessing internet services over APIs/SDKs which can also carry “App-Like” functionalities. Units that let us interact with the underlying content/services without requiring us to download and navigate through multiple apps or websites.</p><p><em>*Disclaimer: Form now on by “Cards” I’m referring to Cards that are built using our platform.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoOQmQnytzPwyvTIaoBp0g.png" /></figure><p>Units that are lightweight, universal, platform-independent, yet native to every platform, and flexible enough to connect directly to any internal and/or external API. Units that can perform their own logic, and effortlessly present the final results on any smart screen.</p><p>Contextually aware intelligent units that are aware of one another and interact with each other over a common language/protocol to bring you whatever you need whenever you need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BQQ8PYJnBoFh66be9gRI9Q.png" /></figure><h3>Chained Cards: the “App-Like” experience</h3><p>Let’s do a quick overview of a card made for ProductHunt, one of my favourite services on the internet with a great iOS app. However, I am not a power user, I just want to see the latest products and the conversation, so for me the app is overkill. Through cards and the card-bundling feature (Chaining Cards) we can achieve a somewhat app-like experience without downloading anything new.</p><p>Here’s is an example of transforming ProductHunt iOS App to Cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aISdKwk0j0ub9OE7e8G7rw.png" /><figcaption>ProductHunt iOS App -&gt; ProductHunt Card -&gt; Relevant Chained Cards</figcaption></figure><p>A more advanced chaining example, would be enabling cards from different services to work with one another to bring a more fluid experience. Something that usually requires us to launch 5–8 apps currently can be achieved in one screen with chained cards</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*lC6xhooSqRY9Y87ilUsD6w.png" /></figure><p>Since cards are constructed on the fly, they don’t require any apps to be downloaded. Not even searching for websites. You get what you need when you need it in a unified experience.</p><blockquote>The Nerdy Version: Cards are constructed on the fly from an extremely simple scripting language built for API aggregation and data manipulation capable of performing complex logic and responding to user interaction. All without the advanced design and programming knowledge (callback-hell) that such functionality often entails. More on this in the next blog post.</blockquote><p>You see, the same functionality that previously required crafting apps or creating websites, can now be achieved with the Card Paradigm, and since all the infrastructure and plumbing has been done, anyone should be able to easily build a fully interactive card in minutes. As long as you know what an API is, you are good to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*By_K0KWs1b6nXmmE37J2oQ.png" /></figure><p>We’ve been heads down working on this technology for sometime now, and it’s still in its very early days. The first incarnation of our technology is the Relevant iOS app which you can download from the App Store.<br>(<a href="https://goo.gl/Qu39nf">Download here</a>)</p><p>In the upcoming months we should be ready to release our SDK so others can also leverage our technology to create a more interconnected service or application. Messaging apps, content platforms, personal assistance apps, aggregators, e-commerce, … . You can sign up here: <a href="http://relevant.ai/friends/">relevant.ai/friends</a></p><p>Ultimately we want to enable more and more devices and services to work with one another seamlessly over a common protocol. From wearables, and smart glasses to gaming consoles and TV Boxes, and even intelligent screens for electric cars.</p><p>This is a future worth building. You feel me?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=941cd18bdffd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momozafarian/a-little-taste-of-the-future-941cd18bdffd">A little taste of the future</a> was originally published in <a href="https://medium.com/momozafarian">Mo Mozafarian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agenda App — Design Process]]></title>
            <link>https://medium.com/momozafarian/agenda-app-design-process-6bcf7f5db22d?source=rss----9008c021c768---4</link>
            <guid isPermaLink="false">https://medium.com/p/6bcf7f5db22d</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 18:59:23 GMT</pubDate>
            <atom:updated>2018-01-08T18:59:22.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*opAHOHMVnlfoiYf55xeTXg.png" /></figure><p>The objective was to create a cross-platform, browser based application that would allow event organizers to create beautiful agendas for their attendees.</p><p>The main pain points of going to events are not knowing who is speaking, when the next session is, where to go next and how to interact with the speakers over social media. While there are plenty of create a native app for your event solutions out there, it is difficult to get attendees to download an app.</p><h3>The UX</h3><p>Agenda at a first glance is a list of sessions ordered by time. When a user taps on a session that cell expands to show more details. For ease of use we decided to put secondary screens inside a hamburger menu that can be accessed from the top-right of every screen. While there are better solutions for implementing navigations in native application, given the restrictions with the current browsers we decided to go with a hamburger menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hxa4_d4zyMN2znYBR6GRaA.png" /></figure><h3>The UI</h3><p>The user interface was designed to have a very minimalistic look followed by accent colours that would go with the branding of each event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZEKIW49P6ljpP17DJDC1Zw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bcf7f5db22d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momozafarian/agenda-app-design-process-6bcf7f5db22d">Agenda App — Design Process</a> was originally published in <a href="https://medium.com/momozafarian">Mo Mozafarian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Relevant AI]]></title>
            <link>https://medium.com/momozafarian/relevant-ai-design-process-f0174589ae2e?source=rss----9008c021c768---4</link>
            <guid isPermaLink="false">https://medium.com/p/f0174589ae2e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 18:38:17 GMT</pubDate>
            <atom:updated>2018-03-06T16:25:10.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*URUnhtTMY8Y5vF1ky7MLiQ.png" /></figure><h4>Case Study &amp; Design Process</h4><p>A few years back I started working with a team of talented engineers on a mission to create a more personalized internet experience for everyone. It led us to founding our startup, Relevant AI.</p><p>With Relevant we wanted to create an interface layer that would sit on top of internet service and allow us to interact with our favorite services/apps based on relevancy. Something that would allow us to get what we want/need without needing to jump from app to app and website to website. The philosophy behind Relevant AI, which became a product used and praised by tens of thousands of people worldwide is best explained here:</p><p><a href="https://medium.com/relevant-stories/a-little-taste-of-the-future-941cd18bdffd">A little taste of the future</a></p><p>As a founder, I was also responsible for all elements of product design process. Both for the mobile app and the underlying API normalizer technology that made it all possible.</p><h3>Problem</h3><p>“There is an app for that.” was a popular catchphrase between 2010 and 2014. When it seemed any service on the internet was creating their own mobile apps. For smartphone users it meant downloading multiple apps to view a particular piece of information or interact with one service at a time.</p><p>As an avid mobile user myself, I felt the pain first hand. So I decided to investigate and see if others also feel the same pain.</p><p>A series of in-depth interviews with heavy app users, helped us validate our hypothesis and better understand the different aspects of the problem.</p><p>Some of our key findings from that research phase included:</p><ul><li><strong>Timing and relevance of specific service is a challenge</strong> — users struggled to find the right app when they needed it</li><li><strong>Searching for the right app on a smartphone of a heavy user can be navigational challenge itself </strong>— users did not organize the apps by frequency of usage, but chronologically (based on download date)</li><li><strong>Morning news routine was when that problem was most visible to users</strong> — just going through weather, sports results and calendar required going in and out of several apps and was time-consuming</li><li><strong>Pain of the problem was more severe for users who were self-described heavy app users</strong></li></ul><h3><strong>Ideation</strong></h3><blockquote><strong>What if</strong> every step between the time we need a service, and the time we access it on our smart screens, took only an instant?</blockquote><blockquote><strong>What if</strong> we did not need to download and set up apps just to be able to view a particular piece of information or interact with a service on our “smart” devices?</blockquote><blockquote><strong>What if</strong> we the entire process of discovering and interacting with internet services was based on what/when we need them?</blockquote><p>These were some of the questions we were trying to answer with the Relevant team.</p><p>Our assumption was to simplify the way users access information/services we had to focus on allowing users to get that particular piece of information <strong>faster</strong>. That way the experience created by the new product would be simpler than existing stand alone apps. That was inline with the “savings in time feel like simplicity” law we wanted to focus on.</p><p>Next step was to prioritize what specific pieces of information could be accessible through our product. Our two phase selection process started with analyzing my previous research results on users daily app routines and the data on the most popular apps used daily. The question we wanted to answer was “What type of information is an essential part of a smartphone <strong>user’s daily routine</strong>?”</p><p>Some of the themes we chose were: weather, sports, key news stations, Yelp and Zomato reviews as well as some niche services for our first target group.</p><p>The second phase was the <strong>technical feasibility</strong>. If we wanted to show a specific piece of information in our product, the services providing that information had to be accessible via an API.</p><p>As a result, we ended up with a list of potential “daily must-have” services to include in the first version of Relevant. Having in mind we were designing for a tech savvy heavy app users, we did include services that were especially attractive to early adopters like analytics, Product Hunt, Hacker News and so on.</p><h3><strong>Design Solution</strong></h3><p>In the product mission, we promised our users a more “relevant, personalized mobile experience” with less frictions which would save them time in comparison to the status quo, where they relied on multiple apps. To achieve such experience we decided to keep the Relevant Interface to just one screen and use card design patterns for displaying the key information from the underlying web services.</p><p>The main screen allows users to access the Library and SmartMode via the buttons on the top-right and top-left of the screen. Tapping on a card allowed users to dig deeper into that service by bring in a WebView or a MapView depending on the type of card. Here’s a look at the main screen wireframes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_JpFY6tjdExdzWaQC4p-A.png" /></figure><h3><strong>Relevant Cards</strong></h3><p>We used Cards design patterns to create flexible components that would display a mix of texts, images, and interactive buttons without being too intrusive. Our Card Design Pattern was made of smaller templates that could be paired with one another to provide a richer experience. This flexibility allowed us to have a variety of cards on the fly without hard-coding any elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8az77hGl-_d9_cSotSL3w.png" /></figure><h3><strong>Interactions</strong></h3><p>We also added some micro interactions that helped with the overall flow of the experience as well as keeping most used interactions within thumb-reach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/254/1*qXdQDK80Zy80ycFOawm8Ag.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/254/1*3mchCNmPrDtMa1sq3kTOzQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/254/1*u3aJfdHrTMFAWxDzP-yAeA.gif" /><figcaption>Left: Content Stream | Centre: Card Library | Right: Card Reordering</figcaption></figure><h3><strong>App Icon Design</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TEkkaYbdColIoEA1bx0EZw.png" /></figure><h3>Promo Video</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fh1pYQt_Lj8g%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dh1pYQt_Lj8g&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fh1pYQt_Lj8g%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bd3dbe219b46ae51f4b5242efac645a1/href">https://medium.com/media/bd3dbe219b46ae51f4b5242efac645a1/href</a></iframe><h3><strong>Results and feedback</strong></h3><p>Relevant iOS app was launched in December 2015 and received great reviews on the App Store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wb4Kzp1IWmOouzxcsuKk1A.png" /></figure><blockquote>“All my key items on cards and a flick away. Better than Google’s cards.”<br>– Barrylevy, United States</blockquote><blockquote>“With this application I have everything I care about in one place.”<br>– Cristobal Letelier, Chile</blockquote><blockquote>“Earned a place on my home screen!”<br>– TOBB, United Kingdom</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0174589ae2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momozafarian/relevant-ai-design-process-f0174589ae2e">Relevant AI</a> was originally published in <a href="https://medium.com/momozafarian">Mo Mozafarian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>