Byrd releases

At Byrd we think good software can only be created if people building product are open and transparent about their releases. This is our attempt to do that for our own product.

0.4.5

Apple status:

Pending review

Play status:

In review

Date:

March 23, 2022

General release notes

A small point release to solve a bug with the new way initial user totals were being divided.

0.4.4

Apple status:

Play status:

Date:

March 23, 2022

General release notes

This release should reduce the amount you’re looking at a loading screen in Byrd. We’ve increased the stability of how items load and the order they load, especially on the homepage.

New features

Pace of average run week We’ve been asking how long you run in an average week, which is a hard question to answer. We all tend to round to the nearest hour but that can make a really big difference to how fast Byrd thinks you’re running. We’re now asking about your pace to make it easier.

Bug fixes

Loading states within app Byrd consumes a number of “streams” of data. We were kind of allowing those streams to crash into one another and cause loading chaos. We’ve improved how we’re orchestrating these data flows, which should result in a much more responsive app and much less loading.

Generating ‘runner state’ when building runs The ‘runner state’ is how Byrd tries to understand us as humans. This gets built fairly frequently but sometimes not frequently enough to avoid potentially incorrect runs to be recommended. We now rebuild the ‘runner state’ everytime we’re building future recommendations to avoid having stale data.

Known issues with the release

We are still relying on the EQAI-coach that we launched with the product back in January. This release contains a lot of the code necessary for the next evolution of how runs are being recommended but we need a few more days of testing. We’re aiming to get it released in a limited way by the end of the week.

0.4.3

Apple status:

Pending review

Play status:

Pending review

Date:

March 21, 2022

General release notes

This release is the first part in our ongoing efforts to improve the recommended runs for the majority of our users. We’ve added a couple of features that give our users early access to the new experimental recommendation generator.

New features

UI performance improvements

We updated the underlying framework to get rid of some sporadic errors and enhance the app experience.

Initial steps in recommended run improvements (more on the way)

We’ve updated some of the analysis that gets performed when you go for a run. This will feed into the new run recommendations.

Access to experimental recommendations

Version 0.4.3 sees the introduction of experimental recommendations. In the Preferences section of the settings, users can now see the Experimental recommendations option - in this screen you can choose whether you want to use the stable recommendations (the from the existing run generator) or the new experimental recommendations. These are currently being supplied by what we’re calling the “unconstrained generator” - it looks at what kind of running you’ve done over the last 8 weeks and tries to replicate the same patterns back to you.

This work will likely be superceded by further work on recommendations but we wanted to give everyone who’s interested the chance to take a look.

Known issues with the release

Run recommendations are still on the road to improvement. We think there’ll be another update in the near future with more work done in this area.

We’re also still aware that the home page of the app looks very volatile when updating - we’re going to get this done in time for the next release.

0.4.2

Apple status:

Expired release

Play status:

Expired release

Date:

March 19, 2022

A point release that was overwritten by release 0.4.3.

0.4.1

Apple status:

Latest release

Play status:

Latest release

Date:

March 9, 2022

General release notes

Version 0.4.1 Fixes a couple of bugs and builds towards better recommendations - most of that work won’t aff

New features

Removed Back-to-back recommended runs

Back-to-backs are particularly intense sessions and whilst the recommendations haven’t been quite right that means the risk of these sessions causing problems for our users would be higher than we can accept. We might introduce them at a later date, when the generated recommendations are better across the board.

Bug fixes

Blank screen issues

We’ve had a couple of reports of some blank screen issues being hit by some users. We’ve updated some code that should stop these but we’re keeping a close eye on it in case anything changes.

Carousel cards now remain dismissed

The carousel cards on the home screen each have a dismiss button on them. Whilst these worked, they only dismissed the card for a very short time, so we’ve changed this now so when you tap on them they will be dismissed for a longer period.

Garmin workouts not receiving the changes to session difficulty

In our previous release, we introduced a slider so users could modify the difficulty of a session by adapting the paces on the session. At the time, we overlooked that these changed paces would need to be included in the workout that Garmin receives. We’re sorry about that - in this version it’s been amended to account for the difficulty our runners select.

Known issues with the release

Pacing and duration on recommended runs is still a priority for us. The work we’ve done over the past few days has been focussed on this problem, and we’re aiming to get the first version of this revamped recommended run generation out very soon - so watch this space.

We’re also still aware that the home page of the app looks very volatile when updating - we’re going to get around to this once the recommended runs have been improved.

0.4.0

Apple status:

Expired public release

Play status:

Expired public release

Date:

March 4, 2022

General release notes

Version 0.4.0 is a small feature update.

New features

Post run mood feedback

We’re keen to keep improving the holistic side of Byrd - trying to make sure that it always replays how you feel about your running and always aims to give you something more. To that end, when you add a run to Byrd now you have the option to record your mood and track it against your running. In future releases, we’ll add more to this post-run flow, and also add to the places where you can see your mood.

Warning before deleting a run

We’ve had a couple of our runners say that they’ve deleted runs when they’ve not meant to. We’ve added an alert dialog to give everyone a chance to stop and think before deleting a run (an action that cannot be undone at this point).

Known issues with the release

Pacing and duration on recommended runs is still a priority for us. We’re building on the improvements in previous releases but it is a complicated system so please bear with us.

We’re also still aware that the home page of the app looks very volatile when updating - we’re working to smooth that state out and improve it going forward.

0.3.17

Apple status:

Expired public release

Play status:

Expired public release

Date:

March 3, 2022

General release notes

Version 0.3.17 includes adds a few more features and a couple of bug fixes

New features

Durations as ranges

Byrd’s recommended runs have been a little too specific for a lot of people, so we’re trialling something in this release. Whenever your run is not an event, Byrd will give you a range of durations to aim for instead of a specific duration.

Everyday goals persisting

We’ve had quite a lot of feedback that everyday goals not persisting is a big deal - if you set a weekly everyday goal, you don’t want to have to set it again the following week. We’ve amended this, so now if you set a weekly goal it will persist for 16 weeks, and monthly goals will persist for 4 months.

Warm up and cool downs on structured runs

Recommended runs with a structured session - such as an interval or a pyramid session - should be done with a warm up & cool down. We include an arbitrary 5 minute warm up/cool down instruction in the session that can be pushed to Garmin watches, but didn’t display it in the session details. We’ve changed this so that everyone can now see that for structured runs in particular, you should be doing a warm up & cool down.

Bug fixes

Weeks left not updating on event goals

Some of our runners were reporting that the number of weeks left on event goals wasn’t updating. We’ve fixed that on this release.

Limit everyday goals charts to the earliest goal

Previously, runners could hit the previous period button on the goals charts as far as their data went, but this seemed a bit pointless, because the charts and the cards wouldn’t show anything useful unless you has set at least one goal for the period. Now when hitting the back button, users can only navigate further back if they have goals present in the past.

