A race organiser asks for the list of your dogs with their microchip and their rabies. A vet wants a dog's journal. A coach wants the plan in a spreadsheet. On the website, all of that already existed; on the phone, a musher who only has a phone had half of it: the entry list and the plan were copied somewhere, which cannot be handed to anyone, and the rest did not exist.

What changes

Five gestures now give a real file, handed to the phone's share sheet — Files, e-mail, a messaging app:

Everything is prepared without a network, except two things: the entry list and the plan's "parameters" file. While the file is being prepared, the button says so ("Preparing the file…") and does not start again if you touch it twice.

What others see, and what they don't

MushMate sends nothing. The file goes where you decide in the phone's sheet, and MushMate does not know where: nobody is notified, nothing is published.

The entry list only speaks of your active dogs: no guest dog, no dog that has left. It gives what an organiser asks for — name, sex, birth, breed, coat, microchip, insurer and policy number, latest rabies — and never the weight, the care notes or a person's name. It stays a file you hand to someone else: read it over first.

A dog's journal is made for you, or for its vet: it holds everything noted for that dog. Nothing about the other dogs of the kennel.

A GPX track is never offered for a session imported from Strava: Strava's agreement reserves its track to the person who imported it, and MushMate does not change that rule.

What the export doesn't do

It is not an Excel file: it is a CSV, which any spreadsheet opens, separated by commas. The headers and the codes (male_neutered, distance_km) stay in English, even in an app set to French: a formula written on distance_km keeps working the day you change the language.

No PDF. The musher's printing pages — rations, insurance, race sheet — stay on the website: that is a separate piece of work, which needs the server to draw the page, and nothing here half-prepares it.

No table on the screen: six columns do not read well on a phone, and that is not the point. The totals go to a spreadsheet, that is all.

The phone's GPX file has no trail name, and its times are the seconds elapsed since the start laid down from 1970: do not look for the outing's date inside the file, it is in its name.

The choices that are not obvious

The entry list refuses to be made offline, whereas the rest of the app works without a network. The phone only knows of your dogs what its last synchronisation gave it: a rabies shot entered this morning on the website might be missing, and an entry list announcing "rabies missing" wrongly is exactly the mistake you don't want to hand an organiser. A plain "Offline" is better than a wrong file.

The totals cover the whole history, not the period shown on the screen. The screen shows a week, a month or the season; the website's file gives the whole history, and the phone gives the same. What you choose at export time is the line: week, month or year. The team and the dogs chosen on the screen do count: under a scope, an outing counts once, with the kilometres of the furthest dog among those you picked — never their sum.

The GPX is not trimmed, whereas the image to share is. An outing's image removes its first and last 500 metres, so as not to show where the team starts from. A GPX is a working file, and a cut track would be an error there: it holds the whole track, start and finish included. The sentence under the button says so before you send.

The plan's parameters need a network. That file says what built the plan, and part of it comes from the model, which the phone does not keep. Rather than write a file with holes, the phone refuses it offline, and the sheet says so under the row ("Needs a connection.").

The same file as the website, not two files that look alike. The website and the phone each make their own file; every rule is written twice and checked against the same cases, whose results are written by the website's own code. A spreadsheet fed by the website one day and by the phone the next does not see the difference. That holds even for a visible flaw: a negative threshold in the "parameters" file is written '-30, with an apostrophe in front — it is the spreadsheets' protection against formulas, and the website puts it on a number too. The phone copied, it did not correct: correcting on one side only would have produced two files.

Three differences show. The day in the file name is your phone's; on the website it is the server's, which can run a day ahead late in the evening. A dog's journal file name is written without accents on the phone (carnet-Elan.csv for Élan), whereas the website keeps them (carnet-Élan.csv). And the GPX track is not the website's, as said above: the phone writes no trail name and dates its points from 1970, where the website writes a name and no times.