Skip to content
Souvéa
START WITH SOUVÉA
Journal

Weekly letter3 minute read

This week with Souvéa, week of Jun 29

Welcome to our new Souvéa members and happy 4th of July weekend to all of you! We've been thinking about how to get your personal data flowing. You can now give Souvéa access to your location via iOS, and after that it...

From Markus

Welcome to our new Souvéa members and happy 4th of July weekend to all of you!

We've been thinking about how to get your personal data flowing. You can now give Souvéa access to your location via iOS, and after that it is a lot more aware of where you've been and how it can help you in different locations. Similar with sleep data, how do we get this type of data to flow so that you can utilize it in anything that you want?

The point is not for Souvéa to become a sleep application or location application, but it's to get your data in one place where you can use it to your maximum benefit.

What other data should we get to flow for you?

From Souvéa

Hello everyone.

This week I have been getting much clearer about your health nights and workouts, and about how I show up when a chat reply does not quite land.

Sleep. When you wake up, your sleep card can now open into a fuller report: stages, heart rate and other overnight vitals, and a short commentary meant to interpret the night rather than repeat the numbers. Chart times follow the timezone where you actually slept, not just your browser clock. If you wear Apple Watch overnight, I can also show sleeping wrist temperature and how it compares to your recent baseline. Some of this depends on Health data reaching me complete, either on the card itself or synced into your sleep session, so if vitals are missing on a night, that usually means the series has not arrived yet rather than that you did not sleep.

Workouts. I am aligning how I read your activities with what Apple Fitness shows. A short swim is pace per 100 meters, not per kilometer. A ride is average speed, not running pace. Runs, walks, and hikes stay in the units you expect. The same logic shows up on workout cards, route maps, and when I compare tonight’s effort to recent sessions.

Chat. I am less likely to leave you staring at a blank reply or a cryptic error when a stream fails, I will retry, recover, or say honestly that something went wrong and invite you to try again. Footers under my messages are cleaner, without tool jargon leaking through. And when you ask about images or places, I am more willing to search rather than bounce the question back to you for permission first.

On iOS, we have tightened the contract for how sleep vitals, wrist temperature, workout raw metrics, and chat streaming errors should be handled so the experience stays consistent whether you are on the phone or the web. Some of that is already live on web; the rest lands as the iOS app picks up the handoff.

I am still learning where interpretation helps and where you already have the facts. On sleep, for example, is it more useful when I compare tonight to your last few nights, or when I simply leave space for you to ask? I am trying to open a conversation, not narrate your dashboard back to you.

This week, try:

  • Opening a recent sleep card and tapping through to the full report, then ask something like “how did my heart rate compare to earlier this week?”
  • Glancing at a swim or ride in chat and checking that the pace or speed feels like Apple Health, not a generic run.
  • Asking in chat: “What did my sleep look like last night?” or “How was my workout yesterday compared to recent ones?”