<?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[relevant stories - Medium]]></title>
        <description><![CDATA[thoughts worth sharing - Medium]]></description>
        <link>https://medium.com/relevant-stories?source=rss----5f7bb647d30c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>relevant stories - Medium</title>
            <link>https://medium.com/relevant-stories?source=rss----5f7bb647d30c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:18:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/relevant-stories" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sunset]]></title>
            <link>https://medium.com/relevant-stories/sunset-437c7babfa93?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/437c7babfa93</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[sunset]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Tue, 01 Nov 2016 18:43:23 GMT</pubDate>
            <atom:updated>2016-11-02T12:57:30.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0mIps1RWUBZre87B4qidfA.jpeg" /><figcaption>By Lee Key</figcaption></figure><p>After taking some time and exploring all options, we have decided to shut down Relevant.</p><p>This was an extremely hard decision to make but given the circumstances, I am convinced it is for the best.</p><p>We started <a href="http://relevant.ai/">Relevant</a> (previously Dashbook) a couple of years back. It’s been quite a journey with a lot of ups and downs. I’m very proud of the team for building a truly great product that was praised and used by tens of thousands of people from all around the world.</p><p>With Relevant we built a card based interface layer that brought all your favorite apps and websites into one place. An intelligent screen that allowed users to interact with the underlying services without needing to download/install any new app.</p><p>It’s just unfortunate that we weren’t able to grow big enough, fast enough. It’s an understatement to say how financially demanding it is to get distribution on the App Store, especially in the recent months.</p><p>We did consider a pivot given the promising core technology we built, REL — a programming language for API aggregation and Data Manipulation on the fly. Yet due to financial reasons we decided not to pursue.</p><p>I truly believe in the next 2–3 years, we will see a solution very similar if not the exact same as Relevant to arise and concur the market. The card based interfaces can solve the app fatigue for users and allow different services to get distribution based on relevancy, not the marketing money. This is something both Apple (iOS10 Notification center) and Google (Google Now Cards) have been investing heavily in.</p><p>In the last couple of months, we did explore the M&amp;A route. While we had great interests and got close to making a deal, we didn’t agree on the terms.</p><p>It’s tough but it is what it is.</p><p>Last but not least, I want to personally thank our investors and advisors for being there for us and providing the support when we needed it the most. Special thanks to our users who have been extremely supportive of us with their kind words and uplifting feedback. It’s been a roller coaster ride. We have learned a ton. We will take every piece of this learning and implement it in our next venture. That I promise.</p><p>P.S. If you are looking for great product people hit me up and I will be happy to connect you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=437c7babfa93" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/sunset-437c7babfa93">Sunset</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I build a couple of “apps” every day. This is how I do it.]]></title>
            <link>https://medium.com/relevant-stories/i-build-a-couple-of-apps-every-day-this-is-how-i-do-it-5c1cd9a6e757?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/5c1cd9a6e757</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Adolfo Rodriguez]]></dc:creator>
            <pubDate>Mon, 28 Dec 2015 00:57:58 GMT</pubDate>
            <atom:updated>2015-12-29T02:13:33.756Z</atom:updated>
            <content:encoded><![CDATA[<p>I often hear friends complain about having great ideas that never take off because they lack the means for execution. “If only I could code, I’d be a millionaire,” they have told themselves more than once.</p><p>Truth is, as some of you may already know, life is never that easy. Even if you become a great coder, your idea may not be as marketable, profitable or even as original as it sounds over a latte, and your execution needs to be extremely well done, presented, and distributed, in order to compete with all those other people having similar ideas. You are going to have to test your hypotheses, prototype, test again, iterate, pivot, growth-hack, and other startup buzz-verbs. Then as tools evolve to make each of these steps easier, markets are going to get saturated, and competitors are going to pop up all around you before you even have a working prototype.</p><p>The days of “build it and they’ll come” are UPPERCASE LONG gone, if they even existed. Heck, the days of “build a great product and they’ll come” are gone.</p><p>But even though front-end code (apps, websites) is only rarely the main limiting factor in building successful software, it often holds a prominent spot among limiting factors, at least in tech startup founders’ minds. At tech events I have heard speakers boast about having validated all of their hypotheses, to later close with statements such as “now we just need to build <em>the app,</em> and if you’re a great developer, please come talk to us!” Don’t get me wrong, validating before building is a proven strategy in most contexts, especially if <em>the app</em> is just a distribution channel for your great product. I’m just pointing out the limiting nature the <em>interface layer</em>.</p><p>In fact, it is pretty common for front-end developers in rich tech environments to be approached by strangers with ideas, or with development needs within small companies, even after all of the core product and back-end is completed.</p><h4><strong>Today,</strong> front-end code is <strong>still</strong> a limiting factor in the quest for building great apps.</h4><p>For a while I have regarded this limitation as a disease of the current nature of software development. So yes, I have been rooting for a cure that would likely make my own occupation unnecessary. Every time new tools are released to make front-end development easier and faster, the symptoms become less visible for those who employ them, but the syndrome remains.</p><p>Even in companies and agencies full of smart front-end developers building applications in bounded fields such as productivity or e-commerce, their job still requires tackling many user experience problems as completely new ones, tossing out old code and creating new one all the time.</p><p>So when I told my very smart friend from a large Seattle-based company that over the past year we had created a sufficiently comprehensive code base that would allow us to cleanly create and integrate new functionality into the <a href="http://relevant.ai/"><strong>Relevant app</strong></a> with very little effort, I did not expect him to believe me at first. “That never happens, but keep going…” he interjected. I would have thought the same. And before the <a href="https://en.wikipedia.org/wiki/Technological_singularity">technological singularity</a> (if it is ever to happen), this is likely to remain an absolute truth on software development as a whole.</p><p>But I postulate that, outside of gaming and other predominantly sensorial software categories, front-end user exeperience is evolving into a relatively restricted field, and with the right wiring/piping of graphical interface elements with a powerful API aggregation platform, the utopy of being limited not by development but only by ideas, is perfectly possible, and we have gotten pretty close to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1pyXfbKsLWPOttYD4NKwQA.jpeg" /></figure><h4>Cards: This is where I justify the quotes around the word “apps” in the title.</h4><p>Relevant cards, although not <strong>apps</strong> in the strict sense of the word (they are not standalone pieces of software), are interactive, aggregate multiple device and external APIs, and have a brain of their own. Their interface is composed of a growing set of <em>templates</em>. Their brain responds to complex instructions to gather and re-structure information from the web or from your device, just like our favourite apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*08klfd84XdxkX17H5WkHOQ.jpeg" /></figure><p>The <strong>Nearby</strong> card, for example, searches our surroundings for interesting places (such as restaurants or coffee shops), seamlessly aggregating Yelp and Foursquare reviews and ratings. Tapping on a place reveals relevant photos and menus when available.</p><p>The <strong>Movies</strong> card displays movie listings and reveals showtimes and other relevant information when tapped, using different sources.</p><p>Other popular cards include <strong>Weather</strong>, <strong>Transit</strong>, and <strong>News</strong>.</p><p>We have worked really hard to develop a platform that makes it a relatively simple task for us to create new cards, and we have succeeded; during the last few days I have found myself building <strong>more than one card per day</strong>. Some while shopping at the mall, or right before going to bed (users need not worry; the cards still go through careful QA and debugging before public deployment). And I can assure you, if you use Relevant and think that some cards could be smarter, richer, or more interactive, this is a reflection of our ability to imagine new functionality, rather than of the actual reach of the Relevant platform. Relevant cards can be as powerful as the services they channel, while being much lighter and faster than the average app or website. In fact you can have <strong>multiple cards</strong> in your deck without any apparent effect on the speed of the Relevant app.</p><p>Relevant cards may or may not be the future of mobile interfaces, but their success (most cards are added to hundreds of decks after made available in the library) is a reflection of a strong need for a more seamless and smarter interface layer between internet services and mobile screens. We are extremely grateful to be part of this shift, so the goal of this article is not to brag about our own ability to build cards in minutes, but to open up a channel of communication with anyone who may be interested in easily creating interface layers for existing services or even their own back-ends/APIs. Take it as a very first step towards the upcoming opening of the Relevant platform to the public.</p><p>Follow me, <a href="/service/mailto:adolfo@relevant.ai"><strong>email me</strong></a>, and join the conversation below to learn more about our vision for the interface layer of the future.</p><p>Visit <a href="http://relevant.ai/"><strong>relevant.ai</strong></a> to check out Relevant.</p><p><a href="http://relevant.ai/friends"><strong>Become our friend</strong></a> to learn more about intergrating and aggregating web services to build Relevant cards. <strong>Android users/makers:</strong> Yes, we’re soon coming to Android :)</p><h4>If you share our vision and like this story, please take a second to recommend it (using the green heart ♥️), and/or share it with your friends 🙂.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c1cd9a6e757" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/i-build-a-couple-of-apps-every-day-this-is-how-i-do-it-5c1cd9a6e757">I build a couple of “apps” every day. This is how I do it.</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Appending arbitrary properties to objects in Swift]]></title>
            <link>https://medium.com/relevant-stories/appending-arbitrary-properties-to-objects-in-swift-ca644a704376?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/ca644a704376</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Adolfo Rodriguez]]></dc:creator>
            <pubDate>Thu, 17 Dec 2015 18:34:36 GMT</pubDate>
            <atom:updated>2015-12-17T23:39:05.711Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N73L-7dencxV3GhGWgHumQ.jpeg" /></figure><p>Although some may regard it as a lazy solution to a problem that may be more cleanly tackled with a subclass, there are some extreme cases in which you may wish to append an arbitrarily named stored property to an existing object.</p><p>This is how you would do this JavaScript:</p><pre>someRandomObject.myNewPropertyName = someStuffIWillUseLater;</pre><p><em>(JavaScript developers do not need blog posts for stuff like this).</em></p><h4>Existing Solutions</h4><p>The key to many partial solutions to this general problem is to use Objective-C’s “objc_setAssociatedObject” function. This function is particularly useful for extending classes with new stored properties, as follows:</p><pre>var key:UInt8 = 0</pre><pre>let policy = objc_AssociationPolicy.OBJC_ASSOCIATION_RETAIN_NONATOMIC</pre><pre>extension UIView {<br>    var name:String? {<br>        get {<br>            return objc_getAssociatedObject(self,&amp;key) as? String<br>        }<br>        set {<br>            objc_setAssociatedObject(self,&amp;key,newValue,policy)<br>        }<br>    }<br>}</pre><p>The issue with this solution is that the property “name” is not arbitrary at all. We had to know before compilation that we needed such property with that particular type, on all UIView objects, and we had to define the global var “key” to serve as a <em>handle</em> for this property.</p><p>Additionally, the type of the property needs to conform to the protocol AnyObject (String does, because Swift).</p><h4>My Solution</h4><p><a href="http://stackoverflow.com/a/29662565">This Stack Overflow answer</a> uses <a href="https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/Generics.html">Swift’s generics</a> to enable appending properties of any type. This idea is the basis for my solution, but I go a bit further by getting rid of the need for the ugly global <em>handler</em> variable “key,” and as a result, allowing you to append arbitrarily named properties at runtime. This is what it looks like to make use of this solution:</p><pre><strong>//Setting properties:</strong><br>view--&gt;[&quot;name&quot;:&quot;My View&quot;]<br>view--&gt;[&quot;importantArea&quot;:CGRectMake(10,10,20,20)]</pre><pre><strong>//Retrieving properties</strong><br>let name:String? = view--&gt;&quot;name&quot;<br>let importantArea:CGRect? = view--&gt;&quot;importantArea&quot;</pre><pre><strong>//Removing a property</strong><br>view--&gt;[&quot;name&quot;:nil as String?]</pre><pre><strong>//Extending classes</strong><br>extension UIView {<br>    var name:String? {<br>        get {return self--&gt;&quot;name&quot;}<br>        set {self--&gt;[&quot;name&quot;:newValue]}<br>    }<br>}</pre><p>My original code involved a dictionary of wrapped variables which would serve as global handlers. However, Reddit user <a href="https://www.reddit.com/user/Kametrixom"><strong>Kametrixom</strong></a> has suggested a simplified version for the associativeKey String extension which I have implemented.</p><p>The full implementation follows. Please feel free to write your feedback below :)</p><h4>The Code</h4><pre>import Foundation</pre><pre>public final class Box&lt;T&gt; {<br>    public init(_ value: T) {<br>        self.value = value<br>    }<br>    <br>    public private(set) var value: T<br>}</pre><pre>private extension String {<br>    var associativeKey:UnsafePointer&lt;Void&gt; {<br>        return unsafeBitCast(hashValue, UnsafePointer&lt;Void&gt;.self)<br>    }<br>}</pre><pre>infix operator --&gt; { precedence 180 }</pre><pre>public func --&gt; &lt;T&gt;(object:AnyObject,key:String) -&gt; T? {<br>    if let v = objc_getAssociatedObject(object, key.associativeKey)<br>               as? Box&lt;T&gt; {<br>        return v.value<br>    } else {<br>        return nil<br>    }<br>}</pre><pre>public func --&gt; &lt;T&gt;(object:AnyObject,dict:[String:T?]) {<br>    for (key,value) in dict {<br>        if value == nil {<br>            objc_setAssociatedObject(object, key.associativeKey,<br>                           nil,<br>                           .OBJC_ASSOCIATION_RETAIN_NONATOMIC)<br>        } else {<br>            objc_setAssociatedObject(object, key.associativeKey,<br>                           Box(value!),<br>                           .OBJC_ASSOCIATION_RETAIN_NONATOMIC)<br>        }<br>    }<br>}</pre><p>Follow me for more snippets of our code. Download the <a href="https://itunes.apple.com/app/relevant-missing-home-screen/id970172407?ls=1&amp;mt=8">Relevant iOS App to see it all in action :)</a></p><p>Originally posted for <a href="http://relevant.ai/">relevant.ai</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca644a704376" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/appending-arbitrary-properties-to-objects-in-swift-ca644a704376">Appending arbitrary properties to objects in Swift</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Relevant 2.0]]></title>
            <link>https://medium.com/relevant-stories/relevant-2-0-ecf4a36e5ba6?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/ecf4a36e5ba6</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Thu, 17 Dec 2015 01:13:08 GMT</pubDate>
            <atom:updated>2015-12-17T01:11:31.892Z</atom:updated>
            <content:encoded><![CDATA[<h4>Your daily routine all in one place.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MnsEWd3PZOqS9JZMCJxBxg.jpeg" /></figure><p>A few months back we released the very first version of <a href="http://relevant.ai/">Relevant</a> to the public. Our goal was to test the water with a wider range of people just to see how our users feel about this new concept of having all their favourite apps and websites in one screen in the form of Relevant Cards.</p><p>The thing is, thinking about the next 3–5 years I have a hard time accepting that we will be still going through a grid of icons, launching a bunch of apps and then navigating through multiple pages just to access what we want. With Relevant we’re exploring new ways to create a more fluid and frictionless mobile experience by bringing and connecting different pieces of the web together. (Read more here: <a href="https://medium.com/relevant-stories/a-little-taste-of-the-future-941cd18bdffd#.mb6ehmvpb">A little taste of the future</a>)</p><p>Today we’re excited to to launch <strong>Relevant 2.0</strong> which is the continuation of implementing our vision on creating a truly intelligent screen that brings you what you need when you need it.</p><p>With this new update we’re introducing two new features: Deep View and Smart Mode</p><h4>Deep View</h4><p>Or the ability to chain services/Relevant Cards to provide more context. Simply tap on a card and if deep view is available for that card you get a chain of cards all Relevant to main card. Try it with Weather, ProductHunt, Nearby, Sports Cards, Calendar, …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*h83d9-S5-sTs1iGSpYvjOg.gif" /><figcaption><strong>Weather Card</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*_TBnKTDQ4CWQ0L9cpUoOUA.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*XzdT637rQGR2B64bQ1dUTA.gif" /><figcaption><strong>ProductHunt &amp; Movies</strong></figcaption></figure><h4><strong>Smart Mode (Beta)</strong></h4><p>This new feature opens a new screen with a series of cards that you might be interested in given Time, Location and other context. This is our very first implementation of what we refer to as Passive Search. It’s designed in a way that the more you use Relevant, the smarter the app should get.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*Y5JHSvR-4IZAle4oimj2xQ.gif" /><figcaption><strong>SmartMode / Nearby Places for lunch</strong></figcaption></figure><p>That’s it for now. We are adding new Cards every week so make sure to opt in for Notifications. We’re very confident that you’re gonna love this new version of Relevant. Download it for free from the <a href="https://itunes.apple.com/app/relevant-missing-home-screen/id970172407?ls=1&amp;mt=8">AppStore</a> and let us know what you think.</p><p>P.S. A better quality video of Relevant in action is available at <a href="http://relevant.ai/">relevant.ai</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecf4a36e5ba6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/relevant-2-0-ecf4a36e5ba6">Relevant 2.0</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing everything? There’s an app for that]]></title>
            <link>https://medium.com/relevant-stories/doing-everything-there-s-an-app-for-that-2a01fbaa849f?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/2a01fbaa849f</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Adolfo Rodriguez]]></dc:creator>
            <pubDate>Wed, 16 Dec 2015 18:41:57 GMT</pubDate>
            <atom:updated>2015-12-17T03:20:10.498Z</atom:updated>
            <content:encoded><![CDATA[<h4>Notes on <a href="https://itunes.apple.com/app/relevant-missing-home-screen/id970172407?ls=1&amp;mt=8">Relevant – the missing home screen</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SHpGqHMfW85pWPl3148fcw.jpeg" /></figure><p>In the consumer app development world, one is often strongly advised against creating a s<em>wiss army knife</em>; a metaphor for the still too common application which by doing too much (or trying to do to much) becomes completely useless.</p><p><em>“Do one thing and do it well”</em> said everyone.</p><p>I profess this same advice, and so does <a href="https://medium.com/u/86eef2a6fb8a">Mo</a>. So how is it that we completely abandoned common sense for a whole year and ended up building an app whose ultimate goal is being able to do pretty much anything?</p><p>The short answer is we did not.</p><p>Let me start the long answer by shamelessly pitching Relevant.</p><p>If you are anything like me, you wake up every morning and read a couple of news headlines, glance at your Twitter feed, or skim some other sources on current events. Before starting your commute you check your calendar, the weather, and if you have been blessed with a decent public transportation system, you confirm your bus or train schedules.</p><p>If you are anything like millions of smartphone users out there, you jump between 10 different apps or websites just to catch up with your day, before you even walk out your door.</p><p>Picture a screen that <em>lets</em> you glance at all of these services without a dedicated piece of software for each of them. One where snippets of information are light, relevant, and rich, where movie ratings arrive seamlessly and orderly from multiple sources, and so do weather forecasts, food reviews, tech news, sports scores, transit schedules, and social media content. You are picturing <a href="http://relevant.ai/">Relevant</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MnsEWd3PZOqS9JZMCJxBxg.jpeg" /></figure><p>The key word here is <em>lets</em>. In fact by developing Relevant we have not built a calendar, or a news outlet, or a transit feed, or a local restaurant directory, or a social network. These are all services that exist, and you have been enjoying them for quite some time. Relevant unbundles them into their most essential parts, producing a simplicity which in turn generates a more connected experience, where one service may trigger another one while they both benefit from contextual information such as device location or manual input.</p><p>We have worked hard to make the integration of new services as smart and frictionless as it needs to be in order to satisfy your changing needs.</p><p>Rather than a swiss army knife, Relevant is a concierge. One that, as app development mantras demand, does <strong>one</strong> thing well; delivering the services you need exactly when you need them.</p><p><a href="https://itunes.apple.com/app/relevant-missing-home-screen/id970172407?ls=1&amp;mt=8">Download Relevant — the missing home screen on the App Store.</a></p><p>Follow me for more relevant posts, and if you’re a maker and would like to know more about the magic behind the Relevant platform, <a href="http://relevant.ai/friends/">become our friend</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a01fbaa849f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/doing-everything-there-s-an-app-for-that-2a01fbaa849f">Doing everything? There’s an app for that</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build a Reddit Card for Relevant]]></title>
            <link>https://medium.com/relevant-stories/build-a-reddit-card-for-relevant-ab36fed9f363?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/ab36fed9f363</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[reddit]]></category>
            <dc:creator><![CDATA[Adolfo Rodriguez]]></dc:creator>
            <pubDate>Fri, 09 Oct 2015 11:59:52 GMT</pubDate>
            <atom:updated>2015-10-09T15:35:19.654Z</atom:updated>
            <content:encoded><![CDATA[<p>In this tutorial I’m going to show you how to create a Reddit card for the <a href="http://relevant.ai/">Relevant iOS App</a> using the <a href="http://platform.relevant.ai/">card-building platform</a>.</p><h4>What we need:</h4><ul><li>An iOS device with the latest version of the <strong>Relevant iOS App</strong>. <a href="https://itunes.apple.com/app/relevant-missing-home-screen/id970172407?ls=1&amp;mt=8">Get it on the App Store</a> or find it there as <strong>relevant - the missing homescreen</strong>.</li><li>An internet browser (to build the card).</li><li>4–5 minutes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*wYaHI5r1Cl3Jg-mZ0b9j-g.jpeg" /></figure><p>We’re going to build a card very similar to the Reddit card that’s already available in the Relevant library.</p><p>View that card by dragging down on the app to display the library and tapping on the <strong>Add</strong> button next to “Reddit.”</p><p>Slide horizontally (left and right) on the card to view more Reddit posts.</p><p>To start building, launch the <a href="http://platform.relevant.ai/"><strong>Relevant card-building platform</strong></a> on your browser, log in using your GitHub account (if you don’t have one you can <a href="https://github.com/join"><strong>create it here</strong></a>), and click on <strong>Build Card</strong>.</p><p><strong>Step 1. Enter Card Info.</strong> We need a <em>Title</em>, <em>Credits</em> and <em>Summary</em>. You can go ahead and enter the values shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UsaDFtm2wShz6yfBVU5cnA.png" /></figure><p><strong>Step 2. Choose Card Type.</strong> Pick the <strong>Stream</strong> option. This simply means that this card will have several slides which can be viewed by scrolling horizontally. Each slide is a Reddit post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*gw7tuIF95funUNs1_58qCQ.png" /></figure><p><strong>Step 3. Choose a Template.</strong> Select the <strong>2nd Template</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xo6eey4pwZhF1dzbCOoxBQ.png" /></figure><p><strong>Step 4. Fetch Data.</strong> This is where it gets interesting. We need a JSON API from where the card info will be fetched. In this case we’ll use the Reddit API:</p><p><strong>https://www.reddit.com/hot.json</strong></p><p>Copy and paste this URL into the <strong>API</strong> text field and click on <strong>Fetch</strong>. A text area will show the fetched JSON object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0lFu8FJf2AkN0fi1LwWnlg.png" /></figure><p><strong>Step 5. Start Mapping.</strong> This JSON object is a variable that we call <strong><em>api</em></strong>. In this step we will map some of its values into the labels and images of the template we have picked.</p><ul><li><strong>Choose the Main Array:</strong> We need to locate the path to the main array where all the Reddit posts are listed. Simply enter;</li></ul><pre><strong><em>api</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;children&quot;<strong>]</strong></pre><ul><li><strong>Link To Source:</strong></li></ul><pre><strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;url&quot;<strong>]</strong></pre><p>(The <strong><em>item</em></strong> variable represents each Reddit post in the main array)</p><ul><li><strong>Banner Image:</strong></li></ul><p>(leave field empty)</p><ul><li><strong>Banner Caption:</strong></li></ul><pre><strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;domain&quot;<strong>]</strong></pre><ul><li><strong>Profile Image:</strong></li></ul><pre><strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;thumbnail&quot;<strong>]</strong></pre><p>(don’t worry if the image doesn’t show up right away)</p><ul><li><strong>Profile Caption:</strong></li></ul><p>(leave field empty)</p><ul><li><strong>Body:</strong></li></ul><pre><strong><em>item</em>[</strong>&quot;data&quot;<strong>,&quot;</strong>title&quot;<strong>]</strong></pre><ul><li><strong>Footer:</strong></li></ul><pre><strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;ups&quot;<strong>]</strong></pre><p>(This is the number of upvotes of this Reddit post)</p><p><strong>Click Next.</strong> You will see a preview of your card. <strong>Click Save.</strong></p><p>You are then going to see your card listed on the main page of the platform, as below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rqe27NyWYwRnZsCLrxZBSg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*LXMiIZpCKov6FnjTldvVAw.png" /></figure><p>You can now copy and paste the <strong><em>Alias</em></strong> of your card into the search field of the Relevant iOS App library (pull down to open the library); tap the <strong>Search</strong> (or <strong>Return</strong>) button of your keyboard; and then tap the <strong>Add</strong> button that pops up (assuming you have internet connection) to preview this card.</p><p>Slide horizontally (left and right) on your card to view other popular Reddit posts.</p><h3>Advanced Card Building — Editing the source.</h3><p>The card we just built looks great, but we can still improve it with some very basic programming knowledge. Go back to the <a href="http://platform.relevant.ai/">Relevant card-building platform</a> and click on the <strong>Source &lt;/&gt; </strong>button to view and edit your card’s source code in <strong>REL</strong>, the extremely simple scripting language we have created for you to build and edit Relevant Cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NtoZHGd7oVDUhnsKAkAJ-Q.png" /></figure><p>This code was automatically generated by the platform. We’ll do a couple of small edits to make our card smarter. We’ll edit the <strong><em>load</em></strong> <strong>{</strong>…<strong>}</strong> block, which is the code that’s executed when the card is loaded. Particularly we’ll edit the <strong>return</strong> value from the <strong><em>.loop</em></strong> <strong>{</strong>…<strong>}</strong> block. This value lists all of the card’s parts: “tap”, “actions”, “banner”, “footer”, “buttons”, and “sectional”. If you’d like to know more about each of these and other elements of the code, you can go ahead and read <a href="https://github.com/relevant-ai/RelevantCardsDocumentation">the more advanced preliminary documentations for <strong>REL</strong></a>. For now let’s focus on the edits.</p><p><strong>Edit #1. Banner:</strong></p><p>In the “banner” template replace:</p><pre>&quot;caption&quot;<strong>:</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;domain&quot;<strong>],</strong></pre><p>with</p><pre>&quot;caption&quot;<strong>:</strong> <strong>small(</strong>&quot;(&quot; <strong>+</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;domain&quot;<strong>]</strong> <strong>+</strong> &quot;)&quot;<strong>)</strong>,</pre><p><strong>Edit #2. Round image:</strong></p><p>You may have noticed that some of the Reddit posts are missing an image. We solve this using some more advanced <strong>REL</strong>.</p><p>Replace</p><pre>&quot;image&quot;<strong>:</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong> &quot;thumbnail&quot;<strong>],</strong></pre><p>with</p><pre>&quot;image&quot;<strong>:</strong> <strong>(<em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;thumbnail&quot;<strong>]</strong> <strong>==</strong> <strong>null</strong> <strong>||</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;thumbnail&quot;<strong>]</strong> <strong>==</strong> &quot;&quot; <strong>||</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;thumbnail&quot;<strong>]</strong> <strong>==</strong> &quot;self&quot;<strong>).then(</strong>&quot;http://s3.dashbook.co/extra/reddit-default-img.jpg&quot;<strong>,</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;thumbnail&quot;<strong>]),</strong></pre><p><strong>Edit #3. Footer:</strong></p><p>Replace</p><pre>&quot;caption&quot;<strong>:</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong>&quot;ups&quot;<strong>]</strong></pre><p>with</p><pre>&quot;caption&quot;<strong>:</strong> <strong><em>item</em>[</strong><em>&quot;</em>data&quot;,&quot;ups&quot;<strong>]</strong> <strong>+</strong> &quot; upvotes | &quot; <strong>+</strong> <strong><em>item</em>[</strong>&quot;data&quot;<strong>,</strong> &quot;num_comments&quot;<strong>]</strong> <strong>+</strong> &quot; comments&quot;</pre><p><strong>Click Save Card</strong> and you’re done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*AXGCwPFlNVDIvhVn9iefeQ.jpeg" /><figcaption>Your Reddit card</figcaption></figure><p>As before, you may add your final card to your Relevant deck by pasting its <strong><em>Alias</em></strong> into the search field of the Relevant iOS App library (pull down to see the library); tapping the <strong>Search</strong> (or <strong>Return</strong>) button of your keyboard; and then tapping the <strong>Add</strong> button that pops up (assuming you have internet connection).</p><p>I hope you enjoyed this first tutorial. Stay alert for more tutorials, have a look at the <a href="https://github.com/relevant-ai/RelevantCardsDocumentation">preliminary docummentations</a> if you’d like to give <strong>REL</strong> a try, and if you have any questions don’t hesitate to tweet <strong>@wirchoreal</strong> or email me directly at <strong>adolfo@relevant.ai.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab36fed9f363" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/build-a-reddit-card-for-relevant-ab36fed9f363">How to Build a Reddit Card for Relevant</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mocking PHP with Swift]]></title>
            <link>https://medium.com/relevant-stories/mocking-php-with-swift-b42dd6fd7122?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/b42dd6fd7122</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Adolfo Rodriguez]]></dc:creator>
            <pubDate>Mon, 29 Jun 2015 21:19:55 GMT</pubDate>
            <atom:updated>2015-06-30T18:12:21.198Z</atom:updated>
            <content:encoded><![CDATA[<p>Since its release last year, Apple’s new programming language <strong>Swift</strong> has become pretty popular in the developer community. Swift modernizes the job of developing on Apple’s operating systems. Much like the Internet or Wikipedia, after less than a year using it I cannot remember how I used to code iOS apps without it.</p><p>Some of Swift’s best features (many of them borrowed from much praised languages like <strong>Python</strong> and <strong>Haskell</strong>) include <a href="https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/Generics.html"><strong>generics</strong></a>, <a href="https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/Closures.html#//apple_ref/doc/uid/TP40014097-CH11-ID102"><strong>trailing closures</strong></a>, <a href="https://robots.thoughtbot.com/introduction-to-function-currying-in-swift"><strong>function currying</strong></a>, <a href="http://nshipster.com/swift-literal-convertible/"><strong>literal convertibles</strong></a>, and <a href="https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/AdvancedOperators.html#//apple_ref/doc/uid/TP40014097-CH27-ID46"><strong>a very powerful operator overloading</strong></a>. These features let you substantially improve and extend the language as you code.</p><p>A side effect of some of these features is that you can <em>kind of</em> imitate other languages.</p><p>Here’s a <strong>somewhat creepy</strong> self-contained example of a <strong>PHP</strong>-style associative array constructor in Swift:</p><pre><strong>//SETUP</strong></pre><pre>import Foundation</pre><pre>struct <strong>PHPArrayItem</strong> {<br>    let key:<strong>String</strong><br>    let value:<strong>AnyObject</strong><br>}</pre><pre>infix operator <strong>=&gt;</strong> { associativity left precedence 100 }</pre><pre>func <strong>=&gt; </strong>(left:<strong>String</strong>, right:<strong>AnyObject</strong>) -&gt; <strong>PHPArrayItem</strong> {<br>    return <strong>PHPArrayItem</strong>(key: left, value: right)<br>}</pre><pre>func array(elements:<strong>PHPArrayItem...</strong>) -&gt; [<strong>String</strong>:<strong>AnyObject</strong>] {<br>    var dict:[<strong>String</strong>:<strong>AnyObject</strong>] = [:]<br>    elements.map{dict[$0.key] = $0.value}<br>    return dict<br>}</pre><pre><strong>//RESULT<br>//&lt;?php lol</strong></pre><pre>var myArray = array(<br>    &quot;a&quot; =&gt; 1,<br>    &quot;b&quot; =&gt; &quot;foo&quot;,<br>    &quot;c&quot; =&gt; &quot;var&quot;,<br>    &quot;d&quot; =&gt; 2<br>)</pre><pre><strong>//?&gt; This produces the dictionary [&quot;a&quot;:1,&quot;b&quot;:&quot;foo&quot;,&quot;c&quot;:&quot;var&quot;,&quot;d&quot;:2]</strong></pre><p>I’m only using one of the nice language features I mentioned before, but I can imagine how some of them may be used to similarly “mock” other languages or behaviours. JavaScript, you’re next! This may actually get useful!</p><p>Originally written for <a href="http://relevant.ai/"><strong>relevant.ai</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b42dd6fd7122" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/mocking-php-with-swift-b42dd6fd7122">Mocking PHP with Swift</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proposing a Standardized Vocabulary for Startups]]></title>
            <link>https://medium.com/relevant-stories/proposing-a-standardized-vocabulary-for-startups-1cdde7d631dc?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/1cdde7d631dc</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[advice]]></category>
            <dc:creator><![CDATA[Mo Mozafarian]]></dc:creator>
            <pubDate>Fri, 26 Jun 2015 14:17:48 GMT</pubDate>
            <atom:updated>2015-06-26T15:45:01.224Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyVsYucvkltnD43YK2_BQg.png" /></figure><p>So I recently noticed a conversational trend between startup folks which happens like every single time. It happens in the hallways, in the cafe while grabbing your morning coffee before your eyes are even fully open, in the washroom while pissing, at a cocktail party drinking to wash the pain away just to name a few. It’s like no matter what, or where you are it’s gonna come up one way or another.</p><blockquote>“oh btw, how’s your startup doing?”</blockquote><p>Stop. Stop right there. Don’t say a word. It’s a trap.</p><p>The things is, as simple as this question may sound, the answer to this question needs some thinking. Really hard thinking. And I mean it.</p><p>It’s not like, you can just say “we are fine” Or “things are well” and it’d go away. Turns out people actually care about what adjective you use to describe how things are going with your business. Unlike when someone asks “how you doing” and you say “I’m okay.” and nobody gives a damn. When it comes to startups, people seem to actually care.</p><p>The adjective you use has way deeper meaning that you’d think and you need to be smart about it. Of course, you don’t want a little misunderstanding jeopardizes you relationships or even worse lose creditability, or god forbid, people think of you as a dis-genuine person.</p><p>We don’t want this to happen. After all there are so many things in startups to take care of that you wouldn’t really want to add misunderstandings to it too.</p><p>Therefore, I’d like to propose a set of standard Vocabulary that’d put this very common misunderstanding forever in rest. From now on anytime anybody asks you: “how’re things going with your startup?” Or “ how’s your startup doing?” you can pick the right adjective that describes your situation/progress best from list below.</p><p>We are doing ________ :</p><p><strong>A) Shit (0–25%)</strong><br>When the average combination of product, sales, team morale, money and core metrics is below 25% and you are in deep shit. i.e. Founder disputes, out of money, no sales, missing product milestones and other typical startup stuff.</p><p><strong>B) Okay (25%-50%)</strong><br>When the average combination of product, sales, team morale, money and core metrics is between 25%-50% and you need to figure shit out asap. i.e 2–3 months of runway, tensions between teammates, product is not just there yet.</p><p><strong>C) Well or Fine (50%-75%)</strong><br>When the average combination of product, sales, team morale, money and core metrics is between 50%-75% and you are figuring things out to turn your business to a rocket ship. i.e. Things are starting to finally work for you, team morale is high, 8–10 months of runway in the bank and the product is in good health.</p><p><strong>D) Amazing (75%-100%)<br></strong>When the average combination of product, sales, team morale, money and core metrics is above 75% and everything is working in your favour. i.e. Taxi drivers go on protest against your company and your company makes more money as a result.</p><p>That’s my two cents. Hope it helps.</p><p>P.S. If you find it useful, please recommend it and help spread the word.</p><p><em>Originally written for </em><a href="http://relevant.ai/"><em>relevant.ai</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cdde7d631dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/proposing-a-standardized-vocabulary-for-startups-1cdde7d631dc">Proposing a Standardized Vocabulary for Startups</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[relevant 1.0]]></title>
            <link>https://medium.com/relevant-stories/relevant-1-0-2d79b2475e3f?source=rss----5f7bb647d30c---4</link>
            <guid isPermaLink="false">https://medium.com/p/2d79b2475e3f</guid>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[relevant]]></dc:creator>
            <pubDate>Mon, 15 Jun 2015 19:36:34 GMT</pubDate>
            <atom:updated>2015-06-17T19:14:53.557Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y058X7jXt1tuFqJxeqnxkw.png" /></figure><h4><a href="https://itunes.apple.com/app/relevant-missing-home-screen/id970172407?ls=1&amp;mt=8">Now available on the App Store</a></h4><h4>Today we’re excited to introduce Relevant for iOS. The best way to get a glance of your favourite apps and websites, all in one place.</h4><p>Relevant is designed to bring you all the best websites, apps and services you use on daily basis, into one screen. So you spend less time jumping from app to app, website to website to see what’s going on and spend more time on doing stuff.</p><h3><strong>Here’s how it works</strong></h3><p>Relevant turns the services you use on daily basis into beautiful, bite-size, easy to read, interactive Cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OtFP0jX_GLbFUnT33gGFAA.png" /></figure><p>From getting the latest news headlines, weather forecast, discovering cool new products on ProductHunt or Kickstarter, to finding places nearby and getting directions, you can do them all without leaving the home-screen.</p><p>Simply add the ones that are relevant to you form the library and you are all set. Now anytime you launch Relevant you get all the things you care about all in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9X1ih1Uzy41G3Q67is9jwA.png" /></figure><p>Relevant Cards are fully customizable, easy to share and blazingly fast. Just to name a few key features:</p><ul><li>Customize each cards to your preference from the back of the card</li><li>Reorder cards in your view based on your daily priorities</li><li>Hold down on cards to get access to extra functionality (go to source, share, open maps, reorder, refresh, …)</li><li>Drag down to see the library</li><li>Share cards via twitter, facebook, email, text message and more</li></ul><h3><strong>Don’t see a card you want, build it yourself</strong></h3><p>Relevant cards are built using <strong><em>REL — The Fancy JSON.</em></strong></p><p>REL at its core is a <em>Functional Immutable Programming Language</em> we developed to simplify the process of building cards. It obeys a reactive paradigm making sure that commands are executed exactly when needed, and it follows a simple readable JSON formatting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*snib_BavzoisjTb8sVba2A.png" /></figure><p>REL’s powerful parsing and processing engines make it super easy to <strong>aggregate </strong>different sources, <strong>manipulate APIs</strong>, and even include <strong>complex logics &amp; calculations</strong> into Relevant cards.</p><p>We worked hard to simplify the language without sacrificing its power so even <strong><em>non-programmers</em></strong> can easily learn REL and start building cool cards in minutes. We’re also open sourcing Relevant Cards built in house as we go and we encourage everybody else to do so, as well.</p><p>Sign up to get access: <a href="http://relevant.ai/#join-us"><strong>relevant.ai</strong></a></p><p>Also sample cards are available at: <a href="http://cards.relevant.ai/"><strong>cards.relevant.ai</strong></a></p><h3><strong>Our Vision</strong></h3><p>We are big believers that the future of the internet on mobile lies in Cards. Cards not just as design patterns but more as atomic units for delivering information.</p><p>With Relevant Cards we’re introducing a new category that sits right in between Apps and Websites. Something lightweight, contextually aware and relevant.</p><blockquote>Not everything needs to be an app or a website.<br>Some things are just meant to be Cards.</blockquote><p>With <strong>Relevant 1.0</strong>, we’re just scratching the surface of what it’d be like to have a centralized, unified experience across the services we use on daily bases. Hopefully, such technology can impact our daily lives and help us make better decisions by keeping us connected with what matters most and making smart suggestions at the right place, at the right time.</p><p>We have built Relevant and its card paradigm to simplify the way we consume, share, discover and interact with the services on the internet. This is the beginning of a long journey and we are just getting started.</p><p>We are excited to hear what you guys think about the iOS app and anxious to see what cards you build. Keep us posted!</p><p><a href="https://itunes.apple.com/app/relevant-missing-home-screen/id970172407?ls=1&amp;mt=8">Download the iOS App</a></p><p>Follow us on twitter @<a href="https://twitter.com/relevant_ai">relevant_ai</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d79b2475e3f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/relevant-stories/relevant-1-0-2d79b2475e3f">relevant 1.0</a> was originally published in <a href="https://medium.com/relevant-stories">relevant stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>