Release v1.14​

BoatyBall Release Notes

🧩 Overview​

This is a quick fix release (v1.12.1) focused on synchronization issues, reservation flow optimization, and UI improvements for unpaid reservations and map visibility rules.

🐞 Bug Fixes​

Issue #1 — UI/Backend version synchronization​

• Fixed mismatch between UI and backend release versions.
• Restricted backend access from outdated UI versions to ensure compatibility and stability.

Issue #2 — VIP / non-VIP map browsing rules​

• Fixed map visibility rules for VIP and non-VIP users.
• Ensured reservations are hidden outside non-reservable time windows.
• Improved consistency of access control across map layers.

✨ Features​

Issue #3 — Reservation backend optimization​

• Removed redundant backend calls in reservation payment flow.
• Improved performance and reduced unnecessary API traffic in Boater reservation workflow.

Issue #4 — “Pay” button for unpaid reservations​

• Added Pay button to reservation details screen for unpaid reservations.
• Improved UX by providing direct payment access alongside reservation details.

🏷️ Tags​

bugfix, feature, backend, frontend, payments, reservations, optimization, ui

!release_date: 2024-09-10

BoatyBall Release Notes

🚀 New Features:​

UI — Google Maps integration upgrade​

• Integrated new React-based Google Maps library.
• Improved clustering and rerendering performance.
• Introduced two map types: road and hybrid.
• Improved labeling for mooring balls and POIs.

Backend — Common tracking module​

• Introduced shared tracking system for backend events.
• Adaptive UI refresh rate based on mooring reservation activity.
• Reduced network payload by sending only changed mooring ball states.
• Improved mooring ball listing performance by ~2× during extended sessions.

New mooring ball type​

• Added support for Unaffiliated mooring balls (outside BoatyBall system).

Backend — Anti fast-blocking protection​

• Prevented rapid API-based blocking of mooring balls.
• Improved reservation integrity and fairness.

Feature — Owner & Manager management improvements​

• Owners can now manage managers across all locations regardless of root location restrictions.
• Support for individual location assignment per manager.
• Added bulk removal of all locations from a manager.

Feature — Reports & scheduling alignment​

• Backend collection service rescheduled to 11:30 with 10-minute intervals for improved alignment with payment timing.

Feature — Optional geo data​

• Boater requests no longer require geo information for balls and POIs.

Feature — User experience improvements (Boater)​

• Added “Unpaid” prefix below mooring balls until payment is completed.
• Added notification for reservation cancellation when unpaid reservation expires (after 4 minutes).

🐞 Bug Fixes​

Issue #50 — POI redirect infinite loading​

• Fixed infinite loading when redirecting to non-existent POI.

Issue #51 — Non-existent mooring ball display​

• Fixed infinite loading screen when accessing invalid ball IDs.

Issue #53 — Owner create mooring ball default location error​

• Fixed issue where default location was missing on direct page load or refresh.

Issue #54 — Location tree UX issue​

• Made root locations foldable in Admin panel to improve navigation in large datasets.

Issue #152 — Hidden mooring ball exposure​

• Fixed security issue allowing hidden mooring balls to be accessed via direct API calls.

Issue #153 — Incomplete location tree in Admin​

• Fixed issue where only first 4 levels of location hierarchy were displayed.

Issue #154 — NULL check-in/out time error​

• Fixed NULL values during child location creation in Admin/Owner workflows.

Issue #56 — Hidden ball access in reservations​

• Prevented hidden mooring balls from being shown in Reservations panel.

Issue #57 — Incorrect password session handling​

• Fixed improper session handling after incorrect password entry.
• Improved authentication failure behavior.

Issue #6 — Existing user invite bug​

• Fixed issue allowing incorrect invitation flow for already active users.

✨ Other Improvements​

Owner/Manager backend enhancements​

• Improved manager assignment logic across all locations.
• Enabled granular and bulk manager location control.

Geo request optimization​

• Made geo information optional in Boater API requests.

🏷️ Tags​

