<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by SocialRadar on Medium]]></title>
        <description><![CDATA[Stories by SocialRadar on Medium]]></description>
        <link>https://medium.com/@SocialRadar?source=rss-83ac45ac935c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*EHWEjop0s-nvNTrA.png</url>
            <title>Stories by SocialRadar on Medium</title>
            <link>https://medium.com/@SocialRadar?source=rss-83ac45ac935c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:30:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SocialRadar/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[LocationKit: The Making of — Part 2]]></title>
            <link>https://medium.com/@SocialRadar/locationkit-the-making-of-part-2-4222a5cef545?source=rss-83ac45ac935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4222a5cef545</guid>
            <category><![CDATA[mobile-sdks]]></category>
            <category><![CDATA[location]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[SocialRadar]]></dc:creator>
            <pubDate>Tue, 26 Apr 2016 16:53:20 GMT</pubDate>
            <atom:updated>2016-04-26T17:30:36.811Z</atom:updated>
            <content:encoded><![CDATA[<h4>August 21, 2015</h4><p>This is part 2 of a 2 part series, <a href="https://medium.com/@SocialRadar/the-making-of-part-1-44177a492ce0">click here to check out part one.</a></p><p>Last time I discussed some background about how making the <a href="http://appstore.com/socialradar">SocialRadar</a> consumer app led us to develop a lot of the core technology we’ve baked into LocationKit — specifically around higher accuracy location and lower battery drain.</p><p>Here we’ll continue our journey into insights we’ve gained and built into <a href="https://locationkit.io/">LocationKit</a>, our advanced <a href="https://locationkit.io/">location manager</a> SDK, which is available for free to iOS and Android developers.</p><h3>Contextual Location Data</h3><p>While it’s great for LocationKit to provide higher accuracy location, it’s only the tip of the iceberg.</p><p>One of the things we discovered while building the SocialRadar app was that while a latitude/longitude can be useful, what we really cared about was contextual information about that location.</p><p>It’s nice to know that a user is currently at (38.904338837, -77.043243408), but unless you’re a computer (or a location geek like myself) you’re unlikely to recognize that as the coordinates of Washington, DC where our offices are located.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/0*HDLjrApcTB_Jgab-.png" /></figure><p>So what we’ve done here at LocationKit is put together an extensive <a href="https://locationkit.io/smart-polygons-shaping-a-more-intelligent-location/">proprietary backend database</a> of venues, buildings, addresses, and events, which we use to provide your app with more comprehensive contextual location information.</p><p>With our simple APIs like <a href="https://docs.locationkit.io/#single-contextual-data-request-with-current-location">getCurrentPlaceWithHandler</a>, you can immediately get information on where the device is.</p><p>So rather than saying “Where is Victor?” and getting an answer like “38.904338837, -77.043243408″ your app can say “Where is Victor?” and LocationKit will provide an answer like “He is at 1111 19th St NW, Washington DC 20036 and he is at the SocialRadar office and there is currently a hackathon taking place there.”</p><p>As a developer, you don’t have to mess around with getting a latitude/longitude, reverse geocoding it to figure out the address, then calling multiple other web APIs to figure out contextual information on that place. LocationKit will handle all of that complexity for you so your app can focus on kick ass experience for your users.</p><p>In summary, this means that rather than just getting a latitude/longitude like you would with CoreLocation, LocationKit will provide your app with context such as what venue your user is in, the address of that place, any events going on at that place, and other users of your app that are also at that place. This is incredibly useful when building an awesome app experience. As a developer you won’t have to do much heavy lifting as we’ve done that all for you with the LocationKit SDK.</p><h3>Auto Venue &amp; Event Detection</h3><p>Another thing we wanted to enable, while building the SocialRadar consumer application, were actions taken upon entering a venue or area.</p><p>For instance, we wanted SocialRadar to alert our user when they walk into the same bar as a friend they went to college with or when they are on the same block as their childhood friend. This would enable real-world interactions and prevent missed connections. It was the feature our users most cared about and was one of the most difficult to enable.</p><p>When you drop LocationKit into your app, it is not only monitoring the device for location information direct from the GPS, but also looking for patterns which seem to indicate the user is about to visit a place. Things like:</p><ul><li>The accelerometer or motion coprocessor is in a pattern consistent with walking</li><li>The compass on the device (magnetometer) indicates a sharp turn</li><li>The GPS signal suddenly drops, indicating they likely went indoors</li><li>The raw GPS points become clustered consistent with a user being in one place, no longer moving</li><li>The device connects to a wifi network</li><li>The user took a path into one of the <a href="https://locationkit.io/smart-polygons-shaping-a-more-intelligent-location/">building polygons in our venue database</a></li></ul><p>These are all factors, which we weight internally and use to figure out if we think a visit started. We are constantly tweaking this visit detection algorithm to improve our accuracy and speed of recognition.</p><p>And not only is LocationKit monitoring the device for visits, but when it detects a visit it will automatically call out to our backend servers, fetch all of the contextual information we have on the place where the visit occurred, and provide it to your app via a very simple API.</p><p>If you have provided a LocationKitDelegate, we will call a method <a href="https://docs.locationkit.io/#venue-amp-event-detection">didStartVisit</a> and provide it with all of the contextual information we have on the place so you can write code to execute and act using that data.</p><p>The visit detection algorithm is something that took us months of development and thousands of visits to local DC establishments during testing. As a developer, you can enjoy the fruits of our labor with LocationKit without having to engineer this complex beast yourself.</p><h3>Location Analytics Dashboard</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6uIdE6QOhg2Vj1up.png" /></figure><p>Another issue we ran into with the SocialRadar was that we had a wealth of location data on our users and wanted to perform analytics on it. Our marketing folks wanted to have insights such as “Where do most of my users live?”, “Which venues are users visiting when they are opening our app?”, “What venues are my users frequently visiting?”, and “What events are my users attending?”.</p><p>We surveyed the landscape and tried to find an existing analytics platform in which to display all of this data. We were unable to find something that adequately fit our needs, so we built our own.</p><p>With <a href="https://iojs.org/en/index.html">io.js</a> on the backend and <a href="http://facebook.github.io/react/">React</a> on the frontend, our team built our analytics dashboard from the ground up, making heavy use of <a href="http://d3js.org/">d3</a> and maps from our fellow DC-based startup <a href="https://www.mapbox.com/">Mapbox</a>.</p><p>Our custom dashboard, fully integrated into LocationKit, will provide a ton of location-based insights that no other platform we’ve seen has been able to provide. Things like the following visualization which shows which categories of venues users visit throughout the day:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h_2-1dN2BilS0A6c.png" /></figure><p>And maps, which show the number of visits by your users to each venue or only the visits to venues in which your app was opened:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/0*5xBopc-MDrCqTgrW.png" /></figure><p>And the ability to break these visits down by category, for instance viewing visits by my users to coffee shops and the corresponding analytics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xDEHgorHl_AWB4IP.png" /></figure><p>These kinds of location-based insights were formerly built one-off for our business folks, and now we are making them available for free as part of the whole LocationKit package. When you sign up for LocationKit you’ll get an API token and you’ll also get access to our location analytics dashboard. These insights can be used to figure out where you ought to target advertising to pick up users for your app, to alter your app based on where it’s used, and much more.</p><h3>Wrap up</h3><p>When we started developing the SocialRadar app, we had a concept and knew little about location.</p><p>We figured we could just use Apple and Google’s location libraries and the rest would be trivial. We could focus on user interface and let the OS handle all things location.</p><p>We quickly learned that wasn’t the case and that location is really hard.</p><p>Even in the most ideal conditions, the GPS alone is often inadequate to accurately determine a user’s location. And beyond that we realized that accurately getting the user’s coordinates was a miniscule slice of the pie that makes up location.</p><p>We had our work cut out for us, but over the course of years we gained expertise in the relevant areas of location, built up backend databases related to location, and built out location analytics. We are now in a position to offer all of our expertise in location to deliver the experience we näively thought the core OS location libraries would deliver for us way back when we started on our journey.</p><p>Learn more and try out our <a href="https://locationkit.io/">free LocationKit SDK</a> today!</p><p>This is part 2 of a 2 part series, <a href="https://medium.com/@SocialRadar/the-making-of-part-1-44177a492ce0">click here to check out part one.</a></p><p><em>Written by<br>Victor Quinn, VP of Engineering at SocialRadar</em></p><p><em>Originally published at </em><a href="https://locationkit.io/locationkit-the-making-of-part-2/"><em>https://locationkit.io/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4222a5cef545" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LocationKit: The Making of — Part 1]]></title>
            <link>https://medium.com/@SocialRadar/the-making-of-part-1-44177a492ce0?source=rss-83ac45ac935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/44177a492ce0</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[location]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[SocialRadar]]></dc:creator>
            <pubDate>Tue, 26 Apr 2016 16:47:21 GMT</pubDate>
            <atom:updated>2016-04-26T17:32:41.835Z</atom:updated>
            <content:encoded><![CDATA[<h4>August 12, 2015</h4><p>This is part 1 of a 2 part series, <a href="https://medium.com/@SocialRadar/locationkit-the-making-of-part-2-4222a5cef545#.kcaj8t5bl">click here for the second part</a>!</p><h3>Overview</h3><p>SocialRadar’s free <a href="https://locationkit.io/">LocationKit</a> SDK for iOS and Android provides advanced location technology to offer developers higher accuracy location, lower battery drain, automatic venue recognition, and detailed location analytics.</p><p>LocationKit enables you to add enhanced location capabilities, and therefore personalized experiences, to your mobile applications without the need for location expertise.</p><h3>Background</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/278/0*d_rhCtFYzYE2t6Rs.jpg" /></figure><p>The SocialRadar consumer app provides real-time information on the people around you</p><p>While we were building the <a href="http://appstore.com/socialradar">SocialRadar consumer application</a>, we came across a series of problems with existing location technology.</p><p>In order to build our app, we needed phones to be able to provide a highly accurate location with low battery drain and had to discover and engineer some creative solutions in order to make that happen.</p><p>And even once we tackled that problem so we could tell where our users were without killing their battery, we were still only able to resolve a latitude/longitude. But human beings don’t want to see or read coordinates, they want to know real-world physical contextual information.</p><p>Rather than “Christian is at 38.875166, -77.000844″ real people want to see “Christian is at the BlueJacket Brewery in the Navy Yard in Washington, DC and he’s there with your friends Susan and Kristin”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Nluv_qqo_P7yHWAL.jpg" /></figure><p>Shot of the interior of the awesome BlueJacket Brewery in Washington, DC</p><p>In setting out to solve these problems, we developed some state of the art technology, backend systems, and algorithms for making these experiences possible, and we are making all of that available to developers in an SDK that we are calling LocationKit which has now been freely available publicly for a few months now.</p><h3>High Accuracy Location</h3><p>LocationKit provides a higher level of location accuracy than Apple’s CoreLocation.</p><p>We are able to do this by utilizing sensors other than the GPS on the device and pairing it with our venue database and some proprietary algorithms to clean up the raw GPS points supplied by Apple’s <a href="https://locationkit.io/">Location Manager</a> and exclude outliers.</p><p>Getting GPS data directly from Apple is like drinking from a firehose at times and getting a raw, unfiltered stream of locations and acting on them within your app can lead to inconsistencies which degrade experience for your users. By using LocationKit in your app, you can have a greater confidence in the locations for your app without having to maintain a team of location experts in-house.</p><p>As an illustrative example, the GPS will often drift, even when the user is not moving. It will sometimes give more accurate points and sometimes less accurate points. LocationKit will monitor and intelligently filter out a lot of the bad data from this GPS drift. If we notice the accelerometer and compass are unmoved yet the GPS thinks the device moved 100 feet away, we know it’s likely suspect and will filter that point out, making sure your app doesn’t get that crazy outlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0T2KR81LUd3w0sYq.jpg" /></figure><p>As another example, it is very difficult to ascertain the user location, particularly in an urban environment as the GPS signal tends to be attenuated by buildings and will often bounce off them as well. We see this a lot around our office in downtown Washington, D.C.</p><p>Using only the raw GPS feed you are very likely to end up with a bogus location for your user. LocationKit will automatically monitor not only the GPS data, but also the compass and accelerometer so it knows that the user didn’t just teleport across the street, it is likely there is a GPS reflection off the nearby buildings. LocationKit will know, from the compass data that the user took a left turn into this building, which we have in our extensive <a href="https://locationkit.io/smart-polygons-shaping-a-more-intelligent-location/">proprietary venue database</a> so we know which building the user entered even though their GPS chip alone may point them as across the street due to reflection.</p><p>Suffice it to say there is a lot we do too in order to supply a higher accuracy location.</p><p>By using LocationKit in your app, you put all the expertise of our location experts without having to think about it. Your location data will be more accurate resulting in a better experience for your users.</p><h3>Low Battery Drain</h3><p>When we first released the SocialRadar app in our private beta almost 2 years ago, it worked to provide location updates like we desired, but the battery drain was rouuuuuugh.</p><p>I can’t remember specifics, but I think we were averaging ~10–15% battery drain per hour for our app. This was entirely unacceptable. I had close friends and family using the beta who apologetically uninstalled it saying that they couldn’t bear the intense battery drain we were putting their phones through.</p><p>After that rough experience, we set out to make sure we could deliver best of breed location while keeping battery drain low and boy did we learn some tricks. We fed them into LocationKit and learned some more.</p><p>We take battery drain very seriously and have gone to great strides to reduce it whenever possible.</p><p>In order to provide the kind of always-on background location updates that LocationKit does, we have to keep the GPS active all of the time. So how then do we ensure that the user’s battery isn’t dead within the hour?</p><p>Well, through a lot of trial and error, we came across the not altogether surprising fact that when you tell Apple that you do not need a high accuracy location, it drains a lot less battery.</p><p>So, we keep the GPS running constantly, but we throttle it up and down intelligently to provide maximum accuracy with minimal battery drain.</p><p>We do tricks like monitor the accelerometer to notice when the user is not moving and throttle the GPS down while they are stationary, then throttle it back up once they start moving.</p><p>This means that our battery drain while their phone is on their night stand is ultra minimal but we can still resolve with good accuracy when they walk outside and into the pizza joint around the corner.</p><p>We throttle the GPS down when the user is (driving data gathered while cruising at 55 MPH is unlikely to yield useful results when figuring out which venues the user visits) and back up when they park their car and start walking.</p><p>This is the default behavior, a mode we refer to internally as “Best for venue detection” which is our lowest battery possible drain while maintaining a very high rate of accuracy on detecting venue visits, but a new feature we just rolled out is that developers can override our default setting with their own custom profile if they want LocationKit to behave a little differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HythboBtrRzwY4Q9.jpg" /></figure><p>A photo of one of our our battery testing rigs, Arduino and all</p><p>I’ll do another full blog post on how we measure, tweak, and quantify our low battery drain (it involves a fun project by one of our summer interns involving an Arduino!) at a later date.</p><p><a href="https://dashboard.locationkit.io/">Sign up for LocationKit</a> to get started today!</p><p>This is part 2 of a 2 part series, <a href="https://medium.com/@SocialRadar/locationkit-the-making-of-part-2-4222a5cef545">click here to check out part two</a>.</p><p><em>Written by<br>Victor Quinn, VP of Engineering at SocialRadar</em></p><p><em>Originally published at </em><a href="https://locationkit.io/locationkit-the-making-of-part-1/"><em>https://locationkit.io/locationkit-the-making-of-part-1/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44177a492ce0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>