Known issues with the release

Pacing and duration on recommended runs is still a priority for us. Even with the improvements in this release, we want to make sure that we’re recommending the right run at the right time.

We’re also aware of the fact that the home page of the app looks very volatile when updating - we’re working to smooth that state out and improve it going forward.

0.3.16

Apple status:

Expired public release

Play status:

Expired public release

Date:

February 28, 2022

General release notes

A couple of features in thie release and some pretty big bugs solved.

New features

Improved durations on recommended runs

This release is the first step in updating the duration algorithms, but it’s pretty big so we hope our users will see the improvements. Further updates will continue to work on it.

Removed structured runs from less intense spaces

The Spaces - or training modes - should reflect what you want to accomplish with your running. Given the way our generator works, our runners could have been presented with a speed run even if they had selected “Breather” as their space. This update fixes that, so if you want to slow down and take in the view, you can.

Customer emails

We were originally going to include this in an earlier release, but we wanted to make sure we got it right. So now our runners should receive emails when hitting certain milestones.

Bug fixes

Crash when editing an everyday goal

We were alerted this morning to an issue affecting users trying to update or add new everyday goals - specifically for durations. We tracked the bug down and have included the fix in today’s release.

Amended default pacing

In the last release we included an update to allow users to adjust their pacing on recommended runs. We added this in response to a lot of our runners saying that the recommendations were too intense, but whilst the ability to control paces is great getting it closer to being correct is our aim at Byrd. So we’ve adjusted the paces down. If you feel that the defaults are now too slow for you, please reach out.

Users stuck in plan regenerations

Some of our runners found that their plan would start regenerating and the UI in the app would get stuck in that state. We’ve fixed this now so that the UI doesn’t linger in this state for any longer than needed.

Removed progression runs

This is slightly similar to the above feature about structured runs being removed from less intense spaces. The major difference is that progression runs were too intense all round - not for specific training modes. So - for the moment - we’ve removed them from the app. You shouldn’t see them after your next plan regeneration.

Fixed a UI bug with the duration form

The duration form had what you might call a question and answer button underneath it. On some screens this was wider than the screen and didn’t overflow to the space beneath it. We’ve fixed this small bug on this release as well.

Known issues with the release

Pacing and duration issues are hopefully going to look improved in this release - but we are not done yet! There’s more to be done to get this working correctly, so we’re putting in the effort now to make sure you’re next run is the right run.

We’re also aware of the fact that the home page of the app looks very volatile when updating - we’re working to smooth that state out and improve it going forward.

0.3.15

Apple status:

Expired public release

Play status:

Expired public release

Date:

February 25, 2022

General release notes

Version 0.3.15 sees the reintroduction of discount codes on iOS, after a previous update removed them in order to remain compliant and be able to release updates to the app store. There’s also a nice new feature for our runners to enjoy.

New features

Adjust run pacing on recommended runs

Think a run is too fast for you right now? Or maybe a little too slow? We’ve introduced a new control to the recommended run detail page that let’s you change the run pacing a little.

Bug fixes

Reintroduction of discount codes on iOS

After a previous build was rejected for not conforming to Apple’s terms of use, We removed the discount code mechanism we had in place. We’ve now brought it back in but it will comply with Apple’s terms because the mechanism used is controlled via the App Store. If you’re a discount code holder with an iPhone and haven’t used the code yet, the old code won’t work anymore. Reach out to us if you need a new one and we’ll be happy to oblige.

Known issues with the release

Pacing and durations on activities are not quite in the state we’d like them to be yet for all users, we’re working on a more sophisticated way of calculating how long people should go out for each run.

The ability to adjust pacing should give help users get more control of their runs individually, and we’re working on ways we can further improve pacing for our runners.

We’ve continued on the groundwork done in v0.3.13 to overhaul durations, but it will take time to get these into Byrd. Thank you for bearing with us.

0.3.13

Apple status:

Expired public release

Play status:

Expired public release

Date:

February 23, 2022

General release notes

We’ve got a couple more features and a couple of bug fixes in for version 0.3.13. Read on to find out what’s new.

New features

Notification when an experience is unlocked

Unlocking the experiences to enhance the Wilds is one of the most unique aspects of Byrd. Now when you do, you’ll get a notification that the experience has been unlocked.

Confirmation emails

We want to make sure that users know when they’ve completed significant actions with us - such as registering an account or subscribing to Byrd. A simple email trigger has now been setup so we can keep you apprised of significant - service only - notifications.

Bug fixes

Everyday goals data persisting when editing

Trying to edit an everyday goal would often be an irritating process - because once on the edit screen the user couldn’t see the value that they were hoping to change. We’ve changed this so now these values should persist.

Relative pace improvements

Relative pace on actual runs on previous releases was only using the weather to calculate the relative pace. We’ve fixed this so the calculation also takes into account the elevation.

Known issues with the release

Pacing and durations on activities are not quite in the state we’d like them to be yet for all users, we’re working on a more sophisticated way of calculating how long people should go out for each run.

We’ve continued on the groundwork done in v0.3.12 to overhaul durations, but it will take time to get these into Byrd. Thank you for bearing with us.

0.3.12

Apple status:

Replaced by 0.3.13 before release

Play status:

Expired public release

Date:

February 22, 2022

General release notes

In version 0.3.12 we’ve managed to add a few small features whilst continuing our efforts to fix the bugs our users are reporting.

New features

Improved pre-run question

The pre-run question flow can now give more detail to our users about the next run in their plan.

Added an explanation a run has no laps

Some users found it confusing when certain runs had no laps associated to them. This is sometimes valid as laps aren’t a feature of all runs. So we’ve improved the experience by putting a message in place that explains that the run has no laps to show.

Included the new duration picker in the Everyday Goals

Everyday goals in the last release were still using the fiddly duration input. We’ve included the duration picker that we introduced in other places into the form for duration event goals in this release.

Added the ability to disconnect Garmin

The Connected Services settings page should have always given Garmin users the option of disconnecting - so we’ve added it in this release.

Bug fixes

Removed planned runs before the latest actual run

The rules around the plan regeneration and planned runs being removed from the plan are quite complicated, and we’ve had a few users reach out to us that it appears to not behaving as expected. Sometimes, the planned run for the day persisted after the actual run had been processed. We’ve fixed this by removing any run from the plan that was due to happen before the latest actual run.

Removed unnecessary capitalisation

Some words in the app were capitalised mid-sentence. We know this can be jarring so we’ve put in a fix to correct this.

Date inputs default to empty

Date inputs would previously show a default value of today by default, but the date wasn’t actually selected. This led to some confusion, so we’ve changed it to show an empty state by default but have the initial value when the picker is shown to today.

