20 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCar records/maintenance logger software
Leading reported evidence
Use app called 'things'
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Use app called 'things'' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Recommend any software' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
Instead of a paper notebook I use notepad on my iPhone (plain text easy to move around)
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Does any use and recommend any software for recording the maintenance history of their cars?
Recommend dealer maintenance intervals + peer / user input
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Presumably it could be programmed with recommended dealer maintenance intervals + peer / user input...
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
A really interesting development in this field would be an app that you can input the make/model/year/mileage of the car and it will *suggest* services and/or recommended maintenance...
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
20 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T133652Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Does any use and recommend any software for recording the maintenance history of their cars? I'm looking for recommendations for Mac-based solutions, or iOS. For extra credit, a solution that syncs between iOS and Mac.
Thanks,
David
I've thought about trying to write an ipad/iphone app for this but figured for sure someone else had already. There are a few out there but I haven't tried them yet.
I would be less interested in making money and more interested in just being able to use it for myself.
Interested in seeing what other people use as well.
Portability is the issue. This is a niche use case and developers come and go. When they stop developing that app there goes your data.
Use excel or another spreadsheet with cloud storage or a simple notepad and a bi see or folder.
It's upgrade proof. (Mostly)
I must be a Luddite (but I work in IT).
I have a notebook in the glove compartment where I log all fuel purchases, oil added, and maintenance or repair items.
Receipts for fuel go in the glovebox notebook, and I have a manila folder in a filing cabinet for repair and parts receipts. The title is stapled to the manila folder, so I can hand the bundle to the buyer, if that day comes.
^ I do the same!
I also use an app called Fuelio that I have been using for a little under a year for all of our vehicles. Has nice graphs.
I do not own an iphone any longer but is free on the Google App store.
I use an app called 'Things'. I don't believe it is available on PC, but you can get it for Mac/iOS and sync between the two. Its a very robust todo list application that allows for projects, scheduling, bullet lists, etc. I setup a 'Porsche' project that has a list of maintenance records, dates, miles as well as sub projects that I plan on tackling.
The reason you're a Luddite is you work in it and you know how sometimes simple is best.
I do same. Instead of a paper notebook I use notepad on my iPhone (plain text easy to move around)
A really interesting development in this field would be an app that you can input the make/model/year/mileage of the car and it will *suggest* services and/or recommended maintenance... Presumably it could be programmed with recommended dealer maintenance intervals + peer / user input... Would take a while to build, but that would be cool... I'm assuming that doesn't exist already?
The Luddite method works best, you get to touch and feel every actual receipt that you add into your record repository. Then the next person does also.
The 35 + year IT professional agrees with the former.
Though I do make entries in the Maintenance book also with notes and references to receipts in the folder.
Mike
