UPDATE ON PERDIX 3 INTEGRATIONS AND THIRD PARTY DIVE LOGGING

Dear Valued Development Partners, 

We wanted to provide an update on the future of third-party dive log integrations and the Perdix 3 platform. 

Historically, Shearwater has been very supportive of third-party dive logging applications, and that philosophy has not changed. We believe divers should be free to use the software that works best for them, and we want to continue supporting a healthy ecosystem of dive applications. 

With the introduction of Perdix 3, however, the underlying Bluetooth architecture has changed significantly. The new platform is designed around an always-on connection model and a future where dive computers can automatically synchronize with a diver's phone whenever they are nearby. This creates a much more seamless experience for divers, but it also changes how external applications can integrate with the ecosystem. 

Rather than having every third-party developer maintain a direct Bluetooth integration for each generation of hardware, our long-term direction is to provide a standards-based account connection model using OAuth. In this model, a diver can choose to connect their Shearwater account to trusted third-party applications and authorize those applications to access their dive data. 

We believe this approach offers several advantages: 

• Developers only need to maintain a single integration instead of adapting to changes in dive computer firmware, Bluetooth implementations, mobile operating systems, and hardware generations. 
• Divers benefit from automatic dive log synchronization without needing to manually manage transfers.  
• Partner applications receive access to dive data through a stable interface that is less likely to be affected by future hardware changes.  
• Divers remain in control of which applications can access their data and can grant that access on an application-by-application basis. 

For these reasons, we are not planning to support new direct Bluetooth integrations on the Perdix 3 platform. Instead, our focus is on building a partner integration framework that enables authorized applications to receive diver-approved dive data through account-based connections.  

We believe this will create a better experience for developers by removing the need to maintain hardware-specific Bluetooth integrations as devices, operating systems, synchronization technologies, and future generations of dive computers evolve. 

In the meantime, divers can continue to synchronize their dives through Shearwater Cloud and export their dive logs in UDDF format for use with compatible third-party applications. 

We are actively developing the partner integration framework and are currently targeting initial developer availability this fall. As with any new platform, timelines may evolve as development progresses, but we wanted to share the direction we are heading and the reasoning behind it. 

We appreciate the patience of the developer community while we build this system. Our goal is not to make access to dive data more difficult, but rather to create a more reliable, scalable, and future-proof integration model that benefits divers, developers, and partners alike. We look forward to sharing additional details as the program continues to mature. 

Thank you for your continued support of Shearwater divers.