Agreed to terms not being recorded

We want to make sure that everyone who has registered an account with Byrd uses it fairly and properly within the scope of our terms and conditions. At present, we prompt our users that they agree to our terms and conditions at the point of registration (and they can view them before they sign up). An oversight on the part of the Byrd team was that we weren’t recording that users agreed to these terms and conditions. We’ve updated this so that from this point on, we will record that users who register will agree to the terms and conditions.

Known issues with the release

Pacing and durations on activities are not quite in the state we’d like them to be yet for all users, we’re working on a more sophisticated way of calculating how long people should go out for each run.

We’ve continued on the groundwork done in v0.3.11 to overhaul durations, but it will take time to get these into Byrd. Thank you for bearing with us.

0.3.11

Apple status:

Latest release

Play status:

Expired public release

Date:

February 18, 2022

General release notes

We’ve fixed a couple more bugs for version 0.3.11. Read on to see what’s changed.

Bug fixes

Improved pacing consistency on future runs

Future runs weren’t consistently showing the correct pace ranges everywhere. Sessions were using one method, while the cards and the details used another. We’ve fixed this to make it more consistent.

Whilst this is more consistent users might notice a difference in their regular paces. If anyone has any feedback on these paces it would be great to hear from you.

Onboarding navigation on smaller screens

We’re working on a bigger redesign of the onboarding, but in the meantime we’ve fixed a problem users with smaller screens were having where selecting the next item in the list was difficult.

Improved counting of seeds

Some users reported seeing their seeds from their most recent run added and then immediately taken away. We’ve looked into this and found a bug in the way the the seeds were being added up - that bug has been fixed in 0.3.11

Made the time for future runs more vague

The runs that Byrd suggests to users are just that - suggestions. Giving specific times to go out and run felt a bit against the grain of what we’re trying to achieve with the way Byrd encourages people to run. So we’ve made these times simply reflect AM/PM - with the run title hinting at the more precise time to get your shoes on and head out the door (but not explicitly giving you the hour of the day to do so).

Known issues with the release

Pacing and durations on activities are not quite in the state we’d like them to be yet for all users, we’re working on a more sophisticated way of calculating how long people should go out for each run.

We’ve continued on the groundwork done in v0.3.10 to overhaul durations, but it will take time to get these into Byrd. Thank you for bearing with us.

0.3.10

Apple status:

Expired public release

Play status:

Expired public release

Date:

February 16, 2022

General release notes

Version 0.3.10 is an entirely bug fix release. We’re very committed to ironing these out for our existing users so everyone gets as positive an experience with Byrd as possible

Bug fixes

Plan updates on settings changes

We’ve had multiple reports of settings changes making very little impact on the our runners' plans, if any at all. We’ve narrowed this down and fixed the bug so anyone updating their preferences should see a refreshed plan to match.

Run import improvements

There have been a few reports on the previous release where runs were failing import altogether. There were a couple of causes and any one of them might have tripped up the process. The first was that there was an unexpected value in some FIT files - we’ve fixed this and users should see the benefit straight away. The second was that the Treadmill garmin activity type wasn’t included in our list of runs so we’ve updated that. The third was that some runs were making the process time out - so we’ve increased the timeout limit.

Notifications being sent too early

Some users noticed that if they tapped on a notification as soon as it appeared that certain parts of the run wouldn’t be ready - including the title and image. We’ve fixed this so now notifications will be slightly delayed, but the content will be ready when it lands.

Improvements to totals and fitness calculations

We noticed some users were seeing issues around their totals being calculated and what we refer to as “runner state” not being properly updated. We’ve fixed this in this release by adding something technical called “null safety”.

Home page stuck in “regenerating” state

We found a bug where it was possible for users to get stuck in the “Your plan is regenerating” state on the home page. We’ve corrected that in this release.

Improvements to user ID processing

Don’t worry! This isn’t about some awful spyware stuff. We need to track the user Id that Byrd gives you so that we can keep records - like your runs and whether or not you’re a subscriber. We noticed that for some of our initial testing crowd there were some mismatches and this was causing issues for the a lot of the processing. So we’ve added some checks to correct these issues and it shouldn’t affect new subscribers.

Experience detail cards improvements

We noticed that some of the experience detail cards were missing… erm… details. Specifically some of the text in the description on the card was being truncated and the date the card was unlocked wasn’t showing. The first one is fixed in this release - the second should fix itself after Byrd processes your first run following this release.

Known issues with the release

Pacing and durations on activities are not quite in the state we’d like them to be yet for all users, we’re working on a more sophisticated way of calculating how long people should go out for each run.

We’ve laid the groundwork for overhauling the durations, and are going to keep at this so it can be moved from the issues up into the New features list.

0.3.9

Apple status:

Expired public release

Play status:

Expired public release

Date:

February 11, 2022

General release notes

Version 0.3.9 is almost entirely a bug fix release - further adding to the stability of the app. The only feature that’s been added in this release is one designed to help us better debug the experience for our users.

New features

Better app version reporting

One of the first things we like to do when investigating bugs from users is check which version of the app they’re using. We have a process in place that lets us do this, but it wasn’t reliable. On this latest release, the app version checking is much more robust - so if you report an issue we should be able to better track down where the bug is and whether updating the app is a solution.

Bug fixes

Cached subscriber status

Some of the reports we’ve had from subscribers have indicated that after purchasing a Byrd subscription, Byrd can forget that the subscription was purchased. We narrowed this down to there being some unexpected behaviour from the API we use for subscriptions and it seemed to specifically affect iOS users. To add some further stability to the improvements made on this in v0.3.5 Byrd now caches your subscriber status, so for a limited time after the subscription has been purchased Byrd has a fallback if the API fails for any reason.

Record run background location notification changes

Android users get a notification when a run is being recorded. There was a bug that meant this notification would return after initially being dismissed at the end of a run, and couldn’t be removed without forcing the app to stop in settings. While testing we also noted that the distance and duration being shown weren’t updated frequently enough to be accurate so we’ve removed these for now and simplified the notification content. We’re investigating ways to bring this back as we know it’s something Android users will find useful.

iOS location permissions when recording a run

We noticed this week that whenever Byrd requests permission for location before recording a run on iOS, the request fails immediately and unexpectedly if location services are off at the time. We’ve changed this now to prompt users who have not got location services turned on to go to their settings and turn them on so that Byrd can request the permission.

Record run sense checks

Byrd was doing very little validation of recorded runs in the last release. When testing we found that GPS issues could lead to erroneous data creeping in, so we’ve now limited the maximum distance that Byrd will accept in a second to 10m. If this change negatively affects any users please get in touch, as we’d love to know how you’re managing to outpace olympic sprinters.

Known issues with the release

