<?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 Sydney Palumbo on Medium]]></title>
        <description><![CDATA[Stories by Sydney Palumbo on Medium]]></description>
        <link>https://medium.com/@sydneypalumbo?source=rss-fa3f327c199------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_JSG1n_nX6Hz1dqNHaKNSA.jpeg</url>
            <title>Stories by Sydney Palumbo on Medium</title>
            <link>https://medium.com/@sydneypalumbo?source=rss-fa3f327c199------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:13:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sydneypalumbo/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[Announcing API usage tracking]]></title>
            <link>https://medium.com/smartcar/announcing-api-usage-tracking-2c13065fadff?source=rss-fa3f327c199------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c13065fadff</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[cars]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[dashboard]]></category>
            <dc:creator><![CDATA[Sydney Palumbo]]></dc:creator>
            <pubDate>Wed, 23 Jan 2019 18:43:10 GMT</pubDate>
            <atom:updated>2019-02-10T02:04:58.400Z</atom:updated>
            <content:encoded><![CDATA[<p>Smartcar dashboard feature alert! 🚨</p><p>Today, we’re proud to announce the most recent addition to our <a href="https://dashboard.smartcar.com/">developer dashboard</a>: usage. Starting today, you will see the option “Usage” in the dashboard’s top left menu. Our usage graph allows you to easily track the requests you’ve made to Smartcar’s API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jbV2LOAyFmgsFYOC.png" /></figure><p>So, what are the benefits? What does this mean for you, developers? We’re glad you asked.</p><ul><li><strong>Trend Tracking</strong> 📈 Thanks to the usage graph’s ability to filter requests by different timeframes — month to date, past year, all time — you can clearly identify trends in volume and frequency of API requests. Not only will you be able to see progress over time, but you can easily pinpoint when it began and what inflection points occured along the way.</li><li><strong>Major Change Monitoring</strong> 💥 With a simple and straightforward visualization of your API requests, you can also monitor large spikes or falls and get real-time insights into when exactly those changes occur.</li><li><strong>Volume Check-In </strong>💯 The moment you land on the dashboard’s usage page, you’ll instantly know two things: 1) how many requests your app has made to Smartcar’s API, and 2) on how many unique vehicles it made those requests. Obtaining this data for a range of timeframes is the easiest thing you’ll do all day.</li></ul><p>Now it’s your turn — get out there and start making requests! Watch that blue line go up and up! 💙</p><p>Any features you’d love for us to add to our usage tracking? <a href="/service/mailto:support@smartcar.com">Give us a shout</a> — we’d love to hear from you!</p><p><em>Smartcar enables developers to locate and unlock cars with an API. Want to take our product for a spin? Check out our </em><a href="https://smartcar.com/docs/"><em>docs</em></a><em> and get started with our </em><a href="https://support.smartcar.com/getting-started/run-our-demo-app"><em>demo app</em></a><em>! Have any questions or feedback? Shoot us an </em><a href="/service/mailto:support@smartcar.com"><em>email</em></a><em>!</em> 🚀</p><p><em>PS: Follow us on </em><a href="https://www.linkedin.com/company/mysmartcar/"><em>LinkedIn</em></a><em> and </em><a href="https://www.facebook.com/mysmartcar/"><em>Facebook</em></a><em>!</em></p><p><em>Originally published at </em><a href="https://smartcar.com/blog/api-usage-tracking/"><em>smartcar.com</em></a><em> on January 23, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c13065fadff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartcar/announcing-api-usage-tracking-2c13065fadff">Announcing API usage tracking</a> was originally published in <a href="https://medium.com/smartcar">Smartcar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What the React? Routing & redesign]]></title>
            <link>https://medium.com/smartcar/what-the-react-routing-redesign-7817bc32f7aa?source=rss-fa3f327c199------2</link>
            <guid isPermaLink="false">https://medium.com/p/7817bc32f7aa</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[react-router]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Sydney Palumbo]]></dc:creator>
            <pubDate>Thu, 11 Oct 2018 23:25:00 GMT</pubDate>
            <atom:updated>2019-02-10T23:31:58.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M0V8VZ2FfDwhzE-kXRr-Jw.png" /></figure><p>Early in the process of <a href="https://smartcar.com/blog/dashboard-redesign/">redesigning our developer dashboard</a>, we came to a realization: The engineering effort needed to implement our exciting new design changes would entail more than just a few stylistic tweaks — a dilemma that many of our fellow engineers know all too well. There would be a handful of technical challenges we had to face during the redesign, especially when it came to routing.</p><p>“Oh, just move the navigation bar,” we said. “Just pull out a few parent routes here and add a few child routes there. We’ll be able to implement the entire redesign in a day — two days max, right?”</p><p>Not quite.</p><h3>Routing Renovations</h3><p>As the <a href="https://smartcar.com/blog/what-the-react-sagas/">previous episode</a> of our “What the React” series outlined, we wanted to eliminate as much friction from our developer experience as possible, starting with removing our /apps route. In our old dashboard, the /apps route was where you had to select your desired app from a list of all your applications, whenever you logged in. Thanks to the redesign, you don’t have to make that choice anymore. Instead, we make an educated guess of which app you’d like to view, based on which application you’ve most recently interacted with.</p><p>What’s more, each app in our dashboard now also contains a few nested routes of its own (think: app credentials and app settings) to organize content within that application more clearly.</p><h4>Before</h4><p>To help you visualize this, here’s the original flow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*29AKvtZSW4hz2g4K.png" /><figcaption>1. Choose your application in the /apps route</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jxDJBYt6OgTyCDcG.png" /><figcaption>2. View all application info in the /apps/:id route</figcaption></figure><h4>After</h4><p>And here’s the new and improved flow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P8ecNtDZZ27DNGqi.png" /><figcaption>View the most important information for your application immediately in the /apps/:id/credentials route!</figcaption></figure><p>From a user standpoint, this is great. Now you get well-organized content and spend fewer clicks getting where you need to go within our dashboard.</p><p>From an engineering standpoint, however, improving this flow was no walk in the park. Our routing needed more than just a few tweaks. Specifically, we had to:</p><ul><li>Replace the /apps route with an /apps/:id route in our top-level router.</li><li>Allow you to navigate to nested routes within an application (e.g. /apps/:id/credentials or/apps/:id/settings).</li><li>If you go to an invalid nested route (e.g. /apps/:id/incorrect-nested-route) or enter the /apps/:id route without specifying a nested route, we should send you to a default nested route (/apps/:id/credentials).</li><li>If you go to a route with an invalid app id (e.g. /apps/invalid-id), we should tell you the application couldn’t be found and direct you to another app.</li><li>If you go to a top-level route that isn’t defined (e.g. /not-defined), we should route you to your most recently viewed app, as we do on login.</li></ul><p>So, before we knew it, we had a very long to-do list of routing adjustments.</p><p>Enter <a href="https://github.com/ReactTraining/react-router">React Router</a>.</p><h3>Elegant Nested Routing</h3><p>One extremely neat feature of React Router is that it allows for nested routing. For us, this meant that we could define our /apps/:id route — which renders the Application component — at the highest level of our dashboard’s routing. Then, in the render method of Application, we could define nested routes for every possible view within an app, each with its own respective component. For example, apps/:id/credentials renders the Credentials component and apps/:id/settings renders the Settings component.</p><p>On top of this, using nested routes allows us to verify that you have navigated to a valid app ID in the Application component, before we send you to a nested route. If the app ID in the route is invalid, we won’t send you to a nested route, but will instead prompt you to choose a valid app or register a new app.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d51bdb3ef33a90ba1828664a2ed18828/href">https://medium.com/media/d51bdb3ef33a90ba1828664a2ed18828/href</a></iframe><h3>Simple Redirecting</h3><p>Another benefit of using nested routing with React Router is the ability to redirect differently in the nested routes and the top-level routes.</p><p>At the nested level, we can redirect you to a default view within an application:</p><ul><li>If your nested route is not specified in the URL, we redirect to the default /apps/:id/credentials.</li><li>If your nested route is not defined in our dashboard, we also redirect to the default /apps/:id/credentials.</li></ul><p>At the top-level, we can redirect based on your authentication:</p><ul><li>If your authentication access token has expired, we redirect you to /login.</li><li>If you are still logged in, but attempt to go to /login, /signup, or another public route, we redirect you to your most recently viewed application.</li></ul><p>In order to do this, we wrote functional wrapper components — &lt;PublicRoute/&gt; and &lt;PrivateRoute/&gt; — around React Router’s &lt;Route/&gt;. If you are properly authenticated, these wrapper components will render the component corresponding to your route. If you aren’t properly authenticated, the wrapper components will render the specified redirect. They look something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d64202be70c05107a477f7e63ff641c5/href">https://medium.com/media/d64202be70c05107a477f7e63ff641c5/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e579f1287e96936375fe4300679718e/href">https://medium.com/media/1e579f1287e96936375fe4300679718e/href</a></iframe><p>Putting this all together, we get our top-level routes — each with their own path, authentication check, component, and redirect:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4f02d0607637d801a241597d4221f7d/href">https://medium.com/media/a4f02d0607637d801a241597d4221f7d/href</a></iframe><h3>We ❤️ React Router</h3><p>Long story short, we love React Router and its straightforward solutions for nested routes and redirecting.</p><p>With its help, adding new routes and tweaking old routes was a piece of cake! We tackled our seemingly very complicated to-do list of routing changes and got to work on our redesign styling in no time.</p><p>Blockers: gone 🚫</p><p>Our redesigned developer dashboard: shipped 🚢</p><p><em>Smartcar is an API that allows mobile and web apps to communicate with connected cars (think “check odometer” or “unlock doors”) — across vehicle brands, hardware-free.</em></p><p><em>Want to take our API for a spin? Check out our </em><a href="https://smartcar.com/docs/"><em>docs</em></a><em> and get started with our </em><a href="https://support.smartcar.com/getting-started/run-our-demo-app"><em>demo app</em></a><em>! Have any questions or feedback? Shoot us an </em><a href="/service/mailto:hello@smartcar.com"><em>email</em></a><em>! </em>🚀</p><p><em>PS: Follow us on </em><a href="https://www.instagram.com/mysmartcar/"><em>Instagram</em></a><em>!</em></p><p><em>Originally published at </em><a href="https://smartcar.com/blog/what-the-react-routing/"><em>smartcar.com</em></a><em> on October 11, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7817bc32f7aa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartcar/what-the-react-routing-redesign-7817bc32f7aa">What the React? Routing &amp; redesign</a> was originally published in <a href="https://medium.com/smartcar">Smartcar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unveiling Smartcar’s developer dashboard redesign]]></title>
            <link>https://medium.com/smartcar/unveiling-smartcars-developer-dashboard-redesign-afc9c75e7feb?source=rss-fa3f327c199------2</link>
            <guid isPermaLink="false">https://medium.com/p/afc9c75e7feb</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[dashboard]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[dashboard-design]]></category>
            <dc:creator><![CDATA[Sydney Palumbo]]></dc:creator>
            <pubDate>Thu, 27 Sep 2018 23:43:00 GMT</pubDate>
            <atom:updated>2019-02-10T02:17:24.911Z</atom:updated>
            <content:encoded><![CDATA[<p>Our goal at <a href="https://smartcar.com/">Smartcar</a> is to make it as simple and secure as possible for developers to build apps that communicate with cars. Our <a href="https://dashboard.smartcar.com/">developer dashboard</a> is your sidekick as you build on the Smartcar API, allowing you to create an account, register your app, and make your first request to a vehicle.</p><p>Today, we’re thrilled to announce that our developer dashboard just got a major facelift. 💅</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7FdKXOvecrV8nOPTZr7Ydg.jpeg" /><figcaption>Say hello to the redesigned developer dashboard!</figcaption></figure><p>With its sleek new exterior, the dashboard is focused on showing you exactly what you need to get started with the Smartcar API. Shedding a few of the clunkier steps that may have previously made it difficult to register and configure your application, the dashboard has been fully redesigned to give you a much friendlier developer experience (not to mention a much friendlier aesthetic experience too 😉).</p><p>More specifically, here are a few changes that might make your life (more than) a little bit easier when building with Smartcar:</p><ul><li><strong>Clutter-free layout: </strong>We’ve placed the information that’s most important to you front-and-center. After creating an account, you can easily copy your client ID, regenerate your client secret, or configure your redirect URIs in no time. These intuitive new features are designed to get you from 0 to 60 in 3.5.</li><li><strong>Clean and simple navigation: </strong>One of the key enhancements of our redesigned dashboard is its lightweight navigation. By neatly grouping content, the dashboard lets you focus on what’s important: your client credentials and app settings. No need to worry about jumping from page to page if you want to register a new application, view a list of all your apps, or get support from our team.</li><li><strong>Seamless access to docs, resources, and support: </strong>We’ve added quick access links to our documentation, support center, and getting-started guides. If you get stuck while configuring your application, you can read up on our relevant docs or run our demo app to get inspiration for your project.</li></ul><p>We hope that these improvements make it just a bit easier for you to build on the Smartcar platform today. To us, the most exciting part of this redesign is how it paves the way for many awesome features to come.</p><p>So, keep an eye out for what’s next! Don’t hesitate to give us as much feedback and as many feature requests as your heart desires. You can <a href="/service/mailto:support@smartcar.com">email us</a> or message us directly on <a href="https://twitter.com/mysmartcar">Twitter</a>. We read every message and are always more than happy to help! 💖</p><p><em>Smartcar is an API that allows mobile and web apps to communicate with connected cars (think “check odometer” or “unlock doors”) — across vehicle brands, no hardware needed.</em></p><p><em>Want to take our API for a spin? Check out our </em><a href="https://smartcar.com/docs/"><em>docs</em></a><em> and get started with our </em><a href="https://support.smartcar.com/getting-started/run-our-demo-app"><em>demo app</em></a><em>! Have any questions or feedback? Shoot us an </em><a href="/service/mailto:hello@smartcar.com"><em>email</em></a><em>! </em>🚀</p><p><em>Originally published at </em><a href="https://smartcar.com/blog/dashboard-redesign/"><em>smartcar.com</em></a><em> on September 27, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afc9c75e7feb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartcar/unveiling-smartcars-developer-dashboard-redesign-afc9c75e7feb">Unveiling Smartcar’s developer dashboard redesign</a> was originally published in <a href="https://medium.com/smartcar">Smartcar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taking a peek “Under the Hood” with Smartcar]]></title>
            <link>https://medium.com/smartcar/taking-a-peek-under-the-hood-with-smartcar-c13eec65cb26?source=rss-fa3f327c199------2</link>
            <guid isPermaLink="false">https://medium.com/p/c13eec65cb26</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Sydney Palumbo]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 23:31:00 GMT</pubDate>
            <atom:updated>2019-02-10T02:11:58.959Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zSkTiOKtvxEkJyylb0hfqQ.jpeg" /></figure><p>In mid-August, our team headed up to San Francisco to give engineers in the Bay Area an opportunity to peek under the hood of the <a href="https://smartcar.com/">Smartcar</a> developer experience. We wanted to give everyone in attendance a clear look into what we’ve been building recently and how they might start using the Smartcar API themselves.</p><h3>Not your usual event, we promise</h3><p>One of the challenges we face working on Smartcar day-to-day is understanding how developers who are completely new to our platform interact with Smartcar: how do they expect the process to work, what do they think is missing, where do they get stuck along the way? In other words, how can we make it easier to get off the ground with Smartcar?</p><p>Of course, we think about these things at Smartcar every day, but what might we learn if we were able to fully take a step back and remove ourselves from the product we’ve created? What elements of the developer experience might we be making assumptions about just because we see them so often internally?</p><p>So, back to the event. After Sahas and Sanketh Katta — our CEO and CTO — explained the Smartcar mission and gave a live demo showing how we connect to vehicles, we shifted gears to what may seem like a not-so-common tech meetup activity.</p><h3>Putting it into practice</h3><p>Breaking into small focus groups, we asked the audience to go through the process of getting started with Smartcar step by step: visiting our <a href="https://smartcar.com/">homepage</a>, making an account, and running our demo application. The attendees put themselves in the driver’s seat, getting into the mindset of developers who want to build applications with our API. The Smartcar crew took a back seat, trying to influence the audience as little as possible during a small-group brainstorming session.</p><p>We kept some critical questions at the center of the discussion. We wanted to be able to guide the conversation, but we didn’t want to direct our audience’s attention away from what it would naturally migrate towards. Here are a few examples of questions we came up with:</p><ul><li>“What do you expect to see when you log into the dashboard?”</li><li>“When you land on our homepage, what do you think is missing?”</li><li>“As a vehicle owner going through the auth flow, what is unclear about this process?”</li></ul><p>With a fresh set of eyes in the room, we quickly dove into an in-depth conversation about the ideal developer experience of an API-driven product.</p><h3>The results are in!</h3><p>In no time, post-it notes were flying through the room and onto the walls. They were filled with potential features that could exponentially improve a developer’s experience, roadblocks that might come up along the way, and essentially everything in between. When we took a step back and looked at what had been uncovered, we couldn’t have been more excited to get back to work, putting the pedal to the metal towards prioritizing and developing the features we had discussed.</p><p>If there’s anything we learned from our Under the Hood event — and trust us, we learned <strong>a lot</strong> — it’s to know (and listen to!) our audience. And we can’t say it enough: we <strong>loved</strong> getting to better know our audience of engineers, better understand how they work with APIs, and better iterate on our product so that they have the best possible experience moving forward.</p><p>Finally, a huge thanks to <a href="https://www.nea.com/">NEA</a> for having us and to everyone who attended!</p><p>PS: Interested in giving us your feedback or participating in a future workshop? Give us a shout at <a href="/service/mailto:hello@smartcar.com">hello@smartcar.com</a>!</p><p><em>Smartcar is the connected car API that allows mobile and web apps to communicate with connected vehicles across brands (think “check odometer” or “unlock doors.”)</em></p><p><em>Want to take our API for a spin? Check out our </em><a href="https://smartcar.com/docs/"><em>docs</em></a><em> and get started with our </em><a href="https://support.smartcar.com/getting-started/run-our-demo-app"><em>demo app</em></a><em>!</em></p><p><em>Originally published at </em><a href="https://smartcar.com/blog/nea-workshop/"><em>smartcar.com</em></a><em> on September 5, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c13eec65cb26" width="1" height="1" alt=""><hr><p><a href="https://medium.com/smartcar/taking-a-peek-under-the-hood-with-smartcar-c13eec65cb26">Taking a peek “Under the Hood” with Smartcar</a> was originally published in <a href="https://medium.com/smartcar">Smartcar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>