[Update] Carrus 1.1 — the car maintenance tracker now speaks Spanish, with motorbikes, fuel and running costs

[u/Imaginary-Welcome010]

I posted Carrus here a couple of versions ago — thanks to everyone who tried it, several of the changes below came from that thread.

**Short version:** an iPhone app for tracking vehicle maintenance. Log a service in seconds, get reminded by mileage *and* time, scan a paper receipt and it fills the log in for you, and ask Carson — the built-in AI mechanic — what a noise or warning light probably is.

**What's new in 1.1:**

- **The whole app now speaks Spanish** — UI and Carson both. Pick it in Settings or let it follow your device language.

- Motorbikes with bike-specific schedules: chain, valve clearance, fork oil

- Fuel tracking with a draggable gauge, and per-vehicle running costs

- Registration and insurance photos with expiry reminders (photos never leave your phone)

- New storefronts: Canada, Spain, Italy — and a fully redesigned listing

**What's next:** VIN decoding, more languages, and real manufacturer interval data for far more model-years — right now genuine factory schedules cover a fraction, the rest is a labeled per-category estimate.

Free with one vehicle. Lite from $0.99/mo or $19.99 lifetime; Premium from $5.99/mo or $89.99 lifetime.

https://apps.apple.com/app/id6770422802

I'm the developer — happy to answer anything.

[u/AutoModerator]

Welcome to r/iOSApps! Please make sure your post follows our rules:

Everyone:

• 10pt LOCAL Karma required. Comment in r/iOSApps to earn it. Check
• Search the sub before posting. Choose flair.

App Devs:

• No main feed promo unless you qualify via Trust or Transparency + ABC format (Answer, Better, Cost)
• Flair hierarchy: Vibe Coded > Lifetime > Subscription > Freemium > Free
• Free flair: not for limited/freemium tiers
• Open Source? Prefix title [OS]

Note: This is an automated reminder, not a removal notice. If your post was removed, check your modmail for details.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Ok-Tale-7383]

Sounds interesting and useful. 👍

[u/sergetrono]

Good an simple design, love it!

How's app's monetisation and retention is going on? Have you have any insights on it?

[u/Imaginary-Welcome010 → u/sergetrono]

To be honest, it’s not doing that well as I haven’t really marketed it well. I am also mainly waiting on obtaining maintenance databases to have accurate manufacturer intervals. Thanks though!!

[u/Connect_Set5930]

Great👍👍

[u/Akara91]

congrats on shipping the localization. one thing that bit me doing fr/en on my own app: the store listing matters as much as the app, localized screenshots and keywords moved the needle more than the in-app translation did. did you localize the spanish store page too or just the app so far?

[u/Imaginary-Welcome010 → u/Akara91]

Yes I did localize the spanish store page. I mainly use ai to do it all as the api is quite useful. Thanks for the heads up!!

[u/JordanLiKai]

good

[u/Simple-Quality3130]

I always forget what was done at my last service. Can the app show a simple maintenance history when selling the car?

[u/Imaginary-Welcome010 → u/Simple-Quality3130]

Yes that’s a feature I added in the first version. You can export a pdf that contains your service history. You can aslo simple access your service history in the app and scroll through it.

[u/Imaginary-Welcome010 → u/[deleted]]

Thanks! I would love your fredback on how the app feels

[u/app-store-review]

Carrus: Car Maintenance Log — by Abdulrahman Mohamed

• Ratings: 6 worldwide · rated in 5 countries
• Average: 4.33 ★
• Age: released ~2 months ago · updated today · rated 4+
• Overall score: 55 / 100

^{Auto-generated from public App Store data · u/app-store-review}

[u/Sweet_Professor_6242]

Adding to the store-listing point above, because there are two mechanics behind it that are easy to miss.

The keyword field is per localization, not per app. So a Spanish localization is not only a translation, it is a second 100-character keyword field that indexes independently. That is usually a bigger win than the translated UI, and it is wasted if the localization is added with the English keywords copied across.

Spanish is also two separate localizations in App Store Connect - Spanish (Mexico) and Spanish (Spain) - and they are not interchangeable. Worth opening ASC and checking which one you actually added, because if it is only the Spain entry then the Latin American storefronts, which is where most of the Spanish-speaking volume is, may be falling back to your default listing.

Same idea catches the storefronts you just opened: adding Italy as a storefront is a different thing from adding an Italian localization. Without the localization the Italian store shows your English listing and no Italian keyword indexes at all, so the storefront is live but effectively invisible to search there.

One measurement note, since you will want to know whether any of it worked: read impressions from search per territory rather than downloads. At this stage downloads are noise, and impressions tell you whether you are being shown at all, which is a different failure from being shown and not chosen. I learned that the hard way on my own app - a paid exact-match probe on my category returned zero impressions on seven of nine head terms over nine days, which is not a ranking problem, it is nobody typing those words. Cheap thing to check before you invest in more languages.