Pacing and durations on activities are not quite in the state we’d like them to be yet for all users, we’re working on a more sophisticated way of calculating how long people should go out for each run.

0.3.8

Apple status:

Replaced by 0.3.9 before release

Play status:

Expired public release

Date:

February 10, 2022

General release notes

Version 0.3.8 contains a few important bug fixes for stability, as well as better improving the communication between the app and the users. Notably the notifications in the app, and the guide speech on the home page.

New features

Improved home page communication

We’ve added more dialogue in the home page to help keep users informed on the current state of their recorded and imported runs, as well as a welcome message for new users. It was previously a bit tough to know what was going on in the time where your run was being imported and processed, up to the point where it was displayed, so now the guide will let you know when your run has been imported, as well as when it is being processed.

Bug fixes

In-app notifications

Users were seeing some quite erratic behaviour with the in-app notifications, as well as sometimes seeing multiple push notifications for the same run. We’ve disabled the in-app notifications for now while we work on making them behave a bit more consistently.

Seeing multiple activities in the plan

We had reports of people seeing both a rest day and a run on the same day, which is pretty confusing - put in some measures to stop this happening.

Events for today not being displayed

Small fix for the events on the goals page - it was only displaying events that were after now, this has now changed to display from the start of today onwards.

Known issues with the release

Pacing and durations on activities are not quite in the state we’d like them to be yet for all users, we’re working on a more sophisticated way of calculating how long people should go out for each run. We’re seeing some issues with the background location notification persisting after a recorded run has finished, fix incoming for this soon.

0.3.7

Apple status:

Latest release

Play status:

Expired public release

Date:

February 8, 2022

General release notes

Version 0.3.7 is mainly a bug fix release - once again focussing on stability both within the app and in our cloud infrastructure.

New features

Time zone aware runs

We’ve added some timezone awareness to your runs, as we’ve noticed that several users have reported issues with both The Wilds and with the run time awareness.

Bug fixes

Fixed a bug on recorded run splits calculations

Runs recorded in Byrd have had some issues with their splits calculations - we’re continuing to improve it and this release includes a small code change which we hope will move things in the right direction for our users.

Fine-tuned the calculation of seeds

Some runners joining Byrd noticed that their first run could result in really high numbers of seeds, which then tail off the more they use the app. This was down to a calculation that uses your average running to normalise how many seeds you should unlock for a particular run. Byrd should dispense seeds more gradually than this, especially for experienced runners. We’ve corrected this by including the current run in the average running calculation.

Tweaked the unlocking of sunrise/sunset

Byrd should give prominence to particular events when they’re being unlocked, but sunrise and sunset were determined only if they met a very specific and scientific criteria. We’ve found these criteria to be too strict, so we’ve loosened the definition in the code to give more leeway to runners looking to unlock these experiences.

Changed which stat to show for laps & splits

Some users noticed longer than expected lap and split times. After checking we noticed that elapsed time - including pause time - rather than moving or “timer” time was being used. We’ve corrected this.

Fixed a bug in the onboarding We had reports that users could get stuck in onboarding if they got into the “Choose Your Space” screen without having completed the previous screen properly. This issue was down to “locked” menu options still being accessible.

Known issues with the release

There are still a few critical frustrations with the app.

  • Paces for early users: These can still be very volatile because of the way we’re asking the onboarding questions. We’re working on improving it from both sides e.g. making it easier to share data with Byrd during onboarding and ensuring that there are bounds around the paces
  • Some users report receiving multiple notifications for a single run

0.3.6

Apple status:

Expired

Play status:

Expired

Date:

February 4, 2022

General release notes

0.3.6 adds a number of relatively small improvements to the app alongside a number of stability fixes within our cloud infrastructure.

New features

Event goals

Somewhere between feature and bug fix we’ve added in the ability to see all your event goals, both future and past from the goals page. We’ll be adding additional complexity to the page as we learn more about how people are using it.

Service message functionality

This feature adds the ability for us to put a message in the cloud and have it accessible from the client. That doesn’t sound particularly interesting but is very useful to let us communicate any problems. You should hopefully never have to see it but useful to have just in case.

Offline notification

Much of Byrd will still work if you’re offline. You can record a run, view you activities and goals. But that’s a bit confusing because there’s quite a few things you’re not able to do. You can’t add a goal, or add an activity and you won’t be able to see the state of The Wilds. We’ve now added a little notification to give you a heads up that you’re offline explaining that the app may not work quite as expected.

Record run notification now shows time and distance

At launch the record run notification just said “Background service is running”, which is a true statement but not a particuarly helpful one. You’ll now be able to see the time and distance you’ve covered since you started recording the run.

Bug fixes

Allows seeds to be discovered more generously

Up to now Byrd has been quite restrained around how many seeds can be discovered on a single run. Talking to people though we could see it meant they weren’t getting a great experience of The Wilds because progress was proving to be slow. We’ve increased the number of seeds that can be discovered. We’re sure this will be tweaked in the future so go grab them whilst you can. If you’re curious about where seeds have come from you can also read a post about it here: Pool, chess, and how Byrd assigns seeds for running

Fixes infinite loop for users with no processed runs

We introduced pagination in 0.2.4, which is awesome but created a problem where someone without runs could crash their phone by trying to scroll down the page without activities on it. We never heard of a report of this happening but think anything that potentially uses all the RAM of your phone should be fixed fast!

Splits showing as expected

The splits saga is finally over - mostly. For processed runs it’ll now show as expected. There is still an issue for runs recorded with Byrd but we’ll be fixing these in the coming days.

Sharing The Wilds on WhatsApp iOS

The way the WhatsApp API works on iOS is different to any other sharing API we’ve come across. Essentially if WhatsApp sees there’s text to share it’ll only share the text even if there’s supposed to be a video shared alongside it. We should have caught this in testing but didn’t. Thanks for the various reports that it wasn’t working! It’s now been fixed.

Apple SSO at registration

Another one we should have caught in testing. Apple SSO was available to login with but the button was missing from the registration page. Now fixed!

Checks for user fitness, volume at settings on activity import

This was particularly important for users who onboarded in the early days of Byrd. A few of them have been sitting - very patiently - for several weeks without recommended runs. Byrd will now check that the various pieces of data it requires are within the database every time a run is processed. If the data points don’t exist Byrd will extrapolate from the single run that you’ve been on to fill the gaps. It’ll give a deeply imperfect plan but is substantially better than a guessed at / generic plan.

Known issues with the release

There are still a few critical frustrations with the app.

  • Timezone awareness: Byrd still thinks everybody lives in the UK, which given I live in Italy is exceptionally stupid
  • Paces for early users: These can still be very volatile because of the way we’re asking the onboarding questions. We’re working on improving it from both sides e.g. making it easier to share data with Byrd during onboarding and ensuring that there are bounds around the paces
  • Splits for runs coming from Garmin are now fixed, but from a recorded run they still run the risk of not working

