What changed in each release, briefly.
0.10.89 — 2026-09-26
- On phones, the situation bar also shows the total number of units as a filter.
- Opening an incident signs you straight into it. If the incident is already running, you are asked for the incident PIN.
- On the computer, the observer's SOS button is shown greyed out, as on phones.
- In the Windows application, the observer's “Zu mir” centers on the device location.
- On macOS, links to a brigade's join page open in the app.
- Security fixes.
0.10.88 — 2026-09-21
- Crew and vehicle keep only SOS on their report bar.
- They do not send requests and do not see assignments on that bar.
0.10.87 — 2026-09-20
- Position reports that could not be sent are kept and resent in order once the connection is back, instead of being dropped.
- Reports without a position no longer pile up in that queue, so the points that matter are the ones that go out first.
- An emergency call that did not get through is retried on its own; only one retry runs at a time.
- During an emergency call the situation view refreshes at its fastest rate for up to two hours. A call left standing for longer no longer keeps every screen at full speed.
- Joining shows a naming example for each role, instead of the same example everywhere.
- The guide lists the roles in the agreed order: EL, ELtg, Beobachter, Einsatzkraft, Fahrzeug.
- On fireappx.com, the chosen language is remembered again.
- The first situation load is smaller, so it arrives faster on a weak link.
- The observer report bar follows rights from situation.me, so it appears without changing role.
0.10.86 — 2026-09-15
- Aerial imagery (Luftbild) tiles draw fully instead of empty or beige squares.
- Zooming into a cold aerial view leaves fewer tile gaps.
- On the web, join offers all five roles (EL, ELtg, Beobachter, crew, vehicle). The Windows and macOS shells stay command-only.
- The join vehicle icon is a general vehicle outline (box and cab).
- The FireAppX mark in the site header goes to the start page.
- On the web, Beobachter can see assignments and requests (read-only).
- On the web, Beobachter “Zu mir” uses the device location, not ELtg or EL.
- Beobachter see assignment requests more clearly on the map and in the status bar. The phone unit sheet shows history.
- When your own location is missing, the situation view shows a readable notice.
- Beobachter “Zu mir” shows a wait hint while GPS arrives.
- On iPhone, Beobachter “Zu mir” requests a one-shot device location.
- Assignment requests no longer appear twice in the status bar.
- Beobachter “Zu mir” now centers on the device GPS when a fix arrives (retries while waiting).
- On macOS, EL and ELtg report from device Location Services; Beobachter “Zu mir” centers on the Mac’s GPS.
- On macOS only, a map pin overrides GPS; a second click returns to the live location.
0.10.85 — 2026-09-14
- Housekeeping on the server side. Nothing changes in the applications.
0.10.84 — 2026-09-14
- The Windows application is released the same way on both paths from now on: the download page and the Microsoft Store carry the same version. The Store copy cannot update itself — it is the Store that brings it — so every release is submitted there as well.
0.10.83 — 2026-09-14
- The Android app is available on Google Play.
- Brigade administration in the Windows application handles one task after another in a single visit: release a unit, save the command PIN, save the gateway, remove a device. The notice above the lists says what is happening and clears itself when it is done.
- A button that is switched off now looks switched off, so it is clear at a glance which actions are available.
- The update button is called "Updates prüfen" (check for updates). In the Microsoft Store version it stays pale: updates arrive through the Store there.
- On Android, the menu now changes the kind and the command PIN during a running incident. Leaving EL works the same way as on iPhone.
- The Android app speaks German and English in the native shell.
0.10.82 — 2026-09-11
- The QR button in the situation bar opens the "Let others join" sheet again during an incident (code, address, share). Outside an incident it still opens the camera in the app.
- iPhone app: a wrong incident PIN entered in the main menu can now be corrected; the field comes back.
- iPhone app: opening a brigade link while signed in no longer switches the brigade under a running incident.
- iPhone app: the keyboard closes when the sign-in form opens.
- iPhone app: the permissions text now says that reporting waits without Precise Location.
- Bug fixes.
0.10.81 — 2026-09-08
- If the incident PIN is already known (start page / QR / URL), command roles only enter the command PIN; the incident PIN is carried as join_code and not asked again.
- If no incident PIN yet: EL, ELtg and Beobachter enter both; crew and vehicles keep the incident PIN only.
0.10.80 — 2026-09-08
- Vehicle type renamed to Water-carrying (DE Wasserführend); TLF/RLF codes unchanged.
- You can join a running incident with only the incident PIN, even when no brigade is selected.
- Taking over as EL or ELtg keeps the previous unit, renamed; Beobachter cannot take over.
- On the web situation bar, QR is unavailable during an incident and works again after sign-out.
- iPhone app: position reporting starts as soon as location access is granted. Notifications stay optional.
- iPhone app: sends less on a poor connection — a growing pause while offline, immediate delivery once the network is back, and the map reloads by itself when the connection returns.
- iPhone app: lower battery use — the compass pauses while the app is in the background.
- iPhone app: on iPad the menus and the sign-in form are a readable column instead of the full width.
- iPhone app: one button above the keyboard instead of three, and the bottom bar no longer floats above the keyboard.
- iPhone app: the SOS confirmation closes when the app goes to the background.
- Bug fixes.
0.10.79 — 2026-09-04
- Android app: a unit that stands still keeps its position on the map.
0.10.78 — 2026-09-04
- Android: the unit list ends at the bottom bar whatever the font size, and on tablets and in landscape it stands beside the map below the header, with the map tools next to it.
0.10.77 — 2026-09-04
- Android app: once location access is granted, the map opens; the advice about battery and notification settings is shown once per sign-in and stays available in the menu.
0.10.76 — 2026-09-04
- Android app: position reporting starts as soon as location access is granted. Battery and notification settings are shown as advice.
- Android app: sends less on a poor connection — one delivery at a time, a growing pause while offline, immediate delivery once the network is back, and a bounded queue that keeps the newest positions.
- Android app: lower battery use. GPS is read every four seconds and from five metres of movement, and the page pauses while the app is in the background.
- Android app: the sign-in screen scrolls in landscape, the bottom bar fits large system fonts, SOS in the bar is red while signed in, and the PIN field stays visible after a wrong PIN.
- Android app: on tablets and in landscape the unit list is a column beside the map.
- Android app: a privacy link in the menu, the camera is optional (the brigade list and the four-digit code work without it), and the update confirmation arrives as a notification when the app is in the background.
- Bug fixes.
0.10.75 — 2026-09-04
- Windows application: a message that could not be sent while offline is delivered as soon as the connection is back — an SOS first.
- Windows application: the sign-in screen has a full-size button to join another incident by its incident PIN, keyboard access to every control, a scrolling PIN column on small screens and a "Checking…" state while it works.
- Windows application: when the sign-in expires or the incident ends, the app returns to the sign-in screen and says why. The SOS marker always lies on top of its neighbours, Escape closes confirmation sheets, an armed "set assignment" button is highlighted, the lists keep their scroll position, and units without GPS or with a low battery have their own colours.
- Windows application: in full screen the top edge of the map responds to clicks. Restarting after an update no longer starts with a waiting screen.
- Windows application: the administration shows the action on the device button, the server's own error messages, and a locked confirmation before deleting.
- Windows application: map tiles are kept on disk (up to 400 MB), so a known area draws without a connection.
- The history no longer lists "reporting without a GPS fix". The unit itself shows that state for as long as it lasts.
- Bug fixes.
0.10.74 — 2026-09-04
- Windows application: once a brigade is chosen, the command PIN is all it takes — the incident PIN field steps aside. If no incident is running there, the same button opens one. A link below switches back to joining another brigade's incident by its incident PIN.
- Windows application: the map now zooms in a smooth motion around the pointer, with the next level's tiles fetched while it moves, and zooming out keeps the map filled.
- Windows application: the zoom setting in the menu now scales the whole situation picture, the lists and the sign-in screen.
- Windows application: the side column and the list rows are a little more compact, so a Full HD laptop shows the units without scrolling.
0.10.73 — 2026-09-04
- In the browser, the situation picture keeps the screen awake while a unit is signed in, and it catches up the moment the tab or the phone comes back to the foreground: situation, own position, heartbeat.
- A location fix that is too imprecise to be useful is held back. The unit stays in contact and keeps its last good position instead of jumping to an estimate.
- The first situation picture shows all units on the map, wherever the brigade is.
- On narrower screens the toolbar above the map fits on one line: the four view buttons show their symbol only, with the label as a tooltip.
- The chosen day or night scheme applies before the page is drawn.
- Signing in from the browser: the button stays locked while the sign-in runs, and a network problem is shown right in the form.
- Bug fixes.
0.10.72 — 2026-09-04
- A tracker running on battery is no longer shown as mains-powered. The charging state now travels as an unambiguous value instead of a text label, and both spellings of the label are understood, so the state cannot get stuck on its last known value.
0.10.71 — 2026-09-04
- With two gateways at one incident, a tracker heard by both now shows up in both incident pictures. Until now the first packet to arrive won and the second was discarded as a duplicate, so the tracker appeared in one picture and not the other.
0.10.70 — 2026-09-04
- The Windows application's sign-in screen now lists every brigade on the right, with running incidents at the top. One click takes you there. The list keeps itself up to date while it is on screen.
- The situation picture makes more room for units: the four counters at the top left are flatter, and "End incident" has moved up beside the heading.
- Map symbols now have a proper outline — dark by day, light at night — so they stand out from the map in both schemes.
- The buttons above the map have swapped sides: assignment, request and "set location" are now on the left, the view controls on the right. The QR code button has gone from the map; it is still in the window bar at the top.
- Settings now has four tabs: Updates, Everyday, Device and Info. Website, contact, donations, the version and the log folder have their own tab again instead of hanging below the update options.
- The window bar separates its groups with thin dividers, so leaving an incident is no longer right next to closing the window.
0.10.69 — 2026-09-04
- A tracker reporting through a neighbouring brigade's gateway no longer shows up there a second time under a made-up name. It keeps the name given by the brigade it belongs to.
0.10.67 — 2026-09-04
- A tracker now exists once across the whole system. When a device reported through a neighbouring brigade's gateway, it could be taken on there a second time under a made-up name; it now keeps the name of the brigade it belongs to. Taking on a device that belongs elsewhere is refused, and the message says where to look.
0.10.65 — 2026-09-03
- When a neighbouring brigade joins an incident, its LoRa trackers now appear on the map as well — over whichever gateway happens to hear them. Until now a gateway only carried the trackers of its own brigade, so a tracker could be transmitting perfectly and still be invisible. Each brigade keeps managing its own devices.
0.10.64 — 2026-09-03
- The English handbook now shows English screenshots. Until now the text was English while every picture showed the German interface.
0.10.63 — 2026-09-03
- The guide now describes the Windows application as it is: it draws the map, the unit list, the history, brigade administration, statistics and the QR code itself. Three screenshots show the situation picture, a selected unit with its details, and night mode.
0.10.62 — 2026-09-03
- The DE|EN switch is now on the administration and statistics pages as well, next to "Back to the situation". Until now the language could only be changed on the public pages, which made the new English version of those two pages hard to reach.
0.10.61 — 2026-09-03
- Signing back into a running incident from the same device now returns the unit you already had — in the browser and in the Android app as well, not just on Windows. On a phone this is the everyday case: the screen goes off, the page is unloaded, and you sign in again.
- Administration and statistics are now available in English as well. Labels, table headings, messages and the explanatory notes all follow the language switch.
- Numbers now follow the language too: 1,234.5 in English, 1.234,5 in German. Distances on the statistics page had been shown in German notation regardless of the setting.
0.10.60 — 2026-09-03
- On the computer, the day/night button now has its own icon instead of sharing the map button's. The phone and tablet versions already showed it that way — and the Windows desktop app follows.
- Brigade administration in the Windows desktop app now has the archive: ended incidents with their period, units, positions, kilometres and the number of distress calls. Each one opens its history, and from there the Excel workbook.
- When a unit calls in, incident command sees and hears it again in the Windows desktop app — until now that only showed in the window bar.
0.10.59 — 2026-09-03
- The Windows desktop app now plays a sound for an assignment and for a request, the same way the browser does — the assignment keeps sounding until it is answered, the request sounds once.
- The situation now shows who you are signed in as, under the brigade name.
- Incident command is the first role on the Windows sign-in screen, and the role colours are right: incident command red, incident commander yellow.
- Signing in when the role is taken: "Join" and "Take over" are clearly separated now, and both can be reached with the keyboard.
- Printing the QR sheet really opens the QR sheet again, not the start page.
- Units on the map can be clicked. This was in 0.10.57 but never worked: the check ran against "the mouse button is down" instead of "the map was dragged", and that is always true when you let go.
- A LoRa tracker that keeps transmitting now comes back into the situation on its own. Until now, once it had been removed from a running incident, its reports kept arriving but it stayed invisible for the rest of that incident. The history records the return, so nobody wonders why a removed unit is back. To keep a tracker out for good, switch the device off in the admin area — that still holds.
0.10.58 — 2026-09-03
- The command PIN box is no longer filled in for you. Some browsers had been restoring it when you went back or reloaded the page. The incident PIN is still kept on purpose — if you drop out mid-incident, you get back in with one press.
0.10.57 — 2026-09-03
- Signing back into the same incident from the same device now returns the unit you already had, instead of creating a new one and renaming the old one. Taking over incident command from a different device works exactly as before.
- The history is now shown in the language of the app — in the browser, on the phone and on the desktop.
- The incident and command PIN fields are no longer treated as password boxes. Password managers stopped offering to save them and no longer cover the field with a suggestion; the digits stay hidden as before.
- The map in the Windows desktop app really turns dark at night now, the same way as in the browser. The aerial view stays untouched.
- Units on the map can be clicked, the unit list is sorted by distance with the command roles on top, and picking a unit shows its details: kind, status, last contact, last position, distance, battery, accuracy.
- The history scrolls, and it now holds enough lines to be worth scrolling.
- Every button above the map stays reachable on a narrow window — the toolbar wraps instead of cutting the last group off.
- The assignment pin looks like the web version and turns green, together with its line, as soon as a unit accepts.
- The emergency call asks before it is sent and before it is taken back, in the app's own style instead of a Windows message box.
- Printing the entry sheet no longer takes you out of the incident.
- Brigade administration and statistics are centred instead of squeezed against the left edge.
0.10.56 — 2026-09-02
- The Windows desktop app can now end an incident and set its keyword — for Einsatzleitung and Einsatzleiter, as everywhere else.
- Track lines are back, and there is a button to switch them on and off.
- Messages that cannot be sent now wait in a queue and go out when the line is back. An emergency call goes first and never expires.
- Assignments and requests can be accepted, declined and marked done from the desktop app.
- Joining with an incident PIN works even when a different brigade is saved on the computer.
- The situation opens right after start instead of waiting for the web page to finish loading.
- The history now says when a unit was removed by someone else instead of leaving on its own.
- Map markers now look exactly like the web version: rounded squares with the dark edge, the status dot and the assignment ring.
- Every button above the map carries its icon; assignment, request and QR are round icon buttons, and the emergency call sits in the middle.
- The history scrolls, and the status stripe next to each unit is clearly visible again.
- The QR sheet can be printed, its link copied and shared.
- Switching to English now really switches everything, including the labels that come with the data.
0.10.55 — 2026-09-02
- The map in the Windows desktop app is dramatically faster to load, pan and zoom. Dragging now moves the finished image instead of redrawing it, missing tiles are filled from the next coarser zoom level, and there is no grey flash any more.
- Unit labels no longer overlap: badges and labels fan out around a crowded spot, with a thin leader line back to the real position.
- Boats, drones and water tenders carry their own icons, and vehicles have a wider badge than people — the same as in the browser and the mobile apps.
- Pressing F1 and closing it again no longer covers the situation.
- The toolbar above the map wraps instead of running off a narrow window.
0.10.54 — 2026-09-02
- Everything from 0.10.53 now actually reaches the Windows desktop app. Devices already running the previous build did not see it offered, because the update check compares build numbers and that number had not moved.
- Included with it: the top-bar buttons respond to a click, signing out closes the situation, assignments and requests can be taken back, and night mode covers the whole app.
0.10.53 — 2026-09-02
- The Windows desktop app now carries the full toolbar above the map: show all, aerial view, day/night, go to me, emergency call, set assignment, request, and set location.
- Every unit shows the icon of its kind — in the list and on the map, the same drawings as in the browser.
- The four counters are the filter: units, active, SOS, no contact. Press one to filter, press it again to clear.
- The history is colour-coded by level, so the one line that matters stands out.
- Day and night switch the whole app, and the setting stays.
- Map tiles load noticeably faster.
- The top bar has proper buttons instead of plain text, and they now respond to a click — management, statistics, QR and sign-out.
- Signing out really signs out: the situation closes and the sign-in screen comes back.
- Assignments and requests can be taken back with the same button that set them.
0.10.52 — 2026-09-02
- The Windows desktop app shows the situation reliably after any sign-in, including after leaving and joining again in a different role.
- The version now stands in the situation itself, bottom left, in the form used everywhere: "Server 0.10.52 - Build 1052".
- English switches everywhere at once — the labels of the app and the ones that come with the data.
- The map starts over land, not over the pole, when no unit has a position yet.
0.10.51 — 2026-09-02
- The Windows desktop app is now native throughout: the situation picture with its map, the unit list, administration, statistics, the QR code and leaving an incident are all drawn by the app itself. The server is the data source.
- The map draws its own tiles and keeps them for the next start. Units show in the colour of their kind, with their trails and their labels. Drag to pan, scroll to zoom, "Alle zeigen" fits everyone on screen.
- Administration, statistics, QR code and leaving are reachable from the window bar while an incident is joined.
- The API is now ordered by platform: shared endpoints stay at /api/v1/..., what a native app needs for its own screens lives at /api/windows/v1/... so the other platforms can follow.
0.10.49 — 2026-09-02
- Joining a running incident from the Windows desktop app takes only the two PINs — the incident PIN and the command PIN. No brigade to pick first, whichever brigade you belong to, or none at all.
- After joining, the app opens the situation picture of the incident the PINs belong to.
- If the PINs match no running incident, the app opens the brigade list so leadership can start one there.
- "Andere Feuerwehr" is always available on the sign-in screen.
- The sign-in screen no longer stretches the role rows across the whole window in full screen.
0.10.47 — 2026-09-02
- Joining an incident from the Windows desktop app: pick the brigade and the role, enter both PINs, and the app takes you into the situation picture.
- Starting the desktop app without a brigade opens the brigade list instead of a sign-in that cannot complete.
- The desktop app remembers the brigade you last joined with, so the next start goes straight to the PINs.
- Picking Beobachter asks for a designation, the way the other roles do.
0.10.46 — 2026-09-02
- The desktop app for Windows signs in on its own screen: pick Einsatzleiter, Einsatzleitung or Beobachter, enter the incident PIN and the command PIN, and join. No web page in between.
- Signing out in the desktop app returns to that screen, ready for the next incident.
- Beobachter can be many at once and see the situation picture like the incident commander does.
- In English, the desktop app now says "Observer" throughout.
- The desktop app shows its version the same way everywhere: "Server 0.10.46 - Build 1046".
- Installations of the desktop app on 0.10.39 and older are offered 0.10.46 the next time they check for updates.
0.10.45 — 2026-08-30
- On the web join sheet, EL, ELtg and Beobachter now enter both the command PIN and the incident PIN.
- Join says "Einsteigen" (English: "Join"). Ending SOS says "SOS beenden" (English: "End SOS").
- Creating a brigade sends a confirmation mail in HTML, with a matching plain-text copy.
- An accepted assignment now shows green everywhere: the pin on the map, the dashed line to it, and the bar on the receiving device. Blue still means "sent, no answer yet". The bar stays blue while a callback request is still open.
/appsends the device to the matching store (App Store, Play, Microsoft Store). Listings may 404.- The public guide is German and English.
/guide?lang=enis English;/guide?lang=deis German. The name FireAppX Tracking stays. - The guide lists five unit kinds, including Beobachter.
0.10.44 — 2026-08-30
- On iPhone, leaving a leadership role through the menu works: an incident commander can switch back to "Einsatzkraft" or any other kind and gets a free name again. While the role is held, its radio designation stays fixed.
0.10.43 — 2026-08-30
- On iPhone, picking "Einsatzleiter", "Einsatzleitung" or "Beobachter" in the menu offers the command PIN field.
0.10.42 — 2026-08-30
- On iPhone the menu now changes the kind and the vehicle type on the running incident as well, not just the name. Switching from "Einsatzkraft" to "Fahrzeug" and picking "Tanklöschfahrzeug" is carried through to the map for everyone. Leadership roles still require signing on with the command PIN.
- On iPhone, changing only the kind, leaving the name as it was, now takes effect — a save with an unchanged name is carried through like any other.
- On iPhone, "Beobachter" is now offered in the menu's list of kinds.
- On iPhone, switching to a leadership role from the menu asks for the command PIN. The field appears only when such a role is selected, and the PIN is kept on the device.
0.10.41 — 2026-08-30
- On the situation screen, the red emergency bar and the blue "Meldet sich" line now show a unit's current name. A unit that renames itself during an incident is named the same way everywhere on screen.
- Renaming yourself on iPhone updates your own name badge at once. The map, the trails and any open assignment stay where they are.
0.10.40 — 2026-08-30
- On iPhone the emergency-call vibration ends with the alarm.
- On iPhone the menu carries the vehicle type as soon as "Fahrzeug" is chosen. The list comes from the brigade.
- On iPhone the button at the bottom of the menu reads "Hauptmenü" when the device is not signed on, and "Zurück zur Lage" when it is.
- On iPhone the main menu stays open after an incident has ended: "Testeinsatz ansehen", "QR-Code scannen" and the brigade list.
- On iPhone the name can be changed during a running incident. The track and any open assignment are kept.
- On iPhone, if the list of kinds is not available at sign-on, the app says so and offers "Noch einmal versuchen".
0.10.39 — 2026-08-26
- The iPhone app icon is the same artwork as the Android one.
0.10.38 — 2026-08-26
- Bug fixes.
0.10.37 — 2026-08-26
- On iPhone an SOS also sounds while the phone is locked. The alert carries the alarm sound and repeats it while the SOS lasts.
0.10.36 — 2026-08-26
- On iPhone an SOS and an assignment reach the phone while it is locked.
- The iPhone app can show a notice on the lock screen. It asks for that the first time a device signs on to an incident. Declining it still leaves the alarm sound.
- On iPhone the menu button closes the menu.
- The QR button is in the bottom bar on iPhone.
0.10.35 — 2026-08-26
- On iPhone the situation page shows the settings button in the bottom bar and uses the app for locating and sound.
- On iPhone the QR button sits in the bottom bar, with SOS in the middle.
- On iPhone a short message does not block taps underneath.
- On iPhone every input field accepts a tap across its whole height, the number keypad can be closed, and the fields stop at the same lengths as on Android.
- On iPhone the page does not pinch-zoom, so the bottom bar stays in view.
- On iPhone the compass has its own line in the permissions screen. A disabled SOS button is grey, not red.
- The server, the Android app and the iPhone app carry the same version number.
0.10.34 — 2026-08-26
- On an iPhone a printed QR code now opens the app instead of Safari. The same already worked on Android; in Safari the tracking only runs while the screen is on.
0.10.33 — 2026-08-26
- There is now an iPhone app. It does the same as the Android one: it keeps reporting the position while the phone is locked in a pocket, it is loud when somebody else raises an alarm, and it brings its own screens for the entry code, the brigade list, signing on, the permissions and the menu.
- On the iPhone the situation page asks before signing off.
- On the iPhone the map button and the day/night button have their own symbols.
0.10.32 — 2026-08-26
- On a computer the toolbar above the map is now grouped: map tools on the left, the emergency call on its own, the command buttons next to it, and entry code, admin, statistics and sign out on the right.
0.10.31 — 2026-08-26
- The Android download on the website matches what testers get from Google Play.
- The Windows application is available as version 0.10.2.
0.10.30 — 2026-08-25
- Maintenance only. Nothing changes in the application.
0.10.29 — 2026-08-25
- The Android app is now available to testers on Google Play.
0.10.28 — 2026-08-25
- The two PDF handouts are current again: the crew sheet now fits on a single page and covers vehicles and crew, and the large handout has the logo on its front page, a list of links at the back, and no more screenshots sitting on top of the text.
0.10.27 — 2026-08-25
- Wording only. Nothing changes in the application.
0.10.26 — 2026-08-25
- Wording only: the handbook, the website and the screens all say "Computer". Nothing else changes.
0.10.25 — 2026-08-25
- In the browser, the phone view is now the same on Android and iPhone: units, entry code, emergency call, sign out — in that order.
- On a computer, the emergency call sits in the middle of the toolbar, and the admin and statistics links moved up beside it.
0.10.24 — 2026-08-25
- Documentation only. Nothing changes in the application.
0.10.23 — 2026-08-25
- On a computer, the button that shows the entry code sits next to the emergency call — the same place the phone app has it.
0.10.22 — 2026-08-25
- After signing in, the units appear straight away.
0.10.21 — 2026-08-25
- Security fixes.
- Bug fixes.
- The compass works in the browser and in the Windows app, not only in the phone apps.
0.10.20 — 2026-08-24
- The two PDF handouts are current again. Every screenshot was taken fresh, and the text now matches what the apps actually do — including the parts that changed since August 20th.
0.10.19 — 2026-08-24
- Security fixes.
- The two download buttons now say which app they fetch — one names Android, the other Windows. A screen reader announces them apart.
0.10.18 — 2026-08-24
- The FireAppX site now says in search results what it is for, in German and in English: the title names the question an incident commander actually has, and the summary fits in the space search engines show.
- The site states its own facts for AI assistants — how to reach us, where the server stands, and that a device is located only while it is signed on to an incident.
0.10.17 — 2026-08-24
- The FireAppX site icon now fills its tile: the mark went from 64 % to 82 % of the width, so it stays legible where search engines and browsers show it small.
0.10.16 — 2026-08-23
- The FireAppX site: the donate link and the footer links follow the page colour in light mode.
- The site loads noticeably less: the two logos are served as vector graphics instead of large bitmaps, and images and stylesheets may now stay in the browser cache for a week.
0.10.15 — 2026-08-23
- The FireAppX site now answers under a single address. The alternative spelling redirects to it permanently, so search engines see one page instead of two.
0.10.14 — 2026-08-23
- Documentation only. Nothing changes in the application.
0.10.13 — 2026-08-23
- Documentation only. Nothing changes in the application.
0.10.12 — 2026-08-23
- Documentation only. Nothing changes in the application.
0.10.11 — 2026-08-23
- Android: "Nach Updates suchen" answers while you are signed in to an incident.
- Android: when an update cannot be installed, the app says why.
- Android: free space is checked before the download starts.
- Android: "Later" means one day.
0.10.10 — 2026-08-23
- The access sheet a brigade receives when it is created now names the observer among the roles that need the command PIN.
- A password containing punctuation is printed in the larger type on that sheet, like every other credential on it.
0.10.9 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.10.8 — 2026-08-23
- The guide now explains assignments and requests — the blue bar, the assignment marker and what the question mark does in each role.
- The guide explains where the command PIN is set, and that it is shown once and never again.
- New sections: the observer, the Windows application, signing off from an incident, and the Excel workbook for an archived incident.
- The guide names the QR button, which every signed-in unit has.
0.10.7 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.10.6 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.10.5 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.10.4 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.10.3 — 2026-08-23
- The guide explains the three states of the SOS button and what happens on a weak connection.
0.10.2 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.10.1 — 2026-08-23
- Android: the app now says so when it is older than the server expects. It keeps working.
- The FireAppX site has an English version, and a clearer title in search results.
0.9.99 — 2026-08-23
- Distress call: on a weak connection the app keeps trying, and the button shows whether the server has confirmed.
0.9.98 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.9.97 — 2026-08-23
- The situation map now sends noticeably less data to each device. On a weak mobile connection that means less waiting and less data used.
- Faster connections between device and server.
0.9.96 — 2026-08-23
- Windows app: checking for a new version now answers in one line — either there is a new version, or there isn't.
- Windows app: when there is one, a button offers to install it right away.
- Windows app: the server address is not a setting in the dialog.
0.9.95 — 2026-08-23
- Housekeeping on the server side. Nothing changes in the application.
0.9.94 — 2026-08-23
- Documentation only. Nothing changes in the application.
0.9.93 — 2026-08-23
- Setup and handover notes brought up to date.
0.9.92 — 2026-08-23
- Security fixes.
- Exporting a very large incident is faster and needs far less memory.
0.9.91 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.9.90 — 2026-08-23
- Wording throughout this file.
0.9.89 — 2026-08-23
- Security fixes.
0.9.88 — 2026-08-23
- Windows app: Settings has a "check for a new version" button with its own answer box.
- Windows app: the log writes versions the same way as the rest of the system.
0.9.87 — 2026-08-23
- Notices above the map can be dismissed with a tap.
- When the incident command clears a unit's raised hand, that unit sees "Meldung gelesen" and can tap it away.
- The admin area has a server dashboard: load, CPU, free memory, disk space, running incidents, reporting devices, database size and versions.
0.9.86 — 2026-08-23
- Devices can be edited: name, make and model, kind, vehicle type and note.
- Each device has a "make and model" field, shown as its own column in the list. It is typed in rather than detected — LoRaWAN devices do not reliably identify their maker.
0.9.85 — 2026-08-23
- The archive export puts date and time in one cell as a real date value, so Excel sorts and filters it correctly. Times include seconds, and the columns are wide enough to show them.
- Observers: "centre on me" centres on the incident command, or on the incident commander if there is no command post. An observer reports no position of their own.
0.9.84 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.9.83 — 2026-08-23
- Internal maintenance. No change to how the application behaves.
0.9.82 — 2026-08-23
- Start page: the download section is headed "Client download". The Windows tile is called "Windows-App", matching the Android one.
- Start page: the incident PIN field is framed in red so it is found at a glance.
- Start page: the guide sits at the end, before the donation note.
- A brigade with a running incident shows the incident keyword in grey in its row.
- Shorter wording in several places.
0.9.81 — 2026-08-23
- Android: "Nach Updates suchen" answers. The button says "Wird gefragt …" while it works, and the result is a dialog — either "Kein neuerer Stand" with the version you have, or "Nicht erreichbar".
- Archived incidents are clickable. Each one opens its history, the units that took part, and the figures.
- From there, an incident downloads as an Excel workbook: date, time, unit, event and the position measured at that moment — plus how old and how accurate that position was.
- A second sheet lists every recorded position, and a third lists the units. If a track is too large to fit, the file says so.
- The same incident always produces a byte-identical file, so two copies can be compared.
0.9.80 — 2026-08-23
- The management page shows local time. Every time there leads with how long ago it was, with the exact local time below it.
- The command PIN is shown once, right after you set it, so you can check it arrived as intended. It cannot be shown again later.
- The command PIN section says "gesetzt" or "nicht gesetzt" at a glance.
0.9.79 — 2026-08-23
- Requests work both ways. The incident command can ask a selected unit to call in, and a crew or vehicle can raise its hand and ask the command to call them.
- The command sees "Meldet sich: …" in the blue bar, hears one short tone when a hand goes up, and clears it by selecting the unit and pressing the question mark.
- Both can be open at the same time on the same unit, and neither clears the other.
- The history tells apart a unit withdrawing its own message from the command acknowledging it.
- Observers see the raised hands but do not raise one.
- LoRa trackers are allowed four minutes without contact instead of three, because their radio duty cycle can stretch the interval. Phones keep the three-minute limit.
0.9.78 — 2026-08-23
- Android: signing in to an incident now takes you straight to a populated map.
- Observers see everything the incident command sees — assignments, requests, declines and track lines — while sending nothing: no position, no alerts, and they cannot be given assignments.
- Observers now sign in with the command PIN, because they see the full command view.
- A declined assignment is orange in the history instead of blue.
- Android menu: shorter. The server address and two explanatory blocks are gone, the version and the update button sit together, and the permission screen leads with its four buttons.
- Version numbers are written the same way everywhere now.
0.9.77 — 2026-08-22
- Android: signing in to an incident is a native screen. The title fits, every field is reachable, and a lost network connection says so.
- The list of unit kinds still comes from the server, so a kind added by your brigade appears without a new app version. Its icon follows with the next app release; until then it shows a plain mark in its own colour.
- The web sign-in form is unchanged and still serves the desktop, iPhone and Windows app, and any Android version older than this one.
0.9.76 — 2026-08-22
- Windows app: the title bar resets when you open the role guide.
- Windows app: with "keep window on top" enabled, the website, contact and donate buttons bring the other program to the front.
- The guide now lists the observer role and explains which PIN is asked for, including the case where scanning the QR code already covered it.
- The management sign-in page offers a way straight to the situation view.
0.9.75 — 2026-08-22
- Every page that is not the situation view now has a "back to the situation" link at the top: the guide, privacy, changelog, and the management and statistics pages.
- The Windows app: the role guide knows which brigade you came from and leads back to its situation view.
- You can now see your own role. The header of every situation view shows your unit name and what you are signed in as (crew, vehicle, incident commander), and the Windows title bar shows it too. It matters because your role can change without you doing anything, when somebody else takes over command.
- Android sign-in screen: the title fits on one line, the buttons sit side by side, and every field stays clear of them — the vehicle type is now selectable. When the entry PIN has already been given by scanning the QR code, the screen says so.
0.9.74 — 2026-08-22
- Android: with the sign-out confirmation open, the back button means "stay signed in" and closes the question, the same as the Bleiben button.
0.9.73 — 2026-08-22
- Android: back on the sign-in screen sends the app to the background; back over the map closes an open dialog and stays in the app.
0.9.72 — 2026-08-22
- Android: the back button follows what the page is showing.
0.9.71 — 2026-08-22
- Android: the back button on the sign-in screen works in every case.
0.9.70 — 2026-08-22
- Android: on the sign-in screen the back button sends the app to the background, as it should — there is nothing to close there. Closing an open dialog over the map keeps working.
0.9.69 — 2026-08-22
- Android: pressing back — by button or by edge-swipe — closes an open dialog and keeps the app while you are signed in.
0.9.68 — 2026-08-22
- The server is built to carry several hundred units at once.
- Android: the device back button now closes an open menu or dialog instead of leaving the app. Only when nothing is open, and the map is showing, does it zoom to your own position.
- Windows: the QR entry sheet now prints from within the app instead of opening a browser.
- The management page can now switch a LoRaWAN tracker off and on again without deleting it. A switched-off tracker stops reporting until it is switched back on.
- Windows: the "Einsätze" link is gone from the app, where it had no use.
0.9.67 — 2026-08-22
- Security fixes.
- The welcome mail subject names the brigade.
0.9.66 — 2026-08-22
- Security fixes.
- The situation map stays responsive with many units signed in.
- Ending an incident finishes at once; the archive move follows afterwards.
- Incident archives stay until the brigade decides otherwise.
0.9.65 — 2026-08-22
- The operator view lists recorded faults: a summary by type and the latest entries in full.
- The nightly cleanup run compares today against yesterday and warns about anything that stands out.
0.9.64 — 2026-08-22
- Hovering over a unit — on the map or in the list — now shows everything the detail panel shows: role, state, last contact, battery and charging, accuracy, and the assignment if you are allowed to see it.
- The Windows settings window gained four buttons: the role guide, the website, a contact mail with the version already in the subject, and a donation link. The last three open outside the application; nothing foreign runs inside it.
0.9.63 — 2026-08-22
- When someone takes over the incident command, the computer that was replaced now says so: a dialog names the new role, lists the buttons that are gone, and stays until it is acknowledged. The buttons follow immediately — before the dialog appears, not when it is closed.
0.9.62 — 2026-08-22
- The Android app can now be updated by hand while an incident is running. The dialog says plainly what that costs: the app restarts, and the unit shows no contact for about half a minute. The automatic check still stays quiet for the whole incident — only the button in the settings goes through.
- The German interface now uses one single word for a release, on every screen, in every dialog and throughout the handbook.
0.9.61 — 2026-08-22
- A second command-post computer can now join an incident as an observer: it sees the whole picture including assignments and hears the emergency call, but sends nothing. There can be any number of them, so nobody has to take the incident command away from a colleague to look on.
0.9.60 — 2026-08-22
- A unit that is running on mains power now says so next to the battery reading, so a steady 100 % is not mistaken for a full battery.
- The position accuracy reported by LoRaWAN trackers now reaches the unit sheet.
0.9.59 — 2026-08-22
- The Windows application is now packaged for the Microsoft Store. In that form it does not update itself — the Store does — and the option to start with Windows is set in the Windows settings instead. Both are shown greyed out with the reason.
- Nothing changes for the version downloaded from the website.
0.9.58 — 2026-08-22
- The position accuracy reported by LoRaWAN trackers reaches the map.
0.9.57 — 2026-08-22
- Housekeeping only. Nothing changes on screen.
0.9.56 — 2026-08-22
- Android: while a native screen such as the menu is open and you are signed in, the bar buttons for units, emergency call and sign-out now take you back to the map, where those controls live. They stay greyed before sign-in, as before.
0.9.55 — 2026-08-22
- The settings button in the bottom bar now carries a proper cog, so it reads as settings at a glance.
- LoRaWAN trackers that report it now record how accurate their position is, in metres. A point on the map can say how much to trust it.
0.9.54 — 2026-08-22
- App, Windows application and server carry the same version number.
- The version in the corner of the map says which number is which: "Server ... · App-Stand ...".
0.9.53 — 2026-08-22
- Internal maintenance. Nothing changes on screen.
0.9.52 — 2026-08-22
- The assignment badge in the unit list uses the normal text colour; the tint still carries the colour and the word still says which state it is.
0.9.51 — 2026-08-22
- The incident command can see whether a unit has accepted its assignment. A ring around the unit on the map, a word on the pin and a badge in the unit list: blue for sent, green for accepted.
0.9.50 — 2026-08-22
- Housekeeping only. Nothing changes on screen.
0.9.49 — 2026-08-22
- LoRaWAN trackers that ask to join show up in the brigade's administration, so a new device can be adopted without knowing its identifier in advance.
0.9.48 — 2026-08-22
- Housekeeping only. Nothing changes on screen.
0.9.47 — 2026-08-22
- Windows: the brigade is now picked from a list instead of typed in by hand. Typing still works, so nothing is lost when the list cannot be fetched.
- Windows: a new check in the settings tells you whether this computer's position comes from GPS or only from its network address — it names the accuracy in metres either way.
0.9.46 — 2026-08-22
- Housekeeping only. Nothing changes on screen.
0.9.45 — 2026-08-21
- Housekeeping only. Server load was still being recorded into an old table that nothing reads any more; it now goes where the reports look. Nothing changes on screen.
0.9.44 — 2026-08-21
- Windows: the application does not replace itself while an incident is running or an emergency call is open.
0.9.43 — 2026-08-21
- Boats and drones now carry their own sign on the map. They differ in outline, not in an inner detail, so they stay apart at map size.
0.9.42 — 2026-08-21
- If a unit is taken over on a new device under the same name, an open question moves across with it, as an open assignment already does.
- On phones and tablets the map buttons stay clear of the bottom bar when the incident command has all of them.
0.9.41 — 2026-08-21
- The incident command sends the question mark to a chosen unit, and that unit answers.
- A unit that receives an assignment sees who sent it, and can decline it as well as accept it.
- Assignments and questions are blue in the log.
- Both fit into much less room on phones and tablets.
- If someone signs in as incident command while another device already holds that role, the first one stays in the incident and is renamed with an "ex_" prefix.
- Android: the app can offer its own updates. It never does so during an incident, and never without being asked.
0.9.40 — 2026-08-21
- The incident command can send a unit to a point on the map. Only that unit, the incident commander and the command post see it. The unit hears a tone until it accepts, taps the point for bearing and distance, and marks it done on arrival.
- A unit can raise a question mark to get the command's attention — for a radio call, for instance. The command acknowledges it and it is gone.
- In the Windows application, "zur Startseite" now leads to its own entry screen instead of the website.
0.9.39 — 2026-08-21
- Groundwork only. Nothing changes on screen yet.
0.9.38 — 2026-08-21
- An emergency call now always reaches the incident commander, whatever the distance.
0.9.37 — 2026-08-20
- The Windows application starts on its own entry screen: pick your brigade, then open an incident or join the running one with the command code. No download section and no donation notice there.
- Security fixes.
0.9.36 — 2026-08-20
- The two e-mail buttons are gone from the website. The address is still in the contact section and in the footer.
0.9.35 — 2026-08-20
- Secondary links on the website carry no box and no underline until you point at them.
0.9.34 — 2026-08-20
- Secondary links on the website are plain underlined links now, not outlined boxes.
0.9.33 — 2026-08-20
- The Windows application has its own window bar. It shows the brigade, the incident keyword, whether you are signed in, and a coloured dot for the state — grey without a connection, amber connected, green signed in, red for an emergency call.
- It puts an icon next to the clock with the same state, so you can see it while the window is behind something else. A click brings the window back, a right click opens a short menu.
- An emergency call now reaches you even when the window is covered: a Windows notification, a flashing taskbar entry and a red icon. The alarm sound stays where it was.
- Settings have a proper dialog (F3): server address, brigade, full screen at start, keeping the screen awake, always on top, zoom, self-update, and starting with Windows.
- The key list (F1) is visible. F1, F2, F5, F11 and Esc work from the map.
0.9.32 — 2026-08-20
- The brigade list marks a brigade that has a running incident.
- The two lower blocks of the start page — creating your own brigade, and what it costs — sit without a card.
- The note about donations is shorter.
0.9.31 — 2026-08-20
- Security fixes.
0.9.30 — 2026-08-20
- The Windows application updates itself. It fetches a new version in the background, checks it against the checksum published alongside it, and installs it when you close the window — so the next start is already the new version. You can also install it right away from the notice bar.
- It never restarts itself while you are working. A computer that is left running installs a waiting update once the session has been locked for ten minutes.
- Version 0.9.21 and older cannot update themselves to this one. Install it once by hand; after that it keeps itself current.
0.9.29 — 2026-08-20
- Security fixes.
0.9.28 — 2026-08-20
- The start page follows the system light or dark setting, and its cards have more room inside.
- Android app and Windows application can now be downloaded from the start page.
0.9.25 — 2026-08-20
- In a brigade's management page the signed-in units now sit directly under the command PIN, instead of below the catalogues. During an incident they are the one thing on that page that matters: a unit that never signed off still counts in every figure and stays on the map as "no contact".
- The management page now shows the app icon in the browser tab.
0.9.23 — 2026-08-20
- The start page header is smaller. The incident PIN sits higher up and is visible on a phone without scrolling.
0.9.21 — 2026-08-20
- Security fixes.
0.9.20 — 2026-08-20
- Security fixes.
- The start page lists brigades by name only. What is going on at another brigade is not anyone else's business.
0.9.18 – 0.9.19 — 2026-08-20
- The entry sheet can be printed from inside the Android app, not only from a browser.
- The situation view stays open and keeps reporting while the print dialog is on screen.
0.9.17 — 2026-08-20
- The map asks the server for updates only as often as something is actually happening. An emergency call always switches to the fastest rate.
- The start page loads noticeably faster, and stays fast as more brigades join.
- Each brigade now has a six-digit number instead of a name in its link. Old links keep working.
- The Android app is called Firefighter Tracking.
- A device without GPS reports "in contact, no position".
- Any unit can now pass on the entry QR code, not just the command roles. The incident PIN still guards the way in.
- The entry sheet can be printed for the station wall or the vehicle.
- A brigade that is created now receives a confirmation by mail: a printable sheet with its identifier, admin password and command PIN.
- Bug fixes.
- One brigade per mail address. The address carries the password reset, so it has to point at exactly one brigade.
- The confirmation mail now carries a printable PDF with the logo.
- The QR sheet fits on small phone screens again.
- Every unit can now show and share the entry QR code, not only the command roles.
- When no incident is running, the sign-in button is gone — only "open incident" remains.
- Pressing Enter after typing the PIN signs you in.
0.9.16 — 2026-08-19
- A position set by hand on the map stays current.
- The admin area warns before mail delivery stops working.
0.9.13 – 0.9.15 — 2026-08-18 – 2026-08-19
- New start page: one line per brigade, running incidents on top.
- Separate PINs for crews and vehicles, and for command roles.
- A scanned QR code takes the place of typing the PIN.
- Unit name and type are remembered as an editable suggestion.
- Moved to fireappx.com.
- Public changelog page.
- The admin area shows whether the gateway is online.
0.9.12 — 2026-08-18
- Guide with screenshots.
- Open, rename and end an incident from the map.
0.9.8 — 2026-08-17
- Faster live updates.
- Short numeric code to join an incident.
- Emergency call alerts the units that matter.
0.9.7 — 2026-08-17
- Share an incident as a QR code.
- Clearer labels when units are close together.
0.9.6 — 2026-08-17
- Tankers carry their own symbol.
- The screen stays on.
0.9.5 — 2026-08-17
- Emergency call can be ended again.
0.9.4 — 2026-08-17
- Steadier compass needle.
- Rotating the device keeps the selected unit.
0.9.3 — 2026-08-16
- Colours follow signal-light convention.
- Admin area for brigades.
- New trackers show up when they ask to join.
0.9.0 – 0.9.2 — 2026-08-16
- Rebuilt app and server.
- Separate interfaces for desktop, Android and iOS.