backend, frontend, maps, performance, reservations, security, admin, owner, boater, bugfix, feature, tracking, api

!release_date: 2024-09-01

This release introduces major improvements to location-level promotional capabilities, enhanced URL linking for mooring balls, and a series of backend and boater-facing bug fixes. It strengthens reservation consistency, improves targeting logic, and refines the user experience for both unaffiliated and paid mooring interactions.

New Features​

Location-Level URL Linking for Mooring Balls​

• Introduced direct URL links for individual balls at the location level.
• Enables deep linking into specific mooring ball details from external or internal navigation sources.
• Improves shareability of specific balls and enhances navigation precision across the platform.

Promotion Feature for Unaffiliated Balls​

• Added promotional support for unaffiliated mooring balls at the location level.
• Allows non-affiliated or external balls to be highlighted within the BoatyBall ecosystem.
• Supports increased visibility of partner or third-party mooring assets.
• Enables location-based promotional campaigns and enhanced discovery.

Feature Enhancements​

Boater Experience Improvements​

"Not Part of BoatBall" Badge

• Introduced a dedicated badge for unaffiliated mooring balls.
• Clearly indicates when a ball is not part of the BoatyBall network.
• Improves user clarity and reduces booking confusion for external listings.

Bookings / Payments Rebranding

• Updated terminology and labeling across booking and payment flows.
• Aligns UI language with current product positioning and future scalability goals.
• Improves consistency across modules and reduces ambiguity in financial interactions.

Swain Sailing Charter Integration

• Added "Swain Sailing" as a recognized charter company in backend systems.
• Expands supported charter ecosystem and improves data completeness for affiliated operators.

Bug Fixes​

Backend Fixes​

VIP Future Reservations Propagation Issue

• Fixed delayed or inconsistent propagation of VIP future reservations.
• Ensures immediate system-wide visibility once reservation is created.
• Improves reliability for high-priority booking workflows.

Advanced Reservation Date Mismatch

• Fixed issue where "to" date could be earlier than "from" date in advanced reservations.
• Enforces correct temporal validation in backend logic.
• Prevents invalid reservation ranges from being processed.

User Targeting Misclassification

• Fixed issue where logged-in users were incorrectly cast as boaters.
• Replaced isLoggedInUser() logic with TargetUserType() validation.
• Ensures accurate user segmentation across application modules.

Sorting Logic Failure in Backend Queries

• Fixed bug where sorting by unsupported event criteria defaulted inconsistently to current time.
• Stabilized sorting behavior for unsupported or missing criteria inputs.
• Prevents unpredictable ordering in API responses.

Boater-Facing Fixes​

Unpaid Own Balls Border Styling

• Updated visual styling for unpaid owned balls.
• Replaced red dashed border with neutral blue styling.
• Reduces visual misinterpretation of unpaid status as an error condition.

Reservation Error Messaging Improvement

• Improved feedback for failed peak-time reservation attempts.
• Replaced vague "Create reservation error. OK" messaging with clearer failure communication.
• Enhances user understanding during high-demand booking scenarios.

External App Linking Fix

• Fixed broken external linking to BoatyBall app for balls and points of interest.
• Ensures deep links correctly open the intended in-app context.
• Improves cross-platform navigation reliability.

Backend Improvements​

• Strengthened validation rules for reservation time windows.
• Improved consistency of user role classification across services.
• Enhanced promotional flag handling for location-based assets.
• Optimized routing logic for external entity linking.

System Behavior Improvements​

• More consistent handling of unaffiliated vs affiliated mooring assets.
• Improved reliability of reservation state synchronization.
• Reduced edge-case failures in sorting and filtering APIs.
• Better alignment between frontend expectations and backend response structure.

Impact Summary​

Boaters​

• Clearer distinction between affiliated and unaffiliated mooring balls
• Improved reservation feedback during peak times
• More intuitive visual indicators for payment and ownership states

Operators / Admin / Backend Systems​

• Stronger reservation consistency and validation rules
• Improved user targeting accuracy
• Enhanced support for promotional content at location level