0.3.5

Apple status:

Latest release

Play status:

Latest release

Date:

January 28, 2022

General release notes

Hot fix for a problem with Apple subscription.

New features

  • Better handles removed / amended totals in preparation for future features.

Bug fixes

  • Forces the purchaser info to be called more frequently by the app to stop a subscriber from being considered a non-subscriber by the app
  • Allows the ‘Frost’ card in Season 0 to more consistently be unlocked (those sub 3°c runs will no longer be in vain!)

Known issues with the release

See release notes from 0.3.4

0.3.4

Apple status:

Replaced by 0.3.5 before release

Play status:

Expired public release

Date:

January 27, 2022

General release notes

This release handles a number of general connectivity issues that users have been seeing.

New features

Delete runs

A frequent request since launch has been the ability to delete runs. Especially for those who’ve been testing the resilience by both recording the run with Byrd and Garmin. You can now delete a run by going to the activity page, clicking on the three vertical dots (‘context menu’) in the top right corner and hitting delete.

Add a run with a FIT file

It’s now possible to add a FIT file directly through Byrd. There have been some connectivity issues with Garmin in the past few days and we think it’s important that people have the chance to get their data across in all the granular detail they might want. You can find it as an option when you add a run.

Bug fixes

Increases resilience with Garmin API

Between Tuesday night, 27 Jan, and Wednesday morning, 28 Jan (7pm UK time to 5am UK time) a number of runs failed to process correctly into Byrd. Likewise on Wednesday evening there was an outage of an hour around 7pm. The error was on our end with a socket (the thing listening for incoming connections) didn’t listen in the expected way. We’ve put in a number of additional error handling (in addition to those in 0.3.2) to ensure this doesn’t happen again. We feel the pain. The loss of connection meant that Edd, Nina and Polly were all impacted by runs not coming through as expected!

Input durations using a time picker

Someone between bug and feature we’ve had a few people incorrectly entering data with the existing text fields. We’ve swapped these for an iOS style time picker that we think will increase accessibility. There’s an edge case - if you want to enter a duration that’s more than 24 hours - that will mean you need to still use the text fields but it’s rare to run for more than a day so we hope that’ll be an infrequent interaction!

Stops in-app notification that ‘Byrd has processed a run’ appearing multiple times

This was getting in the way of a number of people using the app. It’s now been fixed so should only appear the once and will respect when you hit ‘close’.

The Wilds have gone missing

If you’ve been out in the fog, mist, haze or murk over the last few weeks you’ll have been presented with the message that ‘The Wilds have gone missing’. These have all now been correctly mapped to ‘atmosphere’ so should display the expected state for you in The Wilds. Sorry they went walk-abouts.

This release also fixes a few minor things

  • Onboarding now scrolls to the next item to complete. A few people got stuck
  • Changing to a rest day now works 100% of the time. There were circumstances where the request to change to a rest day wasn’t respected.
  • Running more than 10 miles, or 10KM whilst recording a run caused the number to show as 01. Over 20 miles / 20km it showed as 02. Very disconcerting. It was recording correctly but not displaying. Now fixed.
  • Reduces the amount the homepage flicks between loading states. We were bringing up the loading screen after 1 millisecond, which means it could sometimes flicker. It now waits 1 second before moving to the loading screen.
  • Fixes the images overflowing on some run cards
  • Fixes the bug stopping the secondary figure being shown on elevation input fields
  • Added error screens in a more efficient way to avoid anyone ever seeing a black screen

Known issues with the release

Elevation not being displayed

This is still an issue. It’s been relatively low priority since we can see the data is being correctly saved to the database. That said we’ve heard how annoying it is to not be able to see it. We’re going to try and get it fixed in the next release.

Subscription issues

There’s some weirdness happening with subscriptions on iOS. It’s possible to subscribe successfully and then not be recognised as a subscriber on Byrd. This is obviously incredibly frustrating and we’re really sorry for everyone who’s been in this situation. If you do hit the bug please drop me an email at edd@byrd.run and I can make sure it’s worked out. For full transparency it’s a bug that’s relatively frequent but is inconsistent and we’re having a bit of trouble tracking down the root cause. We’ll get a release out as soon as we’ve figured it out though.

Off days / long run preferences not being respected

We know these still aren’t being respected by Byrd for some people. This slipped slightly below the priorities for this release but we’re aiming to sort for the next.

0.3.3

Apple status:

Expired public release

Play status:

Expired public release

Date:

January 24, 2022

General release notes

This release allows you to share The Wilds video and Experience card images. It also makes it substantially easier to add an everyday goal.

New features

Share The Wilds

After each run Byrd creates a new video of The Wilds based on the weather, time of day and the number of seeds you’ve found along the way. You can now share the video (or save it if you’d like). Remember to tag us in it if you share anywhere public 🌄

Add a custom everyday goal

Technically speaking it was already possible to add an everyday goal but it was a bit like the Konami-code. Cool if you know it, totally useless if not. We’ve now made it so you can add an everyday goal straight from the everyday goal card and improved the menu to edit and delete the goal.

There’s been some great feedback on everyday goals so there’s likely to be a number of enhancements and evolutions to this bit of the product through the coming days and weeks.

Bug fixes

Some minor things

  • The everyday goal cards have the design intent colours and validate against the Web Consortium Accessibility Guidelines (WCAG). You might notice a slight shift
  • There was an erroneous ‘today’ on all the event goal cards. This was caused because of the bug fix from Friday for the onboarding formatting. We missed the fact the function was being used in two different places.

Known issues with the release

Event goal list volatility

There’s some loading issues happening on the goals page, which sometimes means you can’t see your goals. Awkwardly this often coincides with adding a new goal 🤔 We know what the problem is so will have a fix in soon.

Accomplished event goals becoming invisible

There’s currently no way to access historic event goals. We thought we could get away with that for the first week of Byrd but clearly not. We should get a fix for this today or tomorrow.

0.3.2

Apple status:

Expired release

Play status:

Expired release

Date:

January 22, 2022

General release notes

This release focussed on making app behave as expected on smaller screens. Byrd was bloody awful to use on iPhone SEs or other small phones before this release. There are still some areas where a small screen won’t quite get the perfect experience but will be navigable and usable.

New features

This release

  • Extended the trial period for 21 days from the initial 14 days. There’s a blog post coming Monday about this.
  • Increased the amount of information being shown to you when sending workouts to Garmin, especially if they failed.
  • Improved the calculations for the duration of recommended runs, especially for when someone first starts using Byrd. This is a hard problem to solve because of the variability and this is a first step in what - we expect - will be a long journey of evolving this algorithm. We’d really welcome feedback on how it’s working for you!

Bug fixes

