<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>The Slicks blog</title>
    <link>https://slicks.app/blog</link>
    <atom:link href="https://slicks.app/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>News, release notes and guides from the makers of Slicks, the kart telemetry app for iPhone, iPad and Mac.</description>
    <language>en</language>
    <lastBuildDate>Thu, 12 Nov 2026 00:00:00 GMT</lastBuildDate>
    <image><url>https://slicks.app/apple-touch-icon.png</url><title>The Slicks blog</title><link>https://slicks.app/blog</link></image>
    <item>
      <title>How to open AiM XRK files on a Mac</title>
      <link>https://slicks.app/blog/how-to-open-aim-xrk-files-on-mac</link>
      <guid isPermaLink="true">https://slicks.app/blog/how-to-open-aim-xrk-files-on-mac</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
      <description>RaceStudio 3 runs on Windows, but your XRK files don't have to. How to open AiM and MyChron data on a Mac, iPhone or iPad, step by step.</description>
      <category>Guides</category>
      <category>AiM</category>
      <content:encoded><![CDATA[<p>You come off the track, the MyChron has a full session on it, and the laptop in your bag is a MacBook.
You copy the file over, double-click it, and macOS has no idea what an <code>.xrk</code> is. You ask around the paddock
and somebody tells you to borrow a Windows laptop.</p>
<p>You don&#39;t need one. Here&#39;s how to open AiM data on a Mac, and on your iPhone and iPad while you&#39;re at it.</p>
<h2 id="what-is-an-xrk-file">What is an XRK file?</h2>
<p>An XRK file is the session your AiM logger recorded, in AiM&#39;s own format. It holds every lap, the GPS
position many times a second, and every channel the logger was wired for: RPM, exhaust temperature, water
temperature and whatever else you&#39;ve plugged in. MyChron loggers write them, and so do AiM&#39;s other loggers.</p>
<p>An <strong>XRZ</strong> file is the same session, compressed. You don&#39;t need to unzip it first; anything that reads XRK
should read XRZ too.</p>
<p>AiM&#39;s own software for reading these files is RaceStudio 3, and it runs on Windows. That&#39;s why so many Mac
owners end up running Windows in a virtual machine, borrowing a teammate&#39;s laptop, or (most often) just not
looking at their data at all.</p>
<h2 id="can-you-open-xrk-files-on-a-mac">Can you open XRK files on a Mac?</h2>
<p>Yes. <a href="https://apps.apple.com/ca/app/slicks/id6746713889">Slicks</a> opens XRK and XRZ files on the Mac with
nothing from AiM installed. It reads the file on your Mac itself, so it works with no internet connection,
and it&#39;s free. The same download runs on iPhone and iPad, and your sessions sync between them.</p>
<h2 id="step-1-get-the-file-off-the-logger">Step 1: get the file off the logger</h2>
<p>This part still happens with AiM&#39;s own tools, the same way you download sessions today. If that&#39;s
RaceStudio 3 on a Windows laptop, the good news is it keeps every session it downloads as an <code>.xrk</code> file.
Search that laptop for <code>.xrk</code> and you&#39;ll probably find your whole season sitting there.</p>
<p>Then get the files onto your Mac however suits you: a USB stick, a shared folder (iCloud Drive, Dropbox,
Google Drive), or an email to yourself. If a teammate pulls everyone&#39;s data, ask them for the XRK files
rather than screenshots.</p>
<h2 id="step-2-open-it-in-slicks">Step 2: open it in Slicks</h2>
<p>Any of these work, and you can bring in a whole folder of sessions at once:</p>
<ul>
<li><strong>Drag the files onto the sessions list</strong> in the sidebar.</li>
<li><strong>File › Import Sessions…</strong> (or press ⌘O) and pick them.</li>
<li><strong>Right-click a file in Finder › Open With › Slicks.</strong></li>
</ul>
<p>Each session lands with its track, driver and date read from the file. When you bring in a single new
session, Slicks first asks what you changed on the kart: gearing, tire pressures, carb, axle, track width,
caster, new tires. It asks before you see any numbers, on purpose. Once you&#39;ve seen a fast lap, it&#39;s very
easy to remember the change that &quot;obviously&quot; made it fast.</p>
<h2 id="what-you-ll-see">What you&#39;ll see</h2>
<p><img src="https://slicks.app/hero/app-2048.webp" alt="The Slicks Mac app with a list of kart sessions grouped by weekend on the left and a session's fastest lap drawn on a map of the track in the colours of its speed" width="2048" height="1286" loading="lazy" decoding="async"></p>
<ul>
<li><strong>Summary</strong>: every lap split into sectors, your best lap, the theoretical best, the corners that cost you
the most time, and your engine&#39;s peaks against the window your tuner gave you.</li>
<li><strong>Track</strong>: your laps drawn on a real map of the circuit, coloured by speed or by any channel the logger
recorded.</li>
<li><strong>Laps</strong>: one channel charted across every timed lap, so you can see a trend over a session.</li>
<li><strong>Channels</strong>: every channel against time or distance. Hover anywhere for the exact reading.</li>
</ul>
<p>New to all of these? Our <a href="https://slicks.app/blog/how-to-read-kart-telemetry">beginner&#39;s guide to reading kart telemetry</a>
walks through what each one tells you and what to look at first.</p>
<h2 id="on-iphone-and-ipad">On iPhone and iPad</h2>
<p>Your Mac is great at home. At the track, your phone is already in your pocket. On iPhone and iPad you can
open an XRK file straight from the Files app, or AirDrop it over from your Mac. Sign in on each device and a
session imported on one shows up on the others.</p>
<h2 id="no-file-to-try-it-with">No file to try it with?</h2>
<p>Open Slicks with an empty library and tap <strong>Try a Sample Session</strong>. It&#39;s a real kart session with real laps,
so you can poke around everything above before your next track day.</p>
<h2 id="quick-answers">Quick answers</h2>
<p><strong>Do I need RaceStudio installed on the Mac?</strong> No. Slicks reads the files itself.</p>
<p><strong>Does it work with MyChron files?</strong> Yes. Slicks reads the XRK and XRZ files AiM loggers record, MyChron
included.</p>
<p><strong>Does it need an internet connection?</strong> No. Your sessions open and show their numbers offline. Syncing
catches up when you&#39;re back online.</p>
<p><strong>Can Slicks set up my logger?</strong> No. Configuring the logger stays with AiM&#39;s software. Slicks is for reading
what it recorded.</p>
<p><strong>Is it really free?</strong> Yes. One free download for iPhone, iPad and Mac.</p>
<p>Got a file that won&#39;t open? Send it to <a href="mailto:hello@slicks.app">hello@slicks.app</a> and we&#39;ll take a look.</p>
]]></content:encoded>
    </item>
    <item>
      <title>How to read kart telemetry: a beginner's guide</title>
      <link>https://slicks.app/blog/how-to-read-kart-telemetry</link>
      <guid isPermaLink="true">https://slicks.app/blog/how-to-read-kart-telemetry</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
      <description>What your MyChron actually records, the four charts worth learning first, and a 90-second routine for reading your data between sessions.</description>
      <category>Guides</category>
      <category>AiM</category>
      <content:encoded><![CDATA[<p>You did twenty laps. Your best was a 49.7. The kid in the next pit did a 49.3 on the same tires, and
you&#39;ve got no idea where those four tenths went.</p>
<p>Your logger does. It recorded every lap from every angle. Reading it is way less complicated than the wall
of squiggly lines makes it look. You need maybe four charts, and you can get something useful out of them in
the ninety seconds between coming off the track and somebody asking what you want to change.</p>
<p>This guide uses MyChron data, but the ideas work for any kart logger.</p>
<h2 id="what-does-a-kart-data-logger-record">What does a kart data logger record?</h2>
<p>Most of it comes from two places: the GPS and the wires you&#39;ve plugged in.</p>
<ul>
<li><strong>GPS</strong> gives you where the kart was, many times a second. From that you get <strong>speed</strong>, your <strong>line</strong> on
the track, and the forces: <strong>lateral g</strong> (how hard you&#39;re cornering) and <strong>longitudinal g</strong> (how hard
you&#39;re braking and accelerating).</li>
<li><strong>Sensors</strong> give you <strong>RPM</strong> from the plug lead, and usually <strong>exhaust gas temperature (EGT)</strong> and <strong>water
temperature</strong>. Some setups add more.</li>
<li><strong>Lap times</strong> come from the logger spotting each time you cross the start line.</li>
</ul>
<p>That&#39;s it. Everything below is just these few things drawn in different ways.</p>
<h2 id="start-with-your-lap-times">Start with your lap times</h2>
<p>Before any chart, look at the list of laps. Two numbers matter more than your best lap:</p>
<ul>
<li><strong>How far your typical lap is from your best.</strong> If your best is a 49.7 and most laps are 50.4, you
don&#39;t have a speed problem yet. You have a doing-it-every-lap problem, and that&#39;s good news, because
you&#39;ve already shown you can drive the fast lap.</li>
<li><strong>Which laps to ignore.</strong> Out laps, in laps, laps in traffic, the lap you went off. Leave them out of
every comparison. Comparing yourself with a lap where you were stuck behind someone teaches you nothing.</li>
</ul>
<h2 id="find-where-on-the-track-sectors">Find where on the track: sectors</h2>
<p>A sector is a slice of the lap. Split every lap into, say, three slices, time each one, and now &quot;I&#39;m four
tenths off&quot; becomes &quot;I&#39;m three tenths off in the middle of the lap.&quot; That&#39;s something you can actually work
on.</p>
<p>Add up your fastest time through each sector, from any laps, and you get your <strong>theoretical best</strong>: the lap
you&#39;d do if you strung your best bits together. The gap between that and your actual best lap is free time.
You&#39;ve already driven every part of it. We wrote a whole post on
<a href="https://slicks.app/blog/theoretical-best-lap">the theoretical best lap and how to use it</a>.</p>
<h2 id="the-speed-trace-is-the-chart-that-matters-most">The speed trace is the chart that matters most</h2>
<p>If you learn one chart, learn this one. It&#39;s your speed (up the side) along the lap (across the bottom).
The peaks are the ends of the straights and the dips are the corners.</p>
<p>For every corner, look at three things:</p>
<ol>
<li><strong>Where the line starts falling.</strong> That&#39;s your braking point. If it falls earlier than on your fast
lap, you&#39;re braking earlier.</li>
<li><strong>How low the dip goes.</strong> That&#39;s your minimum speed through the corner. This is the big one in a kart.
Karts don&#39;t have much power, so every km/h you scrub off in the corner has to be earned back down the
whole next straight.</li>
<li><strong>How quickly the line climbs out.</strong> A slow climb usually means you were late back on the throttle, or
the kart was still sliding or bogging when you were.</li>
</ol>
<p>A really common pattern for newer drivers: braking too early and too much, so the dip is deeper and wider
than it needs to be. On the trace it looks like a big &quot;V&quot; where a faster driver has a shallow &quot;U&quot;.</p>
<h2 id="compare-two-laps">Compare two laps</h2>
<p>One trace on its own is hard to judge. Two traces on top of each other tell you almost everything. Pick
your best lap as the <strong>reference</strong> and lay another lap over it. Where the lines split apart is where the
laps were different.</p>
<p>The other line to watch is the <strong>time delta</strong>: how far ahead or behind the second lap is at every point
around the track. When it climbs, that lap is losing time. When it falls, it&#39;s gaining.</p>
<p>Here&#39;s the trick: <strong>find the first place the gap grows.</strong> Lose two km/h through turn three and you&#39;ll be
slower all the way down the next straight. The delta keeps climbing there, but the straight isn&#39;t the
problem. Turn three is.</p>
<p>In Slicks you pick two laps and get both speed traces, the delta, and a cursor that moves around the map as
you scrub, so you can see exactly where on the track you&#39;re looking.</p>
<h2 id="let-the-app-rank-your-corners">Let the app rank your corners</h2>
<p>Doing all of the above for every corner gets slow. Slicks does a version of it for you: it lines every lap
up against your fastest and ranks the corners that cost the most, with how many tenths, the speed
difference and where on the track. Start with the top one and ignore the rest for now. Fixing one corner
per session is a lot more than most people manage.</p>
<h2 id="look-at-the-track-map">Look at the track map</h2>
<p>The map shows your laps drawn on the real circuit and coloured by speed. It&#39;s the quickest way to get a
feel for the whole lap. Change the colour to <strong>lateral g</strong> and you see how hard you were cornering
everywhere. A corner that stays pale while the rest of the track lights up is one you&#39;re not committing to.</p>
<p><img src="https://slicks.app/hero/phone-963.webp" alt="Slicks on an iPhone showing a kart session's fastest lap drawn on a satellite map of the track, with the lap time underneath and tabs for laps, time loss and sectors" width="963" height="2011" loading="lazy" decoding="async"></p>
<h2 id="check-the-engine">Check the engine</h2>
<p>Your engine builder or tuner usually gives you a window for each reading, so you&#39;re mostly checking you&#39;re
inside it:</p>
<ul>
<li><strong>Peak RPM.</strong> If you&#39;re hitting the limiter well before the end of the longest straight, your gearing is
probably too short (a smaller rear sprocket gives you a taller gear). If you never get near the RPM where
the engine makes its power, it&#39;s probably too tall.</li>
<li><strong>EGT.</strong> Exhaust temperature tells you how rich or lean the engine&#39;s running. Too hot can hurt the engine,
too cold usually means you&#39;re leaving power on the table. This is what carb adjustments chase.</li>
<li><strong>Water temperature.</strong> Too cold or too hot and the engine won&#39;t make its best power. Tape on the radiator
is the usual fix.</li>
</ul>
<p>Slicks shows these peaks against your tuner&#39;s window in plain words as well as colour, with presets for
Rotax, IAME X30 and KA100, Vortex Rok GP and Yamaha KT100.</p>
<h2 id="a-90-second-routine-between-sessions">A 90-second routine between sessions</h2>
<p>When you&#39;re back in the pits with the next session coming up, do this:</p>
<ol>
<li><strong>Best lap and theoretical best.</strong> How big is the gap? Has it shrunk since the last session?</li>
<li><strong>The corner that cost you most.</strong> One corner. Look at its braking point and minimum speed on the trace.</li>
<li><strong>Engine peaks.</strong> Inside the window? If not, that&#39;s the change to make.</li>
<li><strong>Write down what you&#39;re changing.</strong> One thing at a time, so next session you know what worked.</li>
</ol>
<p>That&#39;s all. Save the deep dive for the drive home.</p>
<h2 id="mistakes-everyone-makes">Mistakes everyone makes</h2>
<ul>
<li><strong>Changing two things at once.</strong> Gearing and pressures in the same session, and now you&#39;ll never know
which one helped.</li>
<li><strong>Comparing against a traffic lap.</strong> Pick clean laps, every time.</li>
<li><strong>Treating the theoretical best as a target you have to hit.</strong> It&#39;s a pointer to where the time is, not a
lap time you&#39;re owed.</li>
<li><strong>Trusting tiny wobbles.</strong> GPS gets a little vague next to tall buildings and under trees. Look at the big
shapes, not every small kink in the line.</li>
</ul>
<h2 id="try-it-with-real-data">Try it with real data</h2>
<p><a href="https://apps.apple.com/ca/app/slicks/id6746713889">Slicks</a> is free for iPhone, iPad and Mac. It opens the
XRK files your AiM logger records, MyChron included, with no AiM software. No file yet? Open it with an
empty library and tap <strong>Try a Sample Session</strong> to follow along with a real session. And if your data lives
on a Mac, here&#39;s <a href="https://slicks.app/blog/how-to-open-aim-xrk-files-on-mac">how to open AiM XRK files on a Mac</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Slicks 1.4: your kart and engine on one page</title>
      <link>https://slicks.app/blog/slicks-1-4</link>
      <guid isPermaLink="true">https://slicks.app/blog/slicks-1-4</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
      <description>Slicks 1.4 puts your engine's peaks, every channel's range and your kart setup on one Setup page, plus a new app icon with dark and tinted looks.</description>
      <category>Release notes</category>
      <content:encoded><![CDATA[<p>Slicks 1.4 is out on iPhone, iPad and Mac. The big one is a new <strong>Setup</strong> page that puts everything about
the kart and its engine in one place. There&#39;s also a new icon.</p>
<h2 id="a-setup-page-for-the-kart-and-the-engine">A Setup page for the kart and the engine</h2>
<p>When you come off the track, two questions come up straight away: was the engine happy, and what did we
change last time? Before 1.4 the answers lived in different parts of the session. Now they sit together.</p>
<p>The session screen&#39;s pages are now <strong>Laps</strong>, <strong>Time Loss</strong>, <strong>Sectors</strong>, <strong>Setup</strong> and <strong>Notes</strong>. Setup
has, from top to bottom:</p>
<ul>
<li><strong>Your engine&#39;s peaks against your tuner&#39;s window.</strong> Peak RPM, exhaust temperature and water temperature,
in plain words as well as colour, so &quot;is this OK?&quot; takes a glance.</li>
<li><strong>Every channel&#39;s range.</strong> The lowest and highest reading for everything your logger recorded.</li>
<li><strong>What you changed on the kart.</strong> Gearing, pressures, carb, axle, track width, caster, tires: whatever you
wrote down when you imported the session.</li>
</ul>
<p>Seeing your engine&#39;s peaks right next to what you changed is the point. Went up a tooth on the rear
sprocket? The RPM peak that comes with it is right there.</p>
<p>On iPad, the engine&#39;s peaks sit in the inspector beside the setup, so you can keep them open while you work
through the laps.</p>
<h2 id="a-new-icon">A new icon</h2>
<p>Slicks has a new app icon, with dark and tinted looks for your Home Screen.</p>
<h2 id="usage-analytics-and-how-to-turn-them-off">Usage analytics, and how to turn them off</h2>
<p>Slicks now counts which screens get used, so we know what to work on next. It never records who you are,
what you drove or where. You can turn it off under <strong>Pits › Share Usage Analytics</strong>.</p>
<h2 id="get-it">Get it</h2>
<p>Update from the App Store, or <a href="https://apps.apple.com/ca/app/slicks/id6746713889">download Slicks free</a> for
iPhone, iPad and Mac. Want new builds before they hit the App Store? Join the
<a href="https://testflight.apple.com/join/dF2CCHeY">TestFlight beta</a>.</p>
<p>Something not working, or an idea for the next one? Tell us at <a href="mailto:hello@slicks.app">hello@slicks.app</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Theoretical best lap: what it means in karting</title>
      <link>https://slicks.app/blog/theoretical-best-lap</link>
      <guid isPermaLink="true">https://slicks.app/blog/theoretical-best-lap</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
      <description>Your theoretical best is the lap you've already driven in pieces. How it's worked out, why you'll rarely hit it, and how to use it to find time.</description>
      <category>Guides</category>
      <content:encoded><![CDATA[<p>Every karter has had the session where everything clicked, just never all in the same lap. You nailed the
hairpin on lap 4, the fast stuff on lap 7 and the last corner on lap 9. Your theoretical best is what you
get if you glue those bits together.</p>
<p>It&#39;s one of the most useful numbers your data gives you, and one of the most misread. Here&#39;s how it works
and how to actually use it.</p>
<h2 id="what-is-a-theoretical-best-lap">What is a theoretical best lap?</h2>
<p>A theoretical best lap is the sum of your fastest time through each sector of the track, taken from any
laps in the session. You&#39;ll also see it called an <strong>ideal lap</strong>, <strong>optimal lap</strong> or <strong>ultimate lap</strong>. They
all mean the same thing.</p>
<p>It&#39;s not a guess about what you could do with a better kart or more practice. Every piece of it is
something you actually drove that day.</p>
<h2 id="how-is-it-worked-out">How is it worked out?</h2>
<p>Say you split the lap into three sectors and did three clean laps:</p>
<table>
<thead>
<tr>
<th>Lap</th>
<th>Sector 1</th>
<th>Sector 2</th>
<th>Sector 3</th>
<th>Lap time</th>
</tr>
</thead>
<tbody><tr>
<td>4</td>
<td><strong>16.35</strong></td>
<td>17.10</td>
<td>16.62</td>
<td>50.07</td>
</tr>
<tr>
<td>7</td>
<td>16.49</td>
<td><strong>16.86</strong></td>
<td>16.71</td>
<td>50.06</td>
</tr>
<tr>
<td>9</td>
<td>16.41</td>
<td>17.02</td>
<td><strong>16.51</strong></td>
<td><strong>49.94</strong></td>
</tr>
</tbody></table>
<p>Your best lap is lap 9, a 49.94. Now take the best time in each column:</p>
<p>16.35 (lap 4) + 16.86 (lap 7) + 16.51 (lap 9) = <strong>49.72</strong></p>
<p>That&#39;s your theoretical best. You&#39;re 0.22 seconds away from a lap you&#39;ve already driven, in pieces.</p>
<h2 id="the-gap-tells-you-where-to-look">The gap tells you where to look</h2>
<p>The magic isn&#39;t the number itself, it&#39;s the gap, and which sectors it comes from. Compare your best lap with
the best in each sector:</p>
<ul>
<li>Sector 1: 16.41 vs 16.35, <strong>0.06</strong> to find</li>
<li>Sector 2: 17.02 vs 16.86, <strong>0.16</strong> to find</li>
<li>Sector 3: already your best</li>
</ul>
<p>So most of the time is in sector 2. On lap 7 you went through it 0.16 seconds quicker than on your best lap.
Whatever you did there, you&#39;ve already done it once. Now go and find out what it was.</p>
<p>Bring up lap 7 and lap 9 side by side and look at sector 2 on the speed trace. Did you brake later? Carry
more speed through the middle of the corner? Get on the throttle sooner? (Our
<a href="https://slicks.app/blog/how-to-read-kart-telemetry">beginner&#39;s guide to reading kart telemetry</a> covers how to read the
trace.)</p>
<h2 id="big-gap-or-small-gap">Big gap or small gap?</h2>
<ul>
<li><strong>A big gap</strong> (more than a few tenths) means your best bits are good, you&#39;re just not stringing them
together. That&#39;s consistency, and you can fix it with your own data. Pick the sector with the biggest gap
and work on it.</li>
<li><strong>A small gap</strong> means you&#39;re already driving close to your own best in every sector. That&#39;s a good spot,
but your own data can&#39;t show you much more. More speed will come from somewhere else: a different line, a
setup change, or comparing yourself with a faster driver&#39;s lap.</li>
</ul>
<h2 id="why-you-ll-rarely-hit-it-exactly">Why you&#39;ll rarely hit it exactly</h2>
<p>Don&#39;t beat yourself up if you never match it. It&#39;s built to be a bit optimistic:</p>
<ul>
<li><strong>The pieces come from different laps,</strong> with different tire temperatures, track grip and traffic around
you.</li>
<li><strong>Sectors aren&#39;t independent.</strong> A great exit from one corner can set up a compromised entry to the next.
Your best sector 2 might only have been possible because of a slower end to sector 1.</li>
<li><strong>More sectors means a faster theoretical best.</strong> Split the lap into ten slices and you&#39;re picking the
best of ten pieces, not three, so the number drops. Only compare theoretical bests worked out with the
same number of sectors.</li>
</ul>
<p>That last one is easy to miss. If your theoretical best suddenly got faster, check you didn&#39;t just change
how many sectors you&#39;re using.</p>
<h2 id="can-you-beat-your-theoretical-best">Can you beat your theoretical best?</h2>
<p>Yes, and that&#39;s the goal. It&#39;s the best of <em>today&#39;s</em> laps. Find a better line, or a setup change that
works, and you&#39;ll set new sector bests and push the whole thing lower. Use it as a pointer to where the time
is, not a ceiling.</p>
<h2 id="how-many-sectors-should-you-use">How many sectors should you use?</h2>
<p>Three is a great place to start on most kart tracks. It&#39;s few enough that each sector is a real chunk of
the lap and a sector time means something.</p>
<p>Once you know which part of the track you&#39;re losing time in, go up to five or six to narrow it down to a
corner or two. Past that, each sector gets so short that small differences in where the logger thinks the
line is start to matter more than your driving.</p>
<h2 id="theoretical-best-in-slicks">Theoretical best in Slicks</h2>
<p><a href="https://apps.apple.com/ca/app/slicks/id6746713889">Slicks</a> works out your theoretical best from the XRK file
your AiM logger records, the moment you open it, even with no signal. Every lap is split into equal-distance
sectors, anywhere from 2 to 10, and each lap&#39;s sectors are lined up against the best of the session, so you
can see which lap set which sector and where your best lap lost out. Change the number of sectors and
everything updates.</p>
<p>Because Slicks makes its sectors from the GPS line rather than the track&#39;s timing loops, they won&#39;t line up
with the official sectors on the timing screen. That&#39;s fine. They&#39;re consistent from lap to lap, and that&#39;s
what matters for finding time.</p>
<p>It&#39;s free for iPhone, iPad and Mac. No session to try it on? Tap <strong>Try a Sample Session</strong> in an empty
library.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Why we built Slicks</title>
      <link>https://slicks.app/blog/why-we-built-slicks</link>
      <guid isPermaLink="true">https://slicks.app/blog/why-we-built-slicks</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
      <description>Kart data shouldn't need a Windows laptop and an evening to read. Why we built Slicks, a free kart telemetry app for iPhone, iPad and Mac.</description>
      <category>Behind the scenes</category>
      <content:encoded><![CDATA[<p>Here&#39;s how kart data usually goes. The logger records every lap in amazing detail. Then the session ends,
the next one&#39;s in forty minutes, and the data stays on the logger, because looking at it means a Windows
laptop, a cable, a bit of software and more patience than anyone has in a hot paddock. By the time it&#39;s
open, the moment to act on it has gone.</p>
<p>Plenty of drivers try it a few times, get buried in squiggly lines and go back to &quot;felt fast.&quot;</p>
<p>We built <a href="https://apps.apple.com/ca/app/slicks/id6746713889">Slicks</a> to fix that.</p>
<h2 id="ninety-seconds-between-heats">Ninety seconds between heats</h2>
<p>The paddock doesn&#39;t give you an evening. It gives you about ninety seconds before someone asks what you want
to change. So Slicks opens a session on the numbers that answer that question:</p>
<ul>
<li><strong>Sectors</strong>, and your theoretical best: how much time is already in your laps.</li>
<li><strong>Where the time went</strong>: the corners that cost you the most, ranked.</li>
<li><strong>The engine</strong>: peak RPM, exhaust and water temperatures against the window your tuner gave you.</li>
</ul>
<p>Everything else (lap comparisons, the track map, every channel) is one tap further in for when you&#39;ve got
time.</p>
<h2 id="on-the-devices-you-already-carry">On the devices you already carry</h2>
<p>You&#39;ve already got a phone in your pocket. Plenty of karters have a Mac at home and an iPad in the van. So Slicks
is one app for iPhone, iPad and Mac. Import a session on any of them and it shows up on the others.</p>
<p>And because the paddock often has no signal, the reading happens on your device. Your sectors, theoretical
best and session summary are there with no connection. Sync just catches up later.</p>
<h2 id="no-aim-software-needed">No AiM software needed</h2>
<p>AiM loggers, MyChron included, save sessions as XRK files in AiM&#39;s own format. To open them without AiM&#39;s
software, we had to work out how that format is put together ourselves. Slicks reads XRK and XRZ files
directly, on the device, with nothing else installed.</p>
<p>Getting the file off the logger still happens with AiM&#39;s own tools, and so does setting up the logger.
Slicks is for reading what it recorded.</p>
<h2 id="your-data-stays-yours">Your data stays yours</h2>
<p>Your sessions are private to your account. If you want a coach or teammate to see one, you share it with a
link, and you can switch that link off any time. The original file never goes out through a link. Slicks
has no ads.</p>
<h2 id="free">Free</h2>
<p>Slicks is free on the App Store: one download for iPhone, iPad and Mac.</p>
<h2 id="what-this-blog-is-for">What this blog is for</h2>
<p>We&#39;ll post here a couple of times a week:</p>
<ul>
<li><strong>Guides</strong> to reading your data: braking points, sectors, comparing laps, gearing and engine temperatures.
The <a href="https://slicks.app/blog/how-to-read-kart-telemetry">beginner&#39;s guide to reading kart telemetry</a> is the place to start.</li>
<li><strong>Release notes</strong> for every version, with what changed and why.</li>
<li><strong>Behind the scenes</strong>: how Slicks reads AiM&#39;s files, and how it&#39;s built.</li>
</ul>
<p>Every post is in the <a href="https://slicks.app/blog/feed.xml">RSS feed</a>. Got a question you want answered in a post? Send it to
<a href="mailto:hello@slicks.app">hello@slicks.app</a>.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
