Does v2 have an export all feature? It seems to be sorely missing, even from the in-browser version.
Related, the phone app should have offline session storage. The amount of storage it needs is negligible, but without offline storage, the loading of sessions when opening the app is unreliable (not every windsurf spot has good service) and it is excruciatingly slow even on wifi. It’s just a poor user experence. The offline cache of sessions could be updated from server on every startup, so new sessions recorded on other devices would still load.
Export: A bulk export feature is on the roadmap, but won’t make it into this year’s releases. I’ll note the demand.
Performance: Recording works offline by design – analysis does require a connection, which is a known limitation at spots with poor coverage. Session-level caching is something I’m aware of and want to improve.
One question: where are you located / which region are you sailing in? Loading times can vary depending on network conditions in your area, and it would help me check whether there’s a CDN issue on my end.
I just launched the app on my home wifi. I have 60+Mbps down with a 4ms ping so the network connection is fine. The first sessions load quickly but the app hangs up all the time when I try to scroll down to old sessions. Hardware is pixel 6a. Maybe it’s not the network connection but some other performance issue inside the app. Maybe loading the month images slows it down, which would be ironic as I find those needless and annoying to begin with.
Anyway, an app that doesn’t work offline (it doesn’t show previous sessions) and is slower than the old app is a big step backwards for me. If analysis doesn’t work offline, that’s not great but acceptable… not showing all my old sessions is a dealbreaker. Moving everything to the cloud without full user access and control is a bad direction too. I will downgrade to the old app and see if these are fixed in the future.
On the plus side, I like that the speed section now shows on the track where I got each of the top speeds, but that’s a small improvement compared to a couple of large steps backwards.
Your description sounds like the first sessions load fine, but scrolling down to older ones causes the app to hang. Can you confirm that’s what’s happening? If so, that’s a specific issue I’d like to look into. I was actually at Lake Balaton recently and didn’t experience any slowdowns there, so your description is puzzling – which is why I’d like to narrow it down.
Does it also happen when you rotate the phone to landscape mode?
On the month images: these are bundled in the app, not loaded over the network, so they’re not the culprit here.
On the cloud architecture – I hear your frustration, and I want to be transparent about the reasoning. The cloud approach was a deliberate decision driven by frequent user requests: it enables multi-device use, gives you a proper web interface on a large screen, and means your data isn’t lost if something happens to your phone on the water. The server-side analysis also allows for significantly more detailed results than was possible on-device – especially important for users on older or lower-end hardware. And when I fix or improve the analysis algorithms, everyone benefits immediately without waiting for an app update.
That said, the scrolling behavior you’re describing is a real issue and I want to get to the bottom of it. Let me know what you find with the browser version.
The scrolling is a little choppy in the browser too. From what I remember it was worse in the mobile app but I’m already back on V1 so I can’t test.
I’d bet money it’s some version of a slow server or connection. Everyone thinks their server will be blazing fast and storing everything in the cloud will solve all problems but it never works out that way. Just store a permanent local copy of all the data on the mobile device and the app will run smoothly.
Storing everything in the cloud to enable multi-device use and having a web interface is a good feature, but not if it breaks the basic functionality of the mobile app. Not having my old sessions load if there is no data connection is just not an option. That also means when your servers go down I lose all my sessions. Then add the lack of a bulk export to this… there’s no way I’m using an app that traps my data like that, let alone paying a very hefty price for it.
There was some bug in the importing/exporting of sessions so some of my sessions got lost and scrambled when I downgraded to V1, and there is no map view… so currently, most things I loved about windsporttracker are missing or broken. I should not have updated without checking what the update contained… I guess I trusted you a little too much not to break things that worked fine for years.
Anyway, if there is a possibility of proper permanent offline storage of all sessions and bulk exports, then I will check back occasionally. Otherwise I will have to live with V1 or find a different app. Unfortunate.
On the scrolling: the app loads sessions incrementally as you scroll – there’s a brief moment when the next batch is fetched, which is by design. If “choppy” means something beyond that – longer hangs or visual glitches – I’d like to understand it better, but without V2 access it’s hard to investigate now.
On the session loss in V1: a V2 export isn’t compatible with V1 – the formats are different, so downgrading was always going to be lossy. If you can tell me specifically what happened, I’m happy to look into it.
On data security: V2 runs on dedicated servers in Germany, built to German data protection standards. In V1, if your phone is lost or breaks, your data is gone – that’s what prompted the move to cloud storage. It’s also what makes more detailed server-side analysis possible, which older or lower-end devices simply can’t do on their own.
The subscription covers real infrastructure and ongoing development costs – at €27/year via web, that’s less than a wetsuit repair. I understand it’s not the right fit for everyone right now, and the door stays open.
Wait for the next batch of sessions to load “by design”? Why? Why? And again, why? You want things to load instantly and work smoothly.
V1 and V2 exports being incompatible is a major fail, obviously.
I don’t worry about somebody stealing my data. I don’t want my data to get lost when windsporttracker gets ransomwared, or there is some catastrophic hardware failure, or the business goes belly up and the server gets shut down, which it will eventually. Everyone thinks their business will outlast its users, but none of them do. The solution is on-device storage and an easy bulk export feature so users can easily back up all their stuff if they want to. If you don’t provide this trivially simple feature, then the obvious conclusion users come to is that you want to make it hard for them to move their data out of your service and take it somewhere else.
It’s easy to combine the benefits of on-device functions and server-side functions. If you don’t want to, then you will have fewer users. Simple as that.
Incremental loading is standard practice for cloud-based apps – it’s why the first sessions appear immediately. The alternative would be waiting for everything to transfer before seeing anything. A search and filter function for sessions is already on the roadmap, which will make navigating older sessions significantly faster.
On data portability: WST already offers export in 4 different formats. A bulk export is frequently requested, but “trivially simple” undersells the engineering involved significantly – on-device sync introduces real complexity around data consistency, version compatibility, and subscription validation across devices. With 30 years of professional software development behind WST, I’m confident in that assessment. That complexity is also why apps that go down that route typically ship major updates every 6–12 months. The current architecture lets me respond to user feedback quickly – as you can see from other threads in this forum.
To be direct: a full offline sync as you’re describing is not something I’m planning to implement.
As a wind sports athlete and daily user of WST myself, I have as much interest in data reliability as anyone. Your concern about service continuity is legitimate – it’s also why individual session export exists today.