Makes Byrd usable on small screens

We were super impressed the length that some of you went to get Byrd running on a small screen (the best was the person that said they just used their iPad). Either way, there were a number of bear traps through the app for people will small screens. These are now hopefully all fixed and have incorporated a Nexus S and iPhone SE into our user-acceptance testing process, which should help spot issues in the future.

Recommended runs sometimes not being generated

There was an annoying problem where future runs weren’t being suggested by Byrd because Byrd wasn’t waiting until the default preferences had been set. This has now been fixed so you should always have recommended runs created from the first moment you start using Byrd.

Recent run can be any time in the last ten years

One of our users has literally been stuck trying to enter their recent run since the release. Their recent run was December 15, 2021, which is definitely recent! We’re not sure why it was set to only be the last month. We’ve now extended to be the last 10 years, which is the same time range for the first run. Hopefully your recent run isn’t further in the past than 10 years, otherwise we’ve messed up again!

Other bugs this release fixed

  • Formatting of duration, distance and dates within the onboarding flow were weird for some people. These are now fixed.
  • The clock for event goals was behaving weirdly and appeared to not change from AM to PM on the UI. This is now fixed.

Known issues with the release

Guide being cropped on small screens on the homepage

As mentioned in the release notes whilst we’ve improved how the app behaves on small screens there are still some sharp edges. The guide can sometimes get hidden on the homepage behind their own speech bubble. We’ll have a fix later in the week for this.

On initial use Byrd creates two rest days

There have a few reports of Byrd . We’ve been able to replicate our end but haven’t quite diagnosed the problem. It’s on our critical list and will get a fix ASAP. It appears to only happen when first using the app. Obviously feel free to ignore Byrd, it’s a bug stopping Byrd being able to give the correct recommendation.

Byrd ignoring off-day and long preferences

A few people have mentioned that Byrd isn’t respecting their off day and long run preferences. One person kindly suggested it was because Byrd was trying to be clever and push them out of their comfort zone. Unfortunately it’s a bug that we need to diagnose and fix. It’s on our critical list though. It obviously goes without saying that you should feel free to ignore Byrd if it recommends a run when you don’t want to go on one ☺️

Other things

  • Byrd still thinks all runs are being run in the UK. We hoped to get this fix into this release but ran out of time. It’ll be in early next week.
  • Apple Single sign-on isn’t appearing on iOS devices when logging back in. We’re on it and will be in the next release.

0.3.1

Apple status:

Expired public release

Play status:

Expired public release

Date:

January 20, 2022

General release notes

A dot release to sort a config issue.

New features

As per 3.0.0

Bug fixes

As per 3.0.0. Additionally corrected the numbering in specification docs for Play and App Store.

Known issues with the release

See 3.0.0

0.3.0

Apple status:

Replaced by 3.0.1 before review

Play status:

Replaced by 3.0.1 before review

Date:

January 20, 2022

General release notes

New features

This release adds

A Unique identifier (UID) in your settings

This isn’t going to win a prize for excitement but is very useful. Now at the bottom of your Settings > Your Account you’ll see a little string of numbers and letters. If you’ve not yet registered it makes it a lot easier for us to find out what’s causing any problem in your account when you get in touch if you can use that bit of text.

Additional resilience to the Garmin API

Yesterday we fixed some bugs that only appeared when we scaled. Today we added a whole additional bunch of resilience with better error handling and increasing the amount that we’re checking the connection is behaving as expected.

Bug fixes

Default user preferences are being set during onboarding

We had a number of bugs reported around off days being created where the user believed they had no off days. Some users reported being swapped from metric to imperial units. One user reported no rest days being recommended. The common thread was not having defaults being set for the user preferences when first creating the user. This is now happening and should make that all a bit smoother.

Location permissions on record run

The location permissions have been a painful backwards and forwards between Android and Apple changing their guidelines and us trying to implement them correctly. That created a very awkward interaction. The permission flow should now be much smoother. One of the people testing it earlier said it was “seamless”, which is what we were aiming for. If you’re not finding it seamless please let us know so we can fix.

Avoiding a user exiting record run before saving

It was previously possible to hit the back button from the screen to save your recorded run and simply exit the flow. That caused your recorded run to be deleted. Going for a run and then seeing the evidence disappear in front of your eyes because of bad UX is pretty excruciating. We’ve put in a quick fix that pops an alert to warn you that you’re able to delete your run. Longer term we’re planning to add a feature to back up your run whilst running to avoid losing it because of battery / connectivity issues.

Save button no longer hidden on small screens

The save button when manually adding a finish time was getting hidden below the keyboard. It now uses both relative spacing and is housed within a scrollable element so should be accessible even on the teeniest, tiniest screens

Manual data form improvements

Another bug fix that won’t win awards for excitement but should make the experience a little easier. For some users the content of their forms was disappearing if they went back to edit the data, that obviously made editing very difficult! We’re now saving draft data in the database (rather than having it all on the client until it’s saved) to make handling the form state better for both the user and Byrd.

Event goals now use elevation when recommending a finish time

This was a bit of functionality that didn’t get properly ported from the old client. It meant that someone could say they were running 10km up Mount Everest (Sagarmatha) and Byrd would happily return a recommended time of 40 - 55 minutes, which made it look silly. The recommendations should hopefully feel more curated now. If they don’t please tell us about it in the form in the app.

Byrd better uses the recent run within onboarding for the plan

We hadn’t properly wired up the recent run to help Byrd build the initial plan. With covid, Christmas and the general chaos around people haven’t been running so much recently, which meant that Byrd was recommending runs that were shorter than expected. We’re now using the recent run data to avoid that.

Banner saying a run has been imported is now closable

If you had Byrd open and imported a run - which frequently people do if they’ve recorded a run - there was an annoying pop-up that didn’t have a close button that appeared to tell you a run had been imported. That banner can now be closed and additionally will link you to the relevant run too.