Platform-Wide​

• More stable sorting and filtering behavior
• Improved deep-linking and external navigation support
• Expanded charter ecosystem support

Stability & Reliability​

• Fixed critical backend propagation issues for VIP reservations
• Improved robustness of reservation date validation
• Reduced UI misinterpretation risk for unpaid assets
• Stabilized external linking and routing behaviors

!title: Release v1.13.0 - Promotion / URL to Location Enhancements !tags: boating, backend, frontend, promotions, reservations, bugfix, feature !release_date: 2024-08-15 !description: Introduces location-level URL linking and promotional support for unaffiliated mooring balls, alongside backend fixes for reservation propagation, sorting logic, and user targeting improvements.

Release date: August 2024

🐞 Bug Fixes​

Issue #137 — Cancel already cancelled reservation​

• Fixed backend behavior allowing repeated cancellation attempts on already cancelled reservations.
• System now correctly handles idempotent cancellation requests.

Issue #39 — Cancel reservation UI logic​

• Fixed cancel button visibility rules for non-reservable balls.
• Improved enable/disable logic for reservable states.

Issue #42 — Unclear booking restriction message​

• Improved user-facing message for non-bookable moorings.
• Message now provides clearer explanation for Boater users.

Issue #136 — Manager invitation cancellation inconsistency​

• Fixed issue where cancelled manager invitations remained in INVITED state in backend.

Issue #48 — Reports white screen issue​

• Fixed edge-case causing blank screen in Reports module under certain conditions.
• Added additional safety checks.

Issue #49 — Payment screen not updating after refund​

• Fixed UI not refreshing after refund operation in Payments screen.
• Payment details now update immediately after refund.

Issue #142 — Manager invitation resend failure​

• Fixed missing backend implementation causing 404 errors when resending manager invitations.

Issue #148 — Reports crash on cancelled data​

• Fixed backend exceptions occurring when generating reports with cancelled reservations.

Issue #149 — Incorrect cancelled report summary​

• Fixed incorrect summary calculations when cancelled reservations are included in reports.

✨ Features​

Issue # — Anonymous user data privacy​

• Boat names and reservation details are now hidden for anonymous users.
• Improves privacy and data protection across Boater UI and backend.

Issue #40 — Contact link improvements​

• Added tel: and mailto: prefixes to all phone numbers and email addresses across applications.
• Enables direct click-to-call and email functionality.

Issue #28 — Admin user search enhancement​

