CityWalker in six months
CityWalker went live on 30 April. Six months later it is at 3.11 on Android and, since 25 September, on the App Store. Two months ago I wrote up the first four months. This is the follow-up. The data runs from 13 May, when I started recording analytics events with Aptabase, to 31 October.
The iPhone app is out
Four months in, the iPhone app was an open beta on TestFlight. It went live on the App Store on 25 September. In October, its first full month, more people set up CityWalker on an iPhone (759) than on Android (735), and iPhone users completed 2,258 walks, 44% of the month's total.
Most of the growth below follows from that one change.
Walks
Total walks went from 1,668 to 8,577. October had 5,087 completed walks, more than May to September together (3,490). Walks have not dropped yet: the last week of October was the busiest so far, with 1,365. But new setups already have (see Acquisition), and with winter starting in the northern hemisphere, I expect walks to slow down too.
Completed walks since 13 May, by milestone:
| Milestone | Date | Days since previous |
|---|---|---|
| Walk 1000 | 10 Aug | 89 |
| Walk 2000 | 7 Sep | 28 |
| Walk 3000 | 24 Sep | 17 |
| Walk 4000 | 5 Oct | 11 |
| Walk 5000 | 12 Oct | 7 |
| Walk 6000 | 18 Oct | 6 |
| Walk 7000 | 23 Oct | 5 |
| Walk 8000 | 28 Oct | 5 |
The first 1,000 walks took almost three months. The last 1,000 took five days. Together the walks cover about 29,000 km. The typical walk is 2.3 km and just under 40 minutes.
Imported walks are not in these numbers. People also brought in 2,845 GPX tracks from other apps, almost all of them in October, mostly from a handful of people importing years of history at once.
Walk 1 to walk 2
Four months in, about 55% of people came back for a second walk. Over the last 30 days it is 65%, and nearly the same on both platforms (63% on Android, 67% on iPhone).
| Walk # | Completed (30 days) | % of Walk 1 |
|---|---|---|
| 1 | 666 | 100% |
| 2 | 436 | 65% |
| 3 | 354 | 53% |
| 4 | 288 | 43% |
| 5 | 246 | 37% |
Walks per user
Last time this number had settled at about 2.0. It started rising again in mid September and is now 2.7. New people keep arriving and pulling it down, so a rising number means the people already here are walking more. The most active person has completed 370 walks.
Acquisition
In August, daily installs peaked near 25. Over the last 30 days an average of 49 people a day finished setting up the app.
That number is already going down. Weekly setups peaked at 343 the week of 28 September and were 305 by the last week of October. In the first days of November it is about 39 a day. One likely reason is that winter is starting in the northern hemisphere, where most people who use CityWalker live: shorter, colder days are not when people go looking for a walking app.
| Month | New users |
|---|---|
| May (from 13th) | 32 |
| June | 149 |
| July | 226 |
| August | 425 |
| September | 838 |
| October | 1,494 |
Four months in, every new user came through a link someone shared. That has changed. People now find CityWalker by searching the stores for a walk-every-street app. Germany brought about 300 new users and the United States about 370, with no spike: a steady 5 to 11 a day, the pattern of search, not of a single post. Languages are a big part of that, below.
The biggest spike came from the Netherlands, again thanks to r/wandelen, the Dutch walking subreddit. On 3 October, 87 people in the Netherlands set up the app, out of 126 in total, the biggest day CityWalker has had. Dutch walks went from 151 in September to 701 in October.
Not every spike turns into walking. In early September CityWalker spread in Indonesia, probably through a reel: about 190 people there set up the app in ten days, 64 of them on 3 September. They completed six walks. Most searched for their town and found nothing, or started a walk and stopped. It also pulled walks per user down for a few weeks, which is part of why that number only started rising in mid September.
Eight languages
CityWalker now supports eight languages: English, French, Spanish, German, Dutch, Polish, Portuguese (Brazilian) and Romanian, on both Android and iPhone.
Translating was the easy part. Keeping it right took longer:
- One word for one thing. A glossary fixes how each app term is translated in every language, so "region" and "area", or "walk" and "hike", do not blur together. A script checks every new string against it before it ships.
- Text that fits. German, French and Dutch run longer than English. The download bar and two notification titles were cut off until 3.9.0 shortened them.
- Every new feature ships translated. New strings are translated into all seven languages before a feature is merged, not after.
- Except the share images. The images you post from a walk stay in English for now, whatever the app's language.
Does it matter? On Android, where the phone's language is reliable in the data, the share of completed walks from phones set to one of the seven new languages went from 29% in August to 38% in October. In October that was 280 walks in German, 221 in Dutch, 209 in Spanish, 191 in French, 110 in Polish and 62 in Portuguese. People whose phone is in a language the app does not ship yet came back for a second walk far less often, though that group is still small. Czech, with 46 Android walks in October, is the obvious next language.
City downloads
This is still the metric I watch most closely, and the goal from four months ago is met. At launch about 50% of city downloads failed, at two months 35%, at four months 26%. Over the last 30 days it is 8%: 2,486 downloads finished and 211 failed, not counting ones people cancelled.
What changed:
- Automatic retry. A download that fails because the server is busy now waits and tries again on its own. In the last 30 days 83 downloads recovered this way that would have been an error message before.
- A bigger cache. About 78% of requests to my caching proxy are now answered from the cache, up from 60%. A cache hit is fast and never fails with a busy server.
- More cities split into regions. 860 downloads in the last 30 days were a ready-made region rather than a guess at a radius.
- Failed refreshes keep your streets. Refreshing a district that fails now leaves the old streets and your progress in place, instead of removing them.
Streets are local
A lot of this stretch went into one lesson: OpenStreetMap mappers tag the same thing differently from country to country, and one rule for what counts as a walkable street does not fit everywhere. Nearly every change below started with a message from someone walking there.
- The Netherlands. Cycle paths that run on their own, through the Amsterdamse Bos or across a polder, now count. Ones right beside a street still do not, so they do not show up as a second line next to it.
- Norway. Bergen's smau, the named alleys in the old town, are tagged like driveways. They now count. Driveways and car parks still do not.
- Tracks. Gravel lanes through nature reserves and tracks on marked walking routes now count when the map marks them open to walkers. Farm tracks stay out.
- Russia and Belarus. Many streets there are tagged closed to walkers, with the sidewalks mapped as separate lines. The app dropped both, so whole streets vanished in Saint Petersburg and route planning broke. The fix is in the latest versions of both apps and is being switched on for those two countries.
- Footpaths set back from a road. Walking a path behind a verge, hedge or service road now counts the road beside it.
There is also a way to report a street that is not walkable, a private road or one for cars only, by long-pressing it on any map. Every report is checked by hand, and a confirmed one is left out for everyone.
Stability
In October, 99.4% of Android users and 98.2% of iPhone users had no crash at all. Crashlytics counted 10 crashes on Android, for 7 people, and 33 on iPhone, for 11 people. 25 of the iPhone crashes came in a few days in early October, the first busy week after the App Store launch. Shipping about 20 Android releases in two months brought a few crashes along the way. 3.6.2 fixed a possible out-of-memory crash when opening the app, and 3.10.1 fixed a crash when double-tapping a walk.
Region seeds
The public catalog of city regions went from version 133 to 212. It now covers 187 cities split into 2,684 regions, up from about 130 cities. London went from 6 central regions to all of its boroughs after a walker in Islington asked.
That nearly broke older versions of the app. The catalog is one file, and Android versions up to 3.10.0 would not accept one over 5 MB. London pushed it past that. Instead of telling everyone to update, I simplified the region outlines to within 2 metres, well under GPS error, while keeping shared borders identical. The file went from 5.2 MB to 2.9 MB. With every city added since, it is 3.2 MB.
Walkers around the world
Four months in, the app had been opened in around 85 countries, with a completed walk in 56. It is now 116 countries, with a completed walk in 88.
The most walks have come from Germany (1,094), the Netherlands (985), the United States (732), the United Kingdom (533), France (518) and Norway (447). Australia, Poland and Japan follow.
What I am shipping next
- Pausing a walk without ending it.
- City Replay: watch a city's walks fill in its map, and share it. Being built for both apps.
- A coverage map of all your cities at once, on both apps.
- Street rules on the server, and with them bridleways and Saint Petersburg's driveways.
- Czech, if the numbers keep pointing that way.
- Online backup is planned. Exporting a backup file in Settings is free and stays free.