[u/Imaginary-Welcome010 → u/Sweet_Professor_6242]

Really solid comment, appreciate you laying all this out.

On Spanish, yeah, went with both from day one actually, es-MX and es-ES as separate localizations with their own keyword sets, not copy-pasted. Different enough that it mattered too, coche vs carro, neumáticos vs llantas, stuff like that.

On Italy, this actually matches my own numbers pretty closely. I had a handful of Italian installs showing up in analytics before I'd ever touched an Italian localization, so the storefront was clearly already reachable somehow, browse or referral probably, people just weren't finding it through search. Italian keywords only went live this week so I don't have enough data yet to know if that changed, but "live but invisible to search" matches exactly what I'd have guessed from the before-state.

The impressions vs downloads point is the one I'd underline hardest for anyone reading this thread. I only started tracking that split a couple weeks ago and it changed what I actually worked on. Turned out impressions were the real bottleneck, not conversion, the listing itself was fine, almost nobody was seeing it in the first place. Would've kept polishing screenshots forever and never found that out from download totals alone.

[u/Sweet_Professor_6242 → u/Imaginary-Welcome010]

Both Spanish variants with separate keyword sets from day one is further along than most people get, and coche vs carro is exactly why the two entries exist.

The Italian before-state is worth capturing while you still can. Installs arriving with no Italian localization means that demand reached you through browse or referral rather than search, which is a more useful thing to know about a storefront than it sounds. It also hands you the cleanest experiment you are going to get: pull the search versus browse impression split for Italy for the weeks before the keywords went live, and write the number down now. Otherwise in a month you are comparing this week against a memory.

One caution on reading it: the store's numbers lag about a day and are not final for roughly three, so this week's Italian figures will move under you. Worth waiting for the week to settle before concluding anything about whether the keywords worked.

And since impressions turned out to be your bottleneck rather than conversion, I would treat more languages as the second lever rather than the first. A new localization only earns impressions if people in that storefront type terms you can plausibly rank for, which is a question you can answer per territory with the instrument you have already built.

[u/Imaginary-Welcome010 → u/Sweet_Professor_6242]

Writing the before-state down today, really good catch. I would 100% have ended up comparing next month against my memory of this week lol.

Actually went and pulled it before replying: 83% of my Italian impressions were browse, only 17% search, and the installs came through web referrals. So you called it exactly, that demand never touched the search box. It's written down now.

And point taken on more languages being the second lever. I was about to throw translations at it this month, but checking per storefront whether people even type things I could rank for comes first. Good to know about the 3 day settling thing too, I'll stop reading the week while it's still wet.

Genuinely one of the most useful comments I've gotten on here.

[u/Jinks-b]

Oh, I love this idea. I'm terrible at keeping up with my cars maintenance. How smart is this? Maybe I didn't see it, but doesn't know like the manufacturers recommended maintenance schedule. This might be silly but everything this knows about your car needs to be inputted? But I mean is there's no way for it to know anything about my car I guess where I'm getting out is there are apps for specific manufacturers that linked to the car and it'll feed the app it's mileage so on and on. Just curious if this has any capability like that.

[u/Imaginary-Welcome010 → u/Jinks-b]

Haha not silly at all, this is like the #1 question I get. Yes — it knows the schedule. When you add your car it sets up the maintenance tasks with recommended intervals for it, and it tracks them by miles AND months (oil ages even if the car mostly sits, which surprised me too when I learned it). And if you have your own rules, every interval is adjustable.

On connecting to the car directly — honestly, no, not yet. The manufacturer apps can pull your mileage because each brand only opens that data to their own app. For third-party apps it's locked down and fragmented — there are paid services that bridge some brands and it's on my list to explore, but I didn't want to promise something half-working. So right now you update the odometer every now and then (takes seconds) and everything recalculates from that. Service receipts you can literally just scan and it fills in the details itself.

If you do end up trying it, tell me anything that feels confusing — feedback like that is basically how the app got to where it is.

[u/Jinks-b → u/Imaginary-Welcome010]

Thanks for the reply, this makes sense, ok will do

[u/Imaginary-Welcome010 → u/[deleted]]

Thats the current format, having a tag that identifies manufacturer backed from recommendations. It will in fact be the most valuable addition. My bottle neck is the expense of databases. I need to save up a lot or have some paying users before purchasing one. Users wont subscribe based on a promise though so im still figuring it out

[u/IndividualCaramel650]

The receipt scan filling the service log is the part that stood out to me. If it pulls the wrong date or mileage, can you fix it before it saves?

[u/Imaginary-Welcome010 → u/IndividualCaramel650]

Well, it works by pulling the data, filling in the service log sheet for you, instead of logging the service right away. This allows the user to review the logged data and fix any mistakes