• Added ability to search users by boat name in Admin panel.
• Backend updated accordingly (Issue #138 dependency).

Issue #41 — Payment date range presets​

• Added quick date range filters in Admin Payments:
  • Yesterday
  • Today
  • Week
  • Month
  • Custom range

Issue #139 — Owner API enhancement: locations & managers​

• Extended /v1/owners API to include locations and manager details.

Issue #43 — Admin users: owner location visibility​

• Added display of owner locations and managers in Admin Users screen.

Issue #44 — Admin user notifications​

• Added self-closing notifications for user actions (activate/deactivate, reservation toggles).
• Improves admin feedback and UX clarity.

Issue #140 — Manager API location details​

• Extended /v1/managers/{id} API with location data.

Issue #45 — Owner manager location management​

• Added ability for owners to add/remove manager locations.
• Includes UI actions and notifications.

Issue #141 — Multi-location manager invitations (backend)​

• Updated invitation API to support multiple locations per manager.

Issue #46 — Multi-location manager invitations (UI)​

• Added UI support for selecting multiple locations when inviting managers.

Issue #143 — Admin manager API extension​

• Extended manager API to include assigned locations in response.

Issue #47 — Admin managers location display​

• Added location lists for managers in Admin Users interface.

🧭 Tags​

boatyball, release, ui, backend, bugfix, feature, admin, owner, boater, payments, reports, permissions, invitations, locations

!release_date: 2024-08-01

BoatyBall UI Release v1.11.1 delivers a focused set of bug fixes and feature enhancements across Boater, Admin, Manager, and Owner roles. This release improves mobile usability, payment workflows, map rendering accuracy, navigation stability, and overall admin visibility into transactions and user management.

Feature Enhancements​

Boater Experience Improvements​

Boat Name Visibility at Zoom Level

• Reservable balls now display the boat name at the same zoom level as the ball number.
• Improves clarity when multiple reservations are clustered or viewed at mid zoom levels.
• Enhances situational awareness during navigation and booking review.

Card Holder Name Field Removal

• Removed unnecessary credit card holder name field from payment flow.
• Streamlines checkout experience and reduces form friction.
• Aligns UI with updated payment data requirements.

Signup Confirmation Code Resend

• Added resend verification email functionality during signup.
• Users can now request a new confirmation email if the original is not received.
• Improves onboarding success rate and reduces signup abandonment.

Admin Improvements​

Transaction History View

• Introduced payment history view for refunds and transactions.
• Admin users can now track payment lifecycle events in a centralized interface.
• Enhances financial transparency and audit readiness.

Phone Number in Expanded Rollups

• Added phone number display in expanded payment rollup view.
• Improves user identification during payment review workflows.

Default Users Tab Behavior

• Users page now defaults to the Boaters tab.
• Reduces navigation friction for frequently accessed user category.

Payments Panel Redesign (Manager Scope)

• Payments panel now grouped by location.
• Balls are sorted by ball number for consistent ordering.
• Improves readability and operational efficiency.

Bug Fixes​

UI and Rendering Issues​

Activity Icon Rendering Issue

• Fixed incorrect rendering of the "Activity" icon across all views.
• Ensures consistent iconography across UI components.

Map Rendering Incorrect Zoom Behavior (Owner/Manager)

• Fixed issue where payment detail map defaulted to world view.
• Map now correctly centers and zooms to ball location.

Authentication & Signup Issues​

Mobile Signup Scroll Blocking (Admin/Owner/Manager)

• Fixed issue where submit button was not visible on mobile devices.
• Enabled proper scrolling behavior on invitation signup pages.
• Prevents users from getting stuck during onboarding.

Invitation Signup Error Handling

• Fixed "Oops! Something went wrong" error occurring after invitation signup submission.
• Corrected redirect flow from error state to payments screen.

Payments System Fixes​

Refund Dialog Validation

• Fixed issue requiring amount field incorrectly in refund dialog.
• Refund process now validates correctly without unnecessary input requirements.

Cancelled Reservation Status Bug

• Fixed issue where recently cancelled reservations still appeared as booked.
• Reservation status now updates immediately after cancellation.

Manager & Owner Fixes​

Broken Route Handling

• Fixed blank screen and console error when navigating to invalid routes (e.g. /map).
• Added proper fallback routing and error handling for non-existent paths.

Mooring Balls Sequence Mixing

• Fixed issue where balls from different locations were incorrectly merged into a single sequence.
• Ensures correct grouping and isolation per location.

Stability & Performance Improvements​

• Improved consistency of state updates across reservation and payment modules.
• Enhanced error handling for invitation-based authentication flows.
• Reduced UI flickering in payment and admin dashboards.
• Strengthened map rendering pipeline for location-bound entities.

Role-Based Summary​

Boaters​

• Improved signup flow reliability
• Enhanced reservation clarity (boat name visibility)
• Simplified payment form experience

Admins​

• Better financial oversight with transaction history
• Improved user management default navigation
• Enhanced payment rollup details

Managers & Owners​

• More stable navigation and routing
• Improved map accuracy in payment views
• Cleaner payments panel organization

Known Improvements Delivered​

• Mobile usability fixes across invitation flows
• Payment system consistency improvements
• Map rendering corrections
• UI cleanup and form simplification

!title: Release v1.11.1 !tags: boating, UI, bugfix, feature, payments, admin, manager !release_date: 2024-07-15 !description: BoatyBall UI release v1.11.1 focuses on improving signup flows, fixing mobile and map issues, enhancing payment transparency, and refining admin and manager dashboards for better operational control.