Known issues with the release

  • Some users are reporting their first two recommended runs are rest days. We don’t know why. We’re investigating
  • Seeds on activity cards are different to seeds on the activity detail page. Unsure why
  • The Frost card isn’t getting unlocked when running in under 3°c temperatures, which seems pretty unfair given how hard it is to go outside when it’s that cold
  • Some users are reporting that the incorrect state of the Wilds is showing on their activity cards. We think it’s an issue with the weather API
  • The Wilds is timezone naive. It doesn’t matter where you are, it’ll think you were running in the UK. Sorry, there’s really no excuse for having software behaving like the UK is still the centre of the world
  • Laps aren’t displaying correctly for any user, though they’re particularly weird for users who have recorded a run
  • Record a run users are being told their run is uncategorised even though it is
  • Onboarding is still painful on small screens (see (0.2.6)[#0.2.6])
  • It’s still important on Android to use the browser to connect to Garmin (see (0.2.5)[#0.2.5])

0.2.6

Apple status:

Expired public release

Play status:

Expired public release

Date:

January 20, 2022

General release notes

This release reduced the dependency on Garmin within the initial phase of starting to use Byrd. This should hopefully lead to a better user experience.

New features

This release

  • Moves the Garmin integration process from onboarding to the user settings. We had lots of awesome feedback (thank you!) about it being weird to jump through a bunch of hurdles before it was possible to really evaluate whether Byrd had any value
  • Adds the manual data questions for all users

Bug fixes

This release fixed

  • Restructured our Garmin API call. We were doing some bad things like setting the response code before the response had been fully captured and would exit from the operation with a single error rather than trying to continue. This should resolve the bugs that some people have reported with their Garmin imports
  • Fixed the black screen error for some users who had backfilled their data. We’re not correctly expecting a number on the client not string
  • Recorded run miles being shown incorrectly whilst running
  • Ensured we ask about the ‘Average running week’ not the ‘Last running week’
  • Decoupled the manual data questions from onboarding so they’re accessible from settings for existing users

Known issues with the release

Onboarding is painful on small screens

Onboarding is close to impossible on iPhone 6s and very uncomfortable on the iPhone SE. The area at the bottom of the screen is simply too small to be useable. This is entirely our fault. We underestimated the prevelance of small phones in the world of running. We’re working on a fix that we hope to get in this week.

Save button hidden by keyboard When adding an event goal if you decide to add a finish time manually the ‘save’ button may be hidden on smaller screens. There’s a widget that’s taking up a relative amount of space on the page that’s pushing it down. This is a problem on iPhones because there’s no easy way to remove the keyboard to press the button.

The manual data questions are quite specific

Byrd doesn’t need a huge amount of specificity with the initial data questions e.g. there’s no functional difference for the product between 80km and 80.2km but the way that the questions are formulated makes it appear that we need that level of specificity. We’re aware that’s a UX failing and can be off-putting for users. We have a fix from a design perspective to use sliders and options (rather than text boxes) but isn’t a priority to implement from a development point of view. We will get to this as quickly as we can but is prioritised below some more critical issues.

0.2.5

Apple status:

Expired public release

Play status:

Expired public release

Date:

January 19, 2022

General release notes

This was a very quick point release created after 0.2.4 to correctly enable anonymous users - e.g. those using Byrd who hadn’t formally registered - to be able to delete their account. Previous to this release these users would have had to email us to delete their data.

New features

None

Removed features

This release removes

The ability to import historic data from Garmin.

We had no errors whilst testing this over the past 6 months but since launch have seen hundreds. We need to understand better what within the infrastructure (whether on our side or Garmin’s) isn’t scaling correctly. Byrd doesn’t need all of the historic data in order to give a usable and useful series of recommended runs, though reduces our ability to give hugely curated event goal recommendations. We can’t rely on it as a critical part of the onboarding flow because it’s too interruptive so have removed for now. We will try and re-instate it as soon as possible.

Bug fixes

This release fixed

  • An error stopping anonymous users being able to delete their accounts
  • An error in our session generator utilities that could potentially have created an infinite plan
  • A typo in the rest day dialogue flow

Known issues with the release

Black screen on homescreen for some users who’ve backfilled data

For a handful (we hope!) of users upgrading to 0.2.5 will create a black screen on their homepage. If you’re unlucky enough to be seeing this first off sorry, second please email edd@byrd.run and I can get it fixed for you, this unfortunately isn’t something that you can solve on your own device because the malformed data is within the database. There are two bugs that are compounding here. The first is that when the homescreen is in error we haven’t given the app a particularly good instruction of what to do (so it does nothing) whilst it goes into error because a string has been written to the database where a number was expected. Both of these things will be fixed in releases later this week (likely the release expected to be public January 21, 2022)

Import failing if runs recorded simultaneously on Byrd and Garmin

It has been awesome hearing about people testing out how well Byrd performs against Garmin when recording a run. We like to be tested :) That said we - annoyingly - didn’t design Byrd’s infrastructure in such a way that it could handle two activities being imported at the same time. This should normally work but if the two activities land in the database at roughly the same time then one of them will fail to import. If you want to test both leave it a few minutes between saving each one.

Byrd won’t identify duplicate activities

Related to the above issue we have no functionality to attempt to detect duplicate activities. That means Byrd could look very, very silly if you import two runs that are near identical via recording a run on Byrd and Garmin. If you went for a 10KM run Byrd will behave as though you’ve run 20KM that day (2 x 10KM) and will amend your recommended runs, event goals, everyday goals and Wilds state accordingly.

Initial Android / Garmin integration

As flagged on 0.2.1 the Garmin flow on Android is harder than it should be. You should use your phone’s browser to integrate with Garmin but that isn’t clear from the Garmin interface. We’re working on a process - similar to the one that Strava uses - that would enforce authentication via the browser but that won’t be ready until 0.2.7 or 0.2.8.

If you’re struggling with the Android / Garmin connection we put together a little Google Doc to help with troubleshooting.

0.2.4

Apple status:

Skipped (removed to push 0.2.5)

Play status:

Skipped (removed to push 0.2.5)

Date:

January 18, 2022

General release notes

New features

This release added

  • The ability for non-registered users to delete their accounts (rather than have to email us)
  • The ability to have recommended runs whilst awaiting the full data history from Garmin
  • A dialogue flow to better communicate the state between Byrd and Garmin

Bug fixes

This release fixed

  • The three record run crashes caused by the timer not being correctly disposed from state
  • Changed the way we instantiate registeredDateSeconds when communicating with Garmin to make it more resilient
  • Allows a registered user - who has lost their data - to restart the onboarding process
  • Removed ability to register via the login page
  • Removed ability for an already registered user to register a new account
  • Fixed a number of typos

Known issues with the release

Anonymous user deletion The initial implementation of anonymous user deletion didn’t work as expected. We released 0.2.5 about an hour later to enable that functionality to behave an expected.

0.2.3

Apple status:

Skipped (removed to push 0.2.4)

Play status:

Expired public release

Date:

January 18, 2022

General release notes

Our third release within 24 hours of launch was put out quickly to help the users who were struggling with the record run not behaving as expected.

New features

This release added

  • Within onboarding the user was asked to give their ‘Last week running’, in conversation with a number of users we changed this to ‘average week running’ to better reflect the information Byrd needs.

Bug fixes

This release fixed

  • Record run sometimes creating lists that went out of bounds from one another
  • Changed record run so that it correctly used cumulative distance from than point-to-point distance
  • Removed an immovable Material banner that appeared if a run was processed whilst a user was in an app. It was super annoying!
  • Displays empty activity pages rather than a loading spinner if a user doesn’t have any future / past activities

Known issues with the release

Many of the known issues from 0.2.1 and 0.2.2 remained in the app with the 0.2.3 release.

0.2.2

Apple status:

Skipped (removed to push 0.2.3)

Play status:

Expired public release

Date:

January 17, 2022

General release notes

A second day zero release to get some additionally functionality out to our users as quickly as possible.

New features

This release added

  • Interstitial page added for Android uses importing from Garmin to better explain to use the web browser

Bug fixes

This release fixed

  • An out of bounds error that stopped the guide talking
  • Garmin backfill stability issues
  • Proposed durations for recommended runs being too dramatically below the runner’s average running duration

Known issues with the release

Black screen on homepage The Garmin backfill stability fixes introduced two new fields to the backfill model. In certain circumstances this can create a black screen on the user’s homepage. There currently isn’t a user fix to this so get in touch if you’re seeing this problem so that we can support.

Registration issues An issue that was present from 0.2.0 but only became visible on 0.2.2 was an issue where users could accidentally disconnect their data from their account. This was caused by a set of compounding bugs that made it appear a user wasn’t fully registered when they in fact were. That led users to incorrectly undertake a series of additional things that caused bad times for all involved. There’s no straightforward fix if your account gets into this state so get in touch if you’re having authentication problems and we can fix on this side.

0.2.1

Apple status:

Expired public release

Play status:

Expired public release

Date:

January 17, 2022

General release notes

This was the first bug release after launch.

New features

This released added

  • Push notifications for when new activities are imported to Byrd

Bug fixes

This release fixed

  • Permission bug on record run
  • The Wilds not appearing on iOS
  • An anonymous user getting stuck on the subscription page
  • Long runs not appearing as a recommended run for users

Known issues with the release

Difficulty connecting to Garmin through Android By far our biggest day zero problem was getting Garmin connected on Android devices. There were a few issues with Garmin through the day but the big one was on Androids when trying to integrate Garmin via their Connect app. The Connect app often wouldn’t return the data it said it would do. The solution is to use the web browser.

A few people reported not being given the option of using the browser when initially connecting. If your Android isn’t letting you use the web browser then it likely means the Garmin Connect app has been “Set to Default for Certain Actions”. You can remove these defaults by going Settings > Applications > Garmin Connect > Defaults > Set as Default and finally hitting ‘Clear defaults’. You should then be given the choice of using your web browser again.

We’re working on what we hope might make the initial integration a little easier but we’re constrained by how much we can do since the problem’s mostly on the authentication side with Garmin.

If you are struggling with Garmin you might want to consider - for the purpose of onboarding - pretending that you don’t have a device to connect and then connecting it later within your settings.

Record run bug There was a sneaky little bug in recording a run. Apologies for the four people this hit because it must have been infuriating to go for a run and then have Byrd eat the evidence. There was an out of bounds error between the distance list and duration list. Awkwardly this only happened when there were odd numbers in the lists, which was why it was happening infrequently. This should now be fixed as it was a problem with our cloud app rather than anything on the client.

Record run bug part 2 A much smaller bug happens if your preferences are set to imperial measurements. The mile figure works up to mile one and then starts looking very odd. You can blame the fact that the person who implemented it (Edd!) has never run with miles in their life and finds them very confusing.

Waiting on Garmin data Not strictly a bug but still super annoying… Garmin doesn’t guarantee how long it will take for data to be supplied from their servers once we’ve made a request to them. When testing on a small scale though we’ve always found it to be reasonably quick. With 0.2.0 and this 0.2.1 release that hasn’t been the case. In future release we’ll be removing the need to import from Garmin in order to get recommended runs.

0.2.0

Apple status:

Expired public release

Play status:

Expired public release

Date:

January 14, 2022

General release notes

Byrd’s first public release on iOS and Android.

New features

This release added

  • Revenuecat API connected
  • Discount and introductory offer codes added

Bug fixes

This release fixed

  • Settings time of day saved to db correctly
  • Seed volatility reduced
  • Colour changes to ensure on brand throughout product
  • Record run location permission amends to respect changed Google Play and App Store guidance
  • Speech bubbles no longer disintegrate

Known issues with the release

Wilds error on iOS The Wilds did a disappearing act on Apple devices and got replaced with a geeky bit of code. We introduced a last minute code change for some Cloud Functions that caused a Dart error to be shown to the user and a white screen where The Wilds should have been growing. Not a great start for the public release.

0.1.5

Apple status:

Expired internal release

Play status:

Expired internal release

Date:

January 8, 2022

General release notes

Our second release candidate ahead of the first public release. Feature and function complete with the intention to be as close to the final app as possible to make bug hunting and final, pre-launch, fixes easier.

New features

  • Production ready video and media for The Wilds season 0
  • Dialogue flows for rest days and missed runs
  • Initial content for homepage carousels
  • Onboarding and registration feature complete

Bug fixes

  • Activities and The Wilds now use the same Time of Day list
  • Uses correct user preferences for distances and heights throughout the app
  • Stops record run crashing the app

Known issues with the release

Still a number of

0.1.0

Apple status:

Expired internal release

Play status:

Expired internal release

Date:

December 23, 2021

General release notes

This was our release candidate ahead of Byrd’s first public release. We tested over the Christmas break between festivities and covid chaos.

New features

  • Launch homepage with initial dialogue flow
  • Record run functionality behaving as intended
  • Everyday goals functionally complete

Bug fixes

  • Removed old client image generation
  • Ensured Mapbox polylines were being plotted correctly
  • Fixed a number of formatting issues with durations, distances and heights

Known issues with the release

  • Onboarding and registration incomplete, will only work for users of previous Byrd client
  • Seeds being awarded in too volatile a manner
  • All runs being imported as uncategorised

0.0.5

Apple status:

Expired internal release

Play status:

Expired internal release

Date:

November 19, 2021

General release notes

First functional version of new client. The aim of this release was to be feature complete within the main channel, even if the functionality wasn’t all accessible navigating the app.

New features

  • JSON inflated forms and onboarding
  • Branded loading and error screens
  • Event goal flows and detail page implemented
  • Activity flows created and connected to database
  • Initial version of The Wilds implemented
  • Additional design atoms created

Bug fixes

None

Known issues with the release

0.0.5 was only partially useable as a product. Most of the data was either hardcoded or pulling from incorrect database fields.

0.0.1

Apple status:

Expired internal release

Play status:

Expired internal release

Date:

October 23, 2021

General release notes

First client release of production Byrd app using an atomic design approach.

New features

  • Created a new Byrd UI package with just over 500 stateless widgets implemented
  • Product scaffold implemented
  • Porting of database services from previous client
  • Connection to shared services, data models and generators

Bug fixes

None

Known issues with the release

Unusable as an app. Individual design elements called from main.dart.