December 2025

• Fixed an issue with the "Wind Map" that on some devices caused the map to not show.
• Added Sailing World Cup format with five-minute sequence, instead of the six and four which existed already.

April 2025

• For Android 14 compatibility added another way of scheduling "flag pole" and race log synchronizing events without requiring "exact alarm" permission.

March 2024

• Added "AIN" as pseudo country code.

August 2023

• Added a new racing procedure SWC_4MIN for kites and windsurfers with a shortened four-minute start sequence with green flag for one minute after start.

July 2023

• Added "SCA" as an invalid result marker (IRM) / redress code.
• Penalty codes / invalid result markers (IRMs) are now sorted alphabetically in drop-downs to select from

June 2023

• Bug fix: do not show the "set protest time" dialog when displaying AP over Hotel or November over Hotel.

April 2023

• Bug fix: added missing handler for Olympic mode Race Log events such as the "result are official" confirmation event.
• Backward compatibility fix: accidentally introduced dependency on newer Android API 24 which caused trouble on older Android versions, e.g., before Android 7.x.

June 2022

• Bug fix: When starting the app after killing it, with unsent messages buffered, fixed loading the messages from the persistent store.
• Bug fix: Big protest flag (Bravo) button on the right side of the screen had no effect until the navigation drawer was pulled in from the left.

May 2022

• A variant of the RRS26 five minutes sequence has been added that shortens the sequence to three minutes, with class up at 3, mode up at 2, mode down at one, and class down at start.
• Bug fix: when filtering for current races, empty series not containing any races caused an internal, invisible error that led to the "Current Races" list staying empty. Now, you can model empty series that have subsequent series with races, and those races from the subsequent races can then be displayed as "current."

October 2021

• The LEADERBOARD:UPDATE permission is now enough again for Race Committee App users to see all competitors for result entry. Due to a security check too strict, READ permissions for the non-public competitor fields were required before which shouldn't have been required.

July 2021

• The date picker for setting the finishing time of a competitor only allows dates equal to the begin of the finishing phase and above.
• A Slovenian translation of the user interface has been added.

June 2021

• Events without proper start or end dates no longer cause problems.

April 2021

• Fixed a problem with the date picker for blue flag events; previously, changing the date did not work properly and used to snap back to the current date.

February 2021

• The solution now supports the new Olympic penalty code (IRM) "NSC" ("Did not sail the course").

December 2020

• Added support for upcoming QR codes containing additional information about the event, course area and position to pre-select. These QR codes can significantly speed up onboarding and sign-in.
• Logout in the settings now clears the access token and stops monitoring your races.

September 2020

• Dependent start times now correctly transmit the race course area ID for display in the Regatta Overview.
• Fixed not running timer below a flag in the navigation drawer.

August 2020

• A problem with loading ORC PCS implied wind source settings for races has been fixed. This problem could have caused the race manager app to fail to load the race logs from the server if only one of them had an "implied wind source" setting of "None".

May 2020

• Leaderboards and regattas can now be configured to take place on more than one course area. This way, users on different course areas can see the races from those regattas in their SAP Sailing Race Manager app race inventory. A typical scenario is a regatta racing the opening series in split fleets (Yellow/Blue during qualification, Gold/Silver during final) where different fleets sail on different course areas at the same time. The course area you choose during log-in is now recorded in the start time events which allows the web site to show which race runs on which course area, even if the regatta races on multiple course areas.

April 2020

• The date of the start time can now be chosen via a suitable date picker. When you tap "SYNC TO MINUTE", you can adjust the seconds by one second and the milliseconds will stay. The next adjustment will clear the milliseconds.
• The app now accepts a date for the blue flag up and down event and is no longer limited to the current day.
• We fixed an issue where the blue flag countdown in the navigation drawer was not running.
• We have improved and unified the representations of times and countdowns.
• Blue flag up and down events can now be revoked, e.g., after accidentally using it.

March 2020

• Problems with conflicting result entry through multiple devices used for the same race have been resolved. For more details, see here.

October 2019

• When finishing times are entered, the invisible milliseconds are now set to 0 when using the time picker. Before, the milliseconds were set to those of the time stamp when the time picker was initialized which led to imprecise time stamping.
• The app is now compatible with servers that use the new ORC Performance Curve Scoring (PCS) ranking metric with its new race log events. It does, however, not yet support capturing or displaying those new event types, such as setting the scratch boat for corrected time baselining or defining the leg types and distances for PCS scoring. This will be added in a future release.

July 2019

• The app no longer remembers the last entered duration when setting a protest time. The protest duration can now be configured correctly in the app settings. Please consider that a protest duration in the specific regatta configuration is preferred to the protest duration in the default regatta configuration.

May 2019

• The Course editor now works correctly when managing more than one regatta. The last course design and the defined marks are now cached per race group.

February 2019

• Now we consider the start mode flags created in your device configuration and will no longer use the default start mode flag if it hasn't been configured.
• Improved the back navigation at several points.

February 2018

• The protest time is now configurable in the backend. An empty value means, the RCApp will take 90 minutes as default. If no time is set in the backend, the RCApp will save a custom duration as new default. A server side duration (device or regatta specific) will always be the default.

August 2017

• The result list can now be edited without a finish time.

June 2017

• It is now possible to capture results during any phase of a race, particularly also during the start phase, making it possible to enter penalties such as OCS, BFD or UFD when they occur.
• When adding a result for a competitor, this result can be "reset" in two ways: either the entry is swiped from the result list (trash can). This way, no update will be sent to the server for that competitor until it is added again to the result list. If instead any explicit score for the competitor is cleared, the rank is set to 0 and the penalty is set to "NONE" then the competitor will remain in the list, and this "empty" result will be sent to the server, clearing any previous score corrections that were sent to the server. This is the only way to "reset" an erroneous score correction entirely from the app, because swiping and thus removing the competitor from the list would leave the previous score correction unchanged on the server upon the next result publication.
• When entering and publishing partial results, updates will only be applied for those competitors for which a result has been entered. In particular, when operating with multiple devices on the same course area and in case the devices haven't synchronized their states yet this will make sure that partial results entered on one device will not unnecessarily remove changes applied on another device.

April 2017

• The "By Marks" course editor can now handle any valid CSS color for mark colors.
• When using the "By Marks" course editor together with the TracTrac connector, it is now possible to construct gates and lines if they have previously been created in a course in the TracTrac Event Manager. In this case, the TracTrac control point consisting of the respective two marks is identified and used. This enables using this course editor also at events outside the Extreme Sailing Series (ESS) where some special treatment had enabled the use of the "By Marks" course editor in the past.

January 2017

• Phone only (xhdpi and higher): If the font size (Android display settings) is larger than default, the summary screen will be use a different layout (two lines instead of one). This way the layout will not wrap the time or labels.

November 2016

• The protest time is now more configurable. You can set the start time and the duration. The default protest duration is 90 min and the last duration is stored in the settings, so you don't need to change it the next time.
• If the protest time is set for a race, it is shown in the race summary view.
• Support for a new racing procedure for the Sailing World Cup with specific count-down procedure
• Fixed a bug regarding protest time entry in smartphone version in case of split fleets
• The "Postpone" button is now hidden once a race has entered the "finishing" phase (after blue flag up)

October 2016

• Fixed missing German translations for some buttons and labels

September 2016

• The wind map is now opened in an external browser, so it is possible to switch between app and map more easily.

July 2016

• Finishing races in the TimePanel show the race duration of the "first ship home."

June 2016

• The start time editing screen has now a "Sync to minute" button, which replaces the both buttons beside the countdown. This button sets the countdown to the nearest minute and after "Set time" the new start time will be sent to the server.
• The "Set Time" button in the start time editing screen remains disabled now until the user actually makes a change. This also helps to identify that "Set Time" needs to be tapped in order to transmit a change carried out using the "Sync to minute" button.
• Changing the server, signing out, changing hidden event visibility, and changing the regatta now properly ensures that the content is refreshed based on the new settings.

May 2016

• A bug related to entering the passing instructions for a waypoint in the "by-marks" course designer has been fixed. At the same time, for now the passing instructions "Offset" and "Fixed Bearing" are no longer offered until the application really offers support for them, particularly during mark passing calculation.
• Swiping the start time button to the left to reach the other buttons for entering the racing procedure, start mode flag, etc. now works reliably, also in case of multi-touch which may have made the app crash before.
• Regatta-specific preferences now properly take precedence over the device configuration. They are updated from the server when the regatta content is refreshed.

April 2016

• Whether or not result entry during or after the finishing phase is offered is now a preference under "REGATTA CONFIGURATION (DEFAULT)." The device configuration managed on the server can remotely manage this configuration setting. With this, it is possible to configure up-front whether a race officer is offered the possibility to manage results directly from the Race Manager app. This should not be used if an external, official regatta management system is being used to capture and manage the official scores.

March 2016

• Added sign in/sign out into the app. The user has to be create in the backend, with leaderboard permission. Without the permission, the user can't send data to the server.
• We changed the QR Code, so it includes the user's access token. There is also a possibility to manual login into the app, if no QR Code is available. The app doesn't store username and password.
• The behavior of the red share icon has also slightly changed. If it is red and tapped, it will call the server to check, if the users access token is still valid. If not the server response with a 401 error code and the user has to enter his credentials.
• You can force a user sign out within the overflow menu, if you need other user credentials.

February 2016

• Added responsive design. You can now use the app on every tablet as well as on mobile phones.
• We returned the group races switch to ESS races. It's located in the left panel bar (or top on phones).
• The behavior of ESS course designer is compact in two lists. The marks and rounding can be easily changed by tapping on it.

August 2015

• Fixes for Android Lollipop were deployed. They solve font size and other display issues.
• The true wind direction provided during wind entry in the app is now interpreted to be a direction based on magnetic north, not true north. This is common practice as wind readings are typically produced on a start vessel based on a magnetic compass device.

July 2015

• Added support for dependent start times. Races can set their start time relative to another race's start time. Caveat: Currently, when aborting races on which other races depend, requires either aborting the dependent races before or setting an absolute start time on the dependent races.

June 2015

• Major overhaul of the entire race committee app. The app has a completely new user interface with a light and a dark theme. The functionality generally remained unchanged.

July 2014

• The race list is now ordered by fleets. This means we display the same order of our backend system in the RCApp. Now the race officials can easily use the order which is displayed and do not have to care about the fleet color order.

March 2014

• Moved away from using a label to create a course and introduced a big button that eases the input of courses.
• Added a new countdown button for ESS and RRS26 start configurations. Using this button one can easily set the start time of a race to exactly the time the countdown starts.

January 2014

• Server-based device configuration
• Device initialization with QR codes
• Automatic upgrades and downgrades to match server software version
• Multiple devices can work on the same race (e.g., start vessel, finishing vessel, shore control)