Version 3.13.0

3.13.0 is a fix release. Most of it is about searching outside the English-speaking world, where the results were often unrelated to the job you asked for, and where jobs close to you were being dropped before you ever saw them. The rest cleans up things in the app that quietly wasted your time.

Searching in Europe

• Your first search in a new country now asks in that country's language. Adding Budapest, Prague or Kraków and pressing Search Now used to send only the English job title on that first run, and the European job board answered with whatever it could match: office, cleaning, gardening and sales jobs in reply to a nursing search. The local wording is now worked out before the search runs, so the first search is as good as the second.
• Results have to be related to what you searched for. A job is only kept when its title shares a real word with your search. That stops a stray match on a fragment such as "ICU" bringing back a hairdresser or a butcher.
• A general word is not a match on its own. German "Fachkraft" and French "diplômé" mean "skilled worker" and "qualified", and they appear in thousands of unrelated job titles. Searching for a dialysis nurse in Berlin was returning warehouse, workplace-safety and dry-lining jobs because they shared that one word. A word like that now only counts through the word that qualifies it, so "Dialysefachkraft" still matches dialysis work and "Fachkraft Lagerlogistik" no longer does. English words such as "engineer", "specialist" and "assistant" are unchanged and still match as they always did.
• Luxembourg is searched in French and German as well as English. A search for a registered nurse there was returning lawyers, fund officers and accountants. It now finds the infirmier and Krankenpfleger postings instead.
• Jobs listed by region are no longer dropped. Poland, Czechia and several other countries label a job with its region rather than its town. A Kraków search discarded every job marked "Małopolskie", and a Prague search came back empty, because the region name did not match the town you searched. A job whose region contains your search location is now kept, and it shows the region name it was given rather than a town nobody promised.
• Jobs are kept when a source writes the place in its own way. France Travail writes "75 - Paris", Reed writes "North West London" or a postcode with no space, Jooble writes "Kingdom of Spain". Those jobs were being thrown out of radius searches even when they were nearby, counted as places we could not put on a map rather than as places that were too far. Each of those is now read properly, and where a source sends its own coordinates we use them.
• Jobs labelled only with a country now show their town. In Lithuania and Luxembourg, a posting given no more than "LT" or "LU" is looked up and placed at its town when the town is named. A job that later gains a town stays a single card in your feed rather than appearing twice.
• A translation that fails is tried again. If working out the local wording failed once, that job title stayed English-only in that language for good. It is now retried on a later search.

Your job feed

• A short feed now says what is keeping it short. When your feed holds fewer than 10 jobs, a note above the list explains why, and offers the one thing that would actually help. Most often the reason is the distance you chose, so the note reads "4 jobs within 10 miles of Leeds" and a button offers to search within 25 miles instead. Nothing changes until you press it, and the line under the button tells you it changes your saved search. When your own filters are what cut the list, the note says so and offers to clear them rather than blaming your distance. When enough of what we found is sitting in your archive, it offers to show you the archive. When your saved search leaves remote jobs out, it names that setting. And if you have not set up a search yet, it links you to that instead of offering to widen a distance that is not the reason. The note is not on the iPhone and iPad app yet.
• A job with nothing to match says so, in minutes. Some postings are too thin for us to read any skills from, or name only skills we do not track. Those cards sat on "Matching..." for about two hours before giving up. They now read "Not scored" after the first attempt, so you can tell at a glance which jobs have a score coming and which never will. A job we genuinely could not reach, because scoring was interrupted, still gets retried as before.
• Going back from a job keeps your place. On page 2 or beyond, opening a job and pressing Back put you at the top of the list again, which meant scrolling back down every time. You now return to the spot you left, with the job you opened where you left it. Next and Previous still start a new page at the top.
• The match score filter waits until you stop. Holding the arrow key on the minimum match score reloaded the feed on every step, so it flickered dozens of times on the way from 0 to 55. It now reloads once, when you stop. Reset Filters clears both score boxes, in the filter panel and in the "no jobs found" message, and they stay cleared.

Auto Search

• You can set your search to the town you actually live in. The location box only ever offered places named in the postal-code files, and those files do not name every town. Typing "Southampton" offered nothing, because the UK file names that postcode area after Northam. Croatia's file lists Zagreb only as its districts, so "Rijeka", "Split" and "Zagreb" were not offered either. People in those towns had to pick a nearby name they might not recognise, and the search was then anchored somewhere slightly wrong without ever saying so. Your own town is now offered as well, and choosing it anchors the search on that town. Where two towns share a name, each suggestion shows the region it is in, and where the region is the same for both, it names the nearest larger town instead, so you can tell which one is yours. Searches you have already saved are untouched. This works on the iPhone and iPad app too.

• "Include remote work" looks the way it is set. It was the only plain checkbox among switches, and in the dark theme it was drawn as a solid filled square while it was switched off, which read as on. It is now the same kind of switch as the settings beside it.

Settings, Help and sign out

• Two-factor sign-in has one name. The Security tab called the same feature "MFA" in some places and "Two-Factor Authentication" in others. It now says Two-Factor Authentication, and 2FA for short, everywhere, which is what the Help pages and the rest of the app already said.
• Long dashes are gone from the pages you read. The Help pages in all four languages, the coach guide, the billing plan descriptions, the release notes and the page and link previews all used a long dash that rendered inconsistently. They now use ordinary punctuation.
• Signing out moves you once. Signing out while a page was still loading could send you to the sign-in page twice, one jump after the other.

Applications

• Tracking the same job twice leaves one application. Tracking a job from two tabs at the same moment could create two cards for one job. Now the second one is refused the same way a repeat always was, and a job whose application you deleted can still be tracked again.