1
00:00:00,020 --> 00:00:04,100
Google and Apple had many technological solutions which have a lot of overhead.

2
00:00:04,400 --> 00:00:04,860
We don't care.

3
00:00:04,960 --> 00:00:07,220
We focus on pure map experience.

4
00:00:08,860 --> 00:00:10,240
Welcome to Techlore Talks.

5
00:00:10,240 --> 00:00:14,180
And today I am super excited to have on Alexander from Organic Maps.

6
00:00:14,360 --> 00:00:18,200
He's going to talk about his journey of creating Organic Maps, which is an open source maps

7
00:00:18,480 --> 00:00:22,520
alternative to something like Apple or Google Maps, how it is open source, how they maintain

8
00:00:22,640 --> 00:00:26,760
it, all of the offline functionality and why he thinks, especially the offline experience,

9
00:00:26,820 --> 00:00:29,360
is actually a lot better than Apple and Google Maps.

10
00:00:29,520 --> 00:00:33,560
We also talk about what the problems are with these big tech alternatives, the challenges

11
00:00:33,650 --> 00:00:38,560
of maintaining data quality, how people can support OpenStreetMaps, which is actually even

12
00:00:38,820 --> 00:00:40,400
utilized for things like Apple Maps.

13
00:00:40,510 --> 00:00:44,420
And we'll also talk about the future of organic maps and just maps as a whole.

14
00:00:44,520 --> 00:00:48,380
I learned a lot of things about maps that I didn't think I would until today, as well

15
00:00:48,500 --> 00:00:51,060
as more of the digital rights angle to a lot of it.

16
00:00:51,200 --> 00:00:53,620
So I hope you enjoy this interview as much as I did.

17
00:00:53,920 --> 00:00:54,420
Let's get to it.

18
00:00:54,740 --> 00:00:58,060
I want to welcome Alexander from Organic Maps on Techlore Talks.

19
00:00:58,200 --> 00:01:00,700
if you want to go ahead and just say a few words about yourself.

20
00:01:01,160 --> 00:01:03,180
Yeah, my name is Alexander Borsuk.

21
00:01:03,880 --> 00:01:09,000
I'm one of the guys who created in 2010 Maps With Me.

22
00:01:09,720 --> 00:01:11,120
Then we renamed it to Maps Me.

23
00:01:11,840 --> 00:01:17,260
When the project was sold, acquired by one company, when we left it.

24
00:01:17,900 --> 00:01:22,980
But before we left it, we pitched the CEO to open the source code of Maps Me.

25
00:01:23,840 --> 00:01:27,460
and development continued when we left as an open source

26
00:01:27,630 --> 00:01:28,940
under Apache 2.0 license.

27
00:01:29,940 --> 00:01:32,960
And in few years, that company sold the project

28
00:01:33,220 --> 00:01:36,060
to yet another company, which screwed up Maps.me.

29
00:01:36,880 --> 00:01:38,900
And that's time when Organic Maps was born.

30
00:01:38,950 --> 00:01:43,000
So we didn't wait for someone to fix it.

31
00:01:43,160 --> 00:01:46,340
We took the latest available open source version of Maps.me,

32
00:01:46,640 --> 00:01:48,600
forked it, called it Organic Maps

33
00:01:48,710 --> 00:01:50,680
because we removed everything, cleaned everything up,

34
00:01:50,780 --> 00:01:53,680
means removed all trackers, unnecessary stuff,

35
00:01:54,680 --> 00:01:58,280
what people don't need, advertisement, some other things,

36
00:01:58,820 --> 00:02:00,340
and left pure map experience.

37
00:02:01,040 --> 00:02:03,220
And that's why organic and focused on this development

38
00:02:03,300 --> 00:02:06,800
in our free time as enjoyable open source project.

39
00:02:08,140 --> 00:02:10,580
Okay, so there was the original project.

40
00:02:10,860 --> 00:02:12,620
It got sold and became another project.

41
00:02:13,260 --> 00:02:15,120
And then it got sold again.

42
00:02:16,180 --> 00:02:17,780
But then, so you took the middle one,

43
00:02:18,180 --> 00:02:19,580
forked the middle one, made it open source,

44
00:02:19,980 --> 00:02:22,940
and made it usable and clean.

45
00:02:23,740 --> 00:02:24,740
Okay, very cool.

46
00:02:24,940 --> 00:02:27,180
And then I read that your bio, you're the co-founder.

47
00:02:27,760 --> 00:02:29,580
So do you want to talk about a bit of the structure

48
00:02:30,120 --> 00:02:32,160
and where your role is and everybody else

49
00:02:32,820 --> 00:02:33,900
who's kind of helped make this happen

50
00:02:33,980 --> 00:02:35,560
and what your team looks like today a little bit

51
00:02:35,680 --> 00:02:36,540
before we dive into this?

52
00:02:37,740 --> 00:02:41,460
Yeah, so the name Organic Maps was born.

53
00:02:41,680 --> 00:02:46,200
And today when we saw that failed release of the Maps.me

54
00:02:46,800 --> 00:02:47,880
from the new owner,

55
00:02:48,840 --> 00:02:57,740
And we created it together with Victor Gavaka, my friend and also founder of Maps With Me.

56
00:02:58,330 --> 00:03:02,340
So we together created this project with some other people also.

57
00:03:03,160 --> 00:03:08,380
And we decided to revive it and work on it.

58
00:03:09,550 --> 00:03:14,100
And after that, we started to build community around it.

59
00:03:14,320 --> 00:03:22,800
because developing open source project alone, at least in times when LLMs will not write the code for you,

60
00:03:23,640 --> 00:03:26,700
was not an easy task, especially in our free time.

61
00:03:27,100 --> 00:03:31,840
We had a business model in Maps.me before Organic Maps.

62
00:03:32,180 --> 00:03:35,580
The free application and paid application, which costed $5,

63
00:03:36,320 --> 00:03:42,720
and we got enough money to go to a break-even and slowly grew up our team from four people.

64
00:03:43,040 --> 00:03:48,800
initially we started to up to 17 before we made the deal and the project was sold was acquired

65
00:03:49,760 --> 00:03:57,000
and in organic maps we stick to similar strategy put a lot of our own efforts time and money into

66
00:03:57,000 --> 00:04:03,460
the initial phase of organic maps and then continued development and open source and started to

67
00:04:04,000 --> 00:04:10,639
help contributors people who were interested in it to to contribute and some of those contributors

68
00:04:10,660 --> 00:04:19,380
became active contributors and active team members. We call them team members. They help us with

69
00:04:19,609 --> 00:04:27,540
several tasks with development, for example, for iOS, for Android, with user support, with

70
00:04:28,780 --> 00:04:34,740
promoting applications and doing all App Store optimization stuff and letting other people know

71
00:04:34,940 --> 00:04:40,960
about organic maps and any other people who are interested of course are welcome because

72
00:04:42,020 --> 00:04:47,500
it's not easy to do it in our free time maybe someday when we get enough donations we can think

73
00:04:47,700 --> 00:04:54,760
about something more involved but so far donations are enough to cover server expenses to cover our

74
00:04:55,160 --> 00:05:02,559
basic development thing but it's not enough of course so you get full speed and work on it

75
00:05:02,580 --> 00:05:08,480
especially for me personally i live right now in switzerland so it's quite expensive country so

76
00:05:08,840 --> 00:05:13,880
we'll see how it goes yeah now we can definitely talk a little bit more about i guess donations and

77
00:05:14,180 --> 00:05:18,180
revenue models you guys have explored i think later i want to touch on that it's always an

78
00:05:18,300 --> 00:05:22,320
interesting question because every open source project project approaches it quite differently

79
00:05:22,820 --> 00:05:27,439
before we get there though i kind of want to start on you know what what i think what most people

80
00:05:27,460 --> 00:05:32,880
think is probably one of the most sensitive applications they use, or maybe they don't

81
00:05:32,940 --> 00:05:33,560
look at it this way.

82
00:05:33,560 --> 00:05:41,580
But I think Maps is quite sensitive just inherently because it's a very well-defined place that

83
00:05:41,780 --> 00:05:42,680
shows everywhere you go.

84
00:05:42,990 --> 00:05:47,700
And people who use Google Timeline and all of these things can visually see everywhere

85
00:05:47,750 --> 00:05:50,500
they go and that their phone knows everywhere they go.

86
00:05:51,100 --> 00:06:09,200
So can we maybe discuss first what kind of data and privacy implications come with using a standard Maps program, whether it's Apple, Google, anything that's mainstream, just to kind of establish the norms so we can kind of compare and contrast your approach to it afterwards?

87
00:06:09,780 --> 00:06:18,420
Yeah, that makes perfect sense to describe first, because now we see a growing interest to privacy, privacy focus from people, from users.

88
00:06:19,260 --> 00:06:23,560
And not everyone understands what about privacy in maps.

89
00:06:23,940 --> 00:06:30,520
And if you remember how Google Maps appeared and then Apple Maps, they were online first maps.

90
00:06:30,620 --> 00:06:35,720
There were reasons, technical reasons for that, because it was hard and almost impossible to make

91
00:06:36,460 --> 00:06:41,120
app work fluently fast enough on mobile device, especially when we started Maps With Me.

92
00:06:41,360 --> 00:06:49,560
It was 2010, times of iPhone 3G, I think only appeared those years. And we did a lot of,

93
00:06:50,240 --> 00:06:56,259
put a lot of knowledge and did a lot of tricks to invent our own super highly compressed map data

94
00:06:56,300 --> 00:07:05,240
format, super fast OpenGL based renderer for this data format, super fast offline search index which

95
00:07:05,360 --> 00:07:11,940
works offline contrary to bigger companies which started initially online and used powerful servers

96
00:07:12,030 --> 00:07:20,420
for that. So and of course when we speak about online maps, the initial way of delivering maps

97
00:07:20,440 --> 00:07:28,560
data was images not vector data like later technology allowed to do. So when you speak

98
00:07:28,780 --> 00:07:35,200
about online maps it means every time you take a look on some place on the map you need to make a

99
00:07:35,280 --> 00:07:43,520
request to the server and even if data location data which your device knows even if it's not

100
00:07:43,860 --> 00:07:49,140
sent not uploaded for whatever reason but it is in most of the cases then at least

101
00:07:50,160 --> 00:07:54,880
on the server side you always know which areas people are requesting, what are they searching for,

102
00:07:55,560 --> 00:08:02,160
what you know, everything what person does in the app. And of course most of the apps also collect

103
00:08:02,410 --> 00:08:07,500
other types of analytics and statistics with the goal, main goal to improve the product,

104
00:08:08,010 --> 00:08:14,659
but there are some other shady goals in some cases. Use this data for advertisement, resell this data

105
00:08:15,260 --> 00:08:23,040
and many many other use cases. So the unique thing about organic maps is that we collect zero data

106
00:08:23,640 --> 00:08:29,560
from our users. The app requires only one thing: you need to download maps from our CDN server,

107
00:08:29,880 --> 00:08:36,960
where we turned off logs. We don't collect any logs and we don't want it. We want to keep it

108
00:08:37,300 --> 00:08:42,979
privacy focused. And on the device there are no any other network requests except when you want to

109
00:08:43,000 --> 00:08:49,000
update the maps when you want to get fresh version of the map. So we don't know anything about our

110
00:08:49,200 --> 00:08:54,140
users yet still we provide very good offline and privacy focused experience and we believe that

111
00:08:54,320 --> 00:09:01,000
this is the future because devices become more and more powerful, we become smarter and can do

112
00:09:01,060 --> 00:09:07,779
more improvements and for example some things which big companies can do only online you're collecting

113
00:09:07,800 --> 00:09:12,740
data from their users and then maybe try to customize, for example, map experience for

114
00:09:12,740 --> 00:09:13,160
their users.

115
00:09:14,020 --> 00:09:19,000
We may think about customizing user experience locally on the device without even sending

116
00:09:19,040 --> 00:09:24,820
or sharing this data because collecting data locally and not sending it anywhere is different,

117
00:09:24,920 --> 00:09:25,120
right?

118
00:09:25,320 --> 00:09:27,760
So we never ever access this data.

119
00:09:27,800 --> 00:09:29,060
It stays on your device.

120
00:09:29,420 --> 00:09:35,480
It's private, but we can use it, for example, to do better search suggestions or change their

121
00:09:35,680 --> 00:09:37,480
behavior to make it more convenient for you.

122
00:09:37,780 --> 00:09:38,700
This is about the future.

123
00:09:39,140 --> 00:09:40,760
We're not there yet, but this is possible.

124
00:09:42,240 --> 00:09:47,160
And how big companies are using collected data in many ways.

125
00:09:47,420 --> 00:09:50,760
So if the product is free, then you're the product, right?

126
00:09:51,480 --> 00:09:53,820
Yeah, and I want to touch on that too, because you guys are also a free product.

127
00:09:54,520 --> 00:10:01,540
So we should distinguish how open source is a bit of an exception to that rule.

128
00:10:03,220 --> 00:10:09,260
But I think it's really well stated and how it is, you know, just an all-in-one place of everywhere you travel.

129
00:10:09,900 --> 00:10:18,780
So, you know, just to understand the infrastructure a bit more, what you guys provide, because in Apple and Google Maps, you can download an offline maps for a region.

130
00:10:19,440 --> 00:10:21,580
So let's say I'm in California.

131
00:10:22,010 --> 00:10:26,280
I just want to download all of California as an offline map in Apple or Google Maps.

132
00:10:28,040 --> 00:10:30,420
That is the only web request your app makes, though.

133
00:10:30,780 --> 00:10:41,980
Because when I download a California map in Apple Maps and I type in, you know, going to the gym, the directions, that's pinging a server, that's doing all these things.

134
00:10:42,280 --> 00:10:46,920
Apple's probably collecting a lot of that data as well, where I go, how often I go, et cetera.

135
00:10:47,860 --> 00:10:53,120
But you guys, it's just that one web request, which is download a map.

136
00:10:53,180 --> 00:10:54,440
Yes, initial download.

137
00:10:54,690 --> 00:11:02,800
And I would like to mention also that offline functionality has been added in Google and Apple Maps way later,

138
00:11:03,500 --> 00:11:11,040
when our Maps.me was very popular or they had more than 100 million downloads all over the world.

139
00:11:11,560 --> 00:11:17,280
Only then first Google and then Apple started to introduce download offline area.

140
00:11:17,310 --> 00:11:20,820
So they are online first and offline functionality is kind of hidden.

141
00:11:20,880 --> 00:11:23,860
And many users may even not know about it and not using it.

142
00:11:24,400 --> 00:11:26,540
So in our case, we are the opposite.

143
00:11:26,740 --> 00:11:29,240
We are planning to add some online features.

144
00:11:29,420 --> 00:11:30,280
So we are offline first.

145
00:11:30,520 --> 00:11:35,820
We have some ideas how to do many important features for users, like traffic

146
00:11:36,100 --> 00:11:38,800
information, public transport, which we are working on right now.

147
00:11:39,300 --> 00:11:41,500
Users also asking for photos, reviews and whatever.

148
00:11:41,760 --> 00:11:43,860
It's possible to do in privacy friendly way.

149
00:11:44,280 --> 00:11:49,240
We will focus on that, but we are starting offline first from privacy focused way.

150
00:11:49,320 --> 00:11:53,920
So now you have some functionality in Google and Apple Maps, even in offline,

151
00:11:55,500 --> 00:11:56,920
but not fully functional.

152
00:11:57,130 --> 00:12:02,420
So it depends what and how are you using and how far you go from the area.

153
00:12:03,180 --> 00:12:04,900
With organic maps, it's very easy.

154
00:12:04,910 --> 00:12:11,500
You select what you want to visit country or region or even whole Europe or whole United States, download it.

155
00:12:12,040 --> 00:12:12,520
And that's it.

156
00:12:13,000 --> 00:12:17,680
So then only what you may need later update the app, update the map data.

157
00:12:18,320 --> 00:12:18,580
That's it.

158
00:12:19,620 --> 00:12:28,460
So how do you do, you know, do you handle business searching? Is that also a static file that you download as part of the map, like businesses and stuff?

159
00:12:28,620 --> 00:12:30,980
All information is embedded in the map.

160
00:12:31,160 --> 00:12:35,740
So when we first released the first version of Maps with me,

161
00:12:35,860 --> 00:12:40,700
we compressed the whole world OpenStreetMap data into six gigabytes of data.

162
00:12:40,980 --> 00:12:45,720
Of course, there were way less data than right now we have available in OpenStreetMap

163
00:12:45,840 --> 00:12:50,460
thanks to many contributors, including our users and other users all over the world.

164
00:12:50,660 --> 00:12:54,120
But we also embed search related information search index.

165
00:12:54,280 --> 00:12:57,640
So you will be able to quickly find whatever you're looking for.

166
00:12:57,700 --> 00:13:00,640
what was downloaded, of course, what's included in those downloaded maps.

167
00:13:02,340 --> 00:13:07,460
To build a route, we need some specially optimized routing index, which helps to

168
00:13:07,810 --> 00:13:14,480
build routes between downloaded regions. The data also contains Wikipedia articles in a number of

169
00:13:14,660 --> 00:13:20,920
languages. In OpenSuiteMap, you can mark, attach a Wikipedia article to some place, to any place,

170
00:13:21,640 --> 00:13:31,360
if it's relevant. And then we have a toolchain which checks this data and gets fresh Wikipedia dump twice per month.

171
00:13:32,340 --> 00:13:36,520
Wikipedia Enterprise allows to get a full dump and use it in your products.

172
00:13:37,130 --> 00:13:45,460
And we also embed elevation data, which is used to create ISO lines, elevation layer on the map.

173
00:13:45,620 --> 00:13:50,240
And also we are embedding this elevation data into roads and tracks.

174
00:13:50,490 --> 00:13:54,740
So when you build a hiking route, for example, you can preview its elevation

175
00:13:54,900 --> 00:13:56,520
graph, how elevation is changed.

176
00:13:57,290 --> 00:14:03,620
So this data comes from big resources, from Aster, from NASA collected data, SRTM.

177
00:14:04,280 --> 00:14:11,200
There is one guy who combined detailed European elevation data in a database,

178
00:14:11,680 --> 00:14:13,800
the loadable database Zonni.

179
00:14:14,220 --> 00:14:15,480
So we also use his data.

180
00:14:15,510 --> 00:14:20,700
You can check all copyrights and the things which we are using in Organic Maps app or on our website.

181
00:14:20,890 --> 00:14:34,540
We have a special copyright button and page which lists everything, all open source libraries or projects or sources of data, including map data, including icons, fonts, whatever we're using in the app.

182
00:14:35,380 --> 00:14:35,860
Very nice.

183
00:14:36,100 --> 00:14:36,200
Yeah.

184
00:14:36,330 --> 00:14:41,440
And then, you know, just kind of to round out, you know, the privacy discussion, just a couple more questions here.

185
00:14:42,060 --> 00:14:49,220
The first one, I see this come up in a lot of interviews, which is this relationship between cloud first and offline first.

186
00:14:49,800 --> 00:15:01,480
And we see this with very advanced features, like the more that you're able to move to somebody's device, typically the better it's going to be for their privacy in terms of control, ownership, etc.

187
00:15:03,160 --> 00:15:05,480
And it's a philosophy difference.

188
00:15:05,920 --> 00:15:09,380
You know, we have companies like Google who tend to opt to be cloud first.

189
00:15:09,920 --> 00:15:12,400
And Apple still does cloud stuff for sure.

190
00:15:13,200 --> 00:15:19,220
But they do tend to default to try to do things offline when possible, unless they can't make

191
00:15:19,220 --> 00:15:20,040
the experience good enough.

192
00:15:20,100 --> 00:15:21,540
And then they go to the cloud as well.

193
00:15:22,260 --> 00:15:24,680
So you guys are all in on offline only.

194
00:15:26,180 --> 00:15:32,080
You know, so offline LLMs, I think, you know, I don't know if that's what you were kind of

195
00:15:33,040 --> 00:15:37,220
hinting at or similar functionality, but it seems like just the offline world seems to

196
00:15:37,220 --> 00:15:38,300
be exploding in some ways.

197
00:15:38,400 --> 00:15:43,740
So I don't know if there are specific technologies you guys are looking at that can continue to make this offline experience better.

198
00:15:43,890 --> 00:15:50,580
Because as people's devices get more powerful, that gives them more control that only apps like you guys have can actually utilize.

199
00:15:51,620 --> 00:15:58,440
So I don't know if there's a question in there, but yeah, I guess I'll just leave it open to you if you have something to say there.

200
00:16:00,420 --> 00:16:07,160
Yeah, modern devices are quite powerful and have embedded chips which can do a lot of computational work.

201
00:16:07,900 --> 00:16:12,480
And we have some ideas how those capabilities can be leveraged.

202
00:16:12,680 --> 00:16:16,640
But at the same time, we're trying to support as many older devices as possible.

203
00:16:17,100 --> 00:16:20,400
Now the lowest version of Android we support is Android 5.

204
00:16:21,000 --> 00:16:30,260
Although we recently slightly updated requirements, we dropped OpenGL 2.0 devices, super old ones,

205
00:16:30,440 --> 00:16:34,940
because we need OpenGL 3 or later, still Android 5 devices,

206
00:16:35,060 --> 00:16:37,220
to properly render the map,

207
00:16:37,460 --> 00:16:40,220
and we plan also to introduce the satellite layer.

208
00:16:41,540 --> 00:16:44,440
So these features are also required by some people,

209
00:16:44,840 --> 00:16:46,260
especially in areas where OpenStreetMap

210
00:16:46,460 --> 00:16:47,400
doesn't have very good coverage.

211
00:16:47,610 --> 00:16:50,120
So you have just empty map or almost empty map.

212
00:16:50,300 --> 00:16:51,820
So that may be quite helpful,

213
00:16:52,400 --> 00:16:55,060
especially if done properly, also usable in offline.

214
00:16:55,440 --> 00:16:56,880
So we have some ideas there.

215
00:16:58,200 --> 00:16:58,460
Very cool.

216
00:16:59,040 --> 00:17:00,480
And then I had a question, actually,

217
00:17:01,580 --> 00:17:04,660
from one of our Signal members in our Signal group.

218
00:17:04,800 --> 00:17:09,839
someone asked why someone should choose organic maps and they're being like it's a genuine because

219
00:17:09,839 --> 00:17:16,400
they said at the end here frame it as a genuine question not a gotcha so why would someone choose

220
00:17:16,579 --> 00:17:22,760
organic maps over apple maps with advanced data protection enabled and i i think you know maybe

221
00:17:23,250 --> 00:17:29,080
a step below that question is how do you feel about end-to-end encrypted privacy versus offline

222
00:17:29,400 --> 00:17:33,779
privacy almost because that's almost what the question is in a way as well as the apple specific

223
00:17:33,940 --> 00:17:37,780
layers to this? Because I think there probably are some Apple-specific issues that don't.

224
00:17:38,520 --> 00:17:45,260
Yeah, Apple offers end-to-end encryption in many cases. And now the frame of Apple is that it

225
00:17:45,800 --> 00:17:51,220
cares about users' privacy, but still it's a company and it should follow the law.

226
00:17:52,120 --> 00:17:59,000
And if law orders something, then it should follow the law. It's a company in the United States,

227
00:17:59,080 --> 00:18:05,560
right and then with end-to-end encryption it's harder so the company in many cases might officially

228
00:18:05,740 --> 00:18:13,900
say we cannot provide you with data because it's encrypted but still as some recent stories showed

229
00:18:14,040 --> 00:18:20,540
with other messengers for example some metadata can be extracted maybe ip addresses maybe something

230
00:18:20,640 --> 00:18:27,979
else what's not encrypted so in some cases that may be enough so apple is quite good in that and

231
00:18:28,000 --> 00:18:35,040
And I hope it will keep its privacy, not first, but embedded privacy in all these products

232
00:18:35,920 --> 00:18:41,340
still as a valid value, as a feature of their products in regards of organic maps.

233
00:18:41,820 --> 00:18:42,900
Why people would choose it?

234
00:18:43,080 --> 00:18:48,940
So if you compare products, we're of course not there yet with many features, which online

235
00:18:49,120 --> 00:18:51,080
maps, online first maps already have.

236
00:18:51,740 --> 00:18:57,219
If you drop those online features, well, not drop completely, but keep in mind that if

237
00:18:57,240 --> 00:19:02,680
get enough resources we will develop them faster if we have more resources. So if

238
00:19:02,680 --> 00:19:08,080
you compare everything else then we're all the better way better. Why? Because we

239
00:19:08,200 --> 00:19:15,520
don't have anything what we don't need to render maps. So Google and Apple they

240
00:19:16,100 --> 00:19:21,160
also collecting a lot of data about how the products are used. They because of

241
00:19:21,580 --> 00:19:27,200
being online first they had many technological solutions which have a lot

242
00:19:27,220 --> 00:19:39,000
We don't care. We focus on pure map experience, no statistics collection, just how to render the map faster, how to make maps more compact, how to make user experience easy.

243
00:19:39,220 --> 00:19:48,620
This is the critical thing. We think, we're sure that our usability in many cases is easier than in Google Maps.

244
00:19:49,160 --> 00:19:55,560
We can build routes in fewer clicks, fewer taps on the screen than in Google Maps, for example.

245
00:19:57,040 --> 00:20:01,940
And this was number one thing when we started the project many years ago.

246
00:20:02,550 --> 00:20:12,280
We tried to keep it as simple as possible to make it usable by not geeks, not experienced computer guys, gurus, but by your parents.

247
00:20:13,600 --> 00:20:21,780
And there was a famous story when we got a response from one of our users, 70-something years old, granny,

248
00:20:22,360 --> 00:20:26,960
who was using maps on cruise ship and was advertising it

249
00:20:27,160 --> 00:20:29,180
because they were visiting different countries for us

250
00:20:29,180 --> 00:20:30,920
and he had all maps downloaded

251
00:20:31,320 --> 00:20:34,980
and told everyone on board about the product.

252
00:20:35,160 --> 00:20:37,920
So we have many cases like that.

253
00:20:38,040 --> 00:20:41,560
And this is important to make it easy to use.

254
00:20:41,840 --> 00:20:46,160
I still struggle a bit explaining how Google Maps work

255
00:20:46,920 --> 00:20:48,200
for my parents, for example.

256
00:20:48,680 --> 00:20:49,660
It's not easy.

257
00:20:50,140 --> 00:20:54,780
Yeah, I mean, the way that you're almost, you know, I think that somebody can be a true,

258
00:20:55,660 --> 00:21:00,240
you know, offline open source purist about this and only use organic maps all day.

259
00:21:00,680 --> 00:21:05,260
But also what you're saying, you know, there's a real hybrid solution here, which is there

260
00:21:05,380 --> 00:21:09,540
is no harm in somebody downloading organic maps, downloading the maps offline.

261
00:21:10,280 --> 00:21:14,580
And then when they, you know, are going on a road trip in a place that has no cell service,

262
00:21:14,720 --> 00:21:20,100
when they're going camping, when they're in any environment where they actually want an

263
00:21:20,120 --> 00:21:23,940
better offline experience than what Apple and Google can provide with their offline experience.

264
00:21:24,620 --> 00:21:28,220
There is no harm in maybe even using Apple and Google Maps here and there, but then having

265
00:21:28,520 --> 00:21:33,200
organic maps is kind of a fallback for those offline environments. In many cases, it's not a

266
00:21:33,400 --> 00:21:39,060
fallback. It's the first solution. The better for offline. Yeah. Yeah. Because of the map data

267
00:21:39,260 --> 00:21:45,780
quality. This is important moment. So Apple tries to mix some bits of OpenStreetMap data into it.

268
00:21:45,860 --> 00:21:51,620
Google has its own proprietary map database, and it lacks a lot of details, which you already

269
00:21:51,900 --> 00:21:56,200
see in many places all over the world, because volunteers in OppositeMap are not limited.

270
00:21:56,790 --> 00:21:59,540
They can add, you can add whatever you want on the map.

271
00:22:00,000 --> 00:22:05,880
Of course, if something goes wrong, then there are ways to clean it up.

272
00:22:06,140 --> 00:22:09,300
There's vandalism, of course, everywhere, but it's post-moderation.

273
00:22:09,800 --> 00:22:15,660
So that means you have a lot of super nice details on the map, maybe not useful always,

274
00:22:15,740 --> 00:22:22,140
maybe sometimes too overwhelming, but you have it there. And one of our struggles is to decide what

275
00:22:22,220 --> 00:22:26,960
we actually want to show on the map, because users write to us, OpenStreetMap volunteers also write

276
00:22:27,060 --> 00:22:34,180
to us, "Hey, I'm mapping on the map this unique row of trees or single trees, please enable them on

277
00:22:34,180 --> 00:22:41,159
the map. I want to see them on the map." So it's hard to keep it simple, readable, usable. So we have

278
00:22:41,180 --> 00:22:45,760
some ideas how to do it actually so maybe switch different for different use cases switch different

279
00:22:45,890 --> 00:22:51,720
map layers but there's another story so good details super good details level especially for

280
00:22:51,940 --> 00:22:59,520
hikes where volunteers collect a lot of routes a lot of tracks which are just absent on google maps

281
00:22:59,800 --> 00:23:04,960
and on apple maps they are there in open street map and organic maps uses open street map and you

282
00:23:04,960 --> 00:23:10,520
of course can contribute directly from organic maps too right now you can add features now on the

283
00:23:10,540 --> 00:23:16,420
point objects, not roads or buildings, but maybe later we think about that too. Now you can update

284
00:23:16,580 --> 00:23:21,220
the data directly even if you don't have any internet and then you get it, your data will

285
00:23:21,220 --> 00:23:28,900
be uploaded to OpenStreetMap directly. So that's the synergy where we rely on map data from OpenStreetMap

286
00:23:29,080 --> 00:23:35,320
and we support it, we contribute and this is actually one of our main goals to make the map

287
00:23:35,340 --> 00:23:41,800
data quality in OpenStreetMap better than Google Maps quality everywhere, not just in places popular

288
00:23:42,560 --> 00:23:49,700
by some active volunteers. How to make it? Increase the user number of organic maps, tell them about

289
00:23:49,900 --> 00:23:53,960
OpenStreetMap, tell them how data is created, because many people are not aware about it.

290
00:23:54,250 --> 00:24:01,240
They write to us as if we are drawing the map, and then they know how to draw the map, how to add

291
00:24:01,260 --> 00:24:07,900
their own building on the map or other buildings or whatever objects there, then that's it.

292
00:24:08,720 --> 00:24:09,980
It's super hard to compare.

293
00:24:10,670 --> 00:24:15,900
You cannot pay billions to keep the data up to date compared to volunteers working for

294
00:24:16,160 --> 00:24:18,400
free just because they like it all over the world.

295
00:24:19,110 --> 00:24:20,180
So yeah, really well stated.

296
00:24:20,480 --> 00:24:22,900
And actually, the next thing I was going to talk about was OpenStreetMap.

297
00:24:23,460 --> 00:24:26,440
So if somebody's never heard of OpenStreetMap, they don't know what it is.

298
00:24:26,590 --> 00:24:29,600
Do you mind just kind of giving a quick deep dive on what that is?

299
00:24:30,240 --> 00:24:31,140
Yeah, that's very simple.

300
00:24:31,240 --> 00:24:37,220
If everyone knows about Wikipedia, so OpenSuiteMap is like Wikipedia, but for maps, where everyone,

301
00:24:37,680 --> 00:24:43,740
anyone can add or edit or update or remove whatever map data is there. You just need to register

302
00:24:44,540 --> 00:24:48,500
and that's it, contribute the data. There are different ways to contribute, different applications.

303
00:24:48,700 --> 00:24:53,580
You can do it from your browser, you can do from some mobile apps. We have a bit of information on

304
00:24:53,580 --> 00:25:01,200
our website, but you can easily Google it. So there are some rules. There is a wiki, special OpenSuiteMap

305
00:25:01,220 --> 00:25:08,080
Wiki, which says how and what should be mapped to make a consistent, more or less consistent database.

306
00:25:08,620 --> 00:25:10,760
Of course, people sometimes do it their own way.

307
00:25:11,400 --> 00:25:16,460
But yeah, so far the community survives for many, many years.

308
00:25:16,760 --> 00:25:18,620
The data quality is, you see, good enough.

309
00:25:18,840 --> 00:25:21,780
Facebook and other big companies also using it.

310
00:25:21,960 --> 00:25:28,560
And there is this Overture project, which tries to get the best from OpenStreetMap and from commercial data by blending it together.

311
00:25:29,340 --> 00:25:31,920
And many companies already using this data.

312
00:25:31,980 --> 00:25:35,820
And this could not happen if this data was of bad quality, right?

313
00:25:36,920 --> 00:25:37,280
Yeah.

314
00:25:37,760 --> 00:25:41,580
I guess I was going to mention this later, but I feel like it's more relevant to bring it up now.

315
00:25:41,860 --> 00:25:43,860
But how is that data protected?

316
00:25:44,160 --> 00:25:49,900
It doesn't feel fair for free volunteers contributing to an open source project like OpenStreetMaps

317
00:25:50,380 --> 00:25:56,260
and then having Apple, Google, all these other companies potentially scooping up that same data for their proprietary project.

318
00:25:56,640 --> 00:25:59,420
So does OpenStreetMaps have a way of protecting that data?

319
00:25:59,510 --> 00:26:00,960
Do they get some kind of compensation?

320
00:26:01,470 --> 00:26:03,960
Or is that just how it works?

321
00:26:04,110 --> 00:26:07,120
The license is similar to Wikipedia license.

322
00:26:07,640 --> 00:26:16,400
So the license to contribute, you need to accept this license, the terms of this license.

323
00:26:17,120 --> 00:26:21,380
And any of your contributions goes under the terms of this license.

324
00:26:21,920 --> 00:26:30,580
And this license allows anyone to use the data, even in commercial projects, considering that you properly attribute it.

325
00:26:30,800 --> 00:26:35,680
There are some restrictions, some points you can check.

326
00:26:36,960 --> 00:26:44,380
For example, it's not easy to just take whatever you want and mix it with existing OpenStreetMap data.

327
00:26:44,640 --> 00:26:48,520
The rule is you should somehow separate to make different layers of data.

328
00:26:49,120 --> 00:26:51,840
But in general, there are no other restrictions.

329
00:26:52,040 --> 00:26:56,100
And every contributor knows that when he or she registers at OpenStreetMap.

330
00:26:56,540 --> 00:26:56,960
Very nice.

331
00:26:57,020 --> 00:26:59,440
And so what's your relationship with OpenStreetMap?

332
00:26:59,440 --> 00:27:05,060
I know it sounds like they're, are they your only and primary source in organic maps for maps data?

333
00:27:05,580 --> 00:27:08,080
Do you guys have a close relationship with them behind the scenes?

334
00:27:08,160 --> 00:27:09,960
Or do you just integrate the project on your own?

335
00:27:11,180 --> 00:27:14,360
The relationship is we like the project, we support it.

336
00:27:14,520 --> 00:27:19,420
We update maps, missing gaps on the map ourselves, of course.

337
00:27:19,990 --> 00:27:25,960
And this is the only main source of map data right now.

338
00:27:26,090 --> 00:27:30,080
We try to use some data sets for addresses.

339
00:27:30,870 --> 00:27:37,380
For example, the United States Hikert database and the United Kingdom database of postal addresses.

340
00:27:37,700 --> 00:27:39,500
We try to use them in our search.

341
00:27:40,220 --> 00:27:45,780
But we don't have any other map data sources except OpenStreetMap at the moment.

342
00:27:47,620 --> 00:27:47,860
Got it.

343
00:27:47,980 --> 00:27:51,720
And then this is actually another question from one of our TechLorians.

344
00:27:51,880 --> 00:27:56,140
How can the community get more involved and actually help organic maps grow?

345
00:27:56,480 --> 00:28:00,240
I assume OpenStreetMaps could be a part of that, but I don't know what other contributions.

346
00:28:00,500 --> 00:28:01,020
Of course, yeah.

347
00:28:01,080 --> 00:28:03,180
There are many ways to contribute and to help.

348
00:28:03,640 --> 00:28:05,220
So the first one is obvious one.

349
00:28:05,360 --> 00:28:07,440
Go and update OpenStreetMap.

350
00:28:07,840 --> 00:28:12,660
everything that goes into OpenStreetMap will automatically get into Organic Maps with next

351
00:28:13,100 --> 00:28:18,260
data map data update. We, by the way, we now update map data once or twice per month

352
00:28:19,160 --> 00:28:25,240
because it's quite a process, but we of course want to make updates more frequent, more easy,

353
00:28:25,820 --> 00:28:31,920
downloadable, less size, more compressed data, more optimal experience here. So any contribution to

354
00:28:32,020 --> 00:28:37,219
OpenStreetMap already supports Organic Maps and all other worldwide projects which are using

355
00:28:37,260 --> 00:28:45,520
OpenSuitMap. Other ways to support report bugs: we have GitHub where we do collect all issues and

356
00:28:45,720 --> 00:28:52,740
track them and do all our development and GitHub is a convenient place for many reasons to keep track

357
00:28:52,740 --> 00:28:58,960
of the project and to have a lot of free resources because Microsoft supports open source projects

358
00:28:59,600 --> 00:29:05,779
and covers a lot of CI. We run continuous development and check our code and test that it works

359
00:29:05,820 --> 00:29:13,560
using GitHub. So contributing bug reports, code if you know how to code, if you have friends who know

360
00:29:13,600 --> 00:29:18,480
how to implement the feature, you can check the list of our issues or features or requirements,

361
00:29:18,640 --> 00:29:24,940
there are many on GitHub and contribute them. We are looking for people who will help us with

362
00:29:25,220 --> 00:29:35,760
community support, with user support also in different countries, in different languages. We

363
00:29:35,780 --> 00:29:41,220
now which is bridged with metrics so if you don't like telegram you can use metrics but we also

364
00:29:42,020 --> 00:29:49,560
working on expanding in community focused channels in native languages not english not only english

365
00:29:49,640 --> 00:29:57,180
for example other languages too you can donate if you don't know other ways to help you can always

366
00:29:57,300 --> 00:30:04,800
donate and support the scaling of the project so our server expenses grow as our user base grows

367
00:30:04,820 --> 00:30:13,400
Now we estimate that we already have more than six million installs of organic maps all over the world and a lot of active users.

368
00:30:14,320 --> 00:30:25,580
We can only estimate the number of our users because we only get data from Google Play and Apple Store about some numbers they show us.

369
00:30:25,960 --> 00:30:28,240
But we don't have any information about FDroid.

370
00:30:28,720 --> 00:30:41,780
And of course, if people decide to download and install APK, a fresh version of Organic Maps directly from GitHub or using Obtainium or from whatever other source, we don't collect this information.

371
00:30:42,040 --> 00:30:43,180
We don't know how many users there.

372
00:30:43,280 --> 00:30:44,000
We can only guess.

373
00:30:44,340 --> 00:30:46,580
Yeah, those are main ways.

374
00:30:46,600 --> 00:30:52,100
And of course, you can help also by helping our users in our social media.

375
00:30:52,260 --> 00:30:56,080
For example, we have many questions coming from different people.

376
00:30:56,740 --> 00:30:58,140
And any support is helpful.

377
00:30:58,280 --> 00:31:04,420
ideas maybe you have some your own other ideas share them so we are open to everything we're

378
00:31:04,420 --> 00:31:12,440
doing it in our free time and of course we cannot scale ourselves so any help is managing this huge

379
00:31:12,520 --> 00:31:18,420
project and it's huge actually if you can check the activity on github and the flow user questions

380
00:31:18,660 --> 00:31:23,780
requests and feedback and features how many features users want how much time does it take

381
00:31:23,860 --> 00:31:30,240
to test actually. One of the biggest issues is how to prove that some change, some improvement,

382
00:31:30,460 --> 00:31:35,780
some bug fix didn't break anything. Because we release organic maps not only actually for Android

383
00:31:35,940 --> 00:31:40,980
and iOS, but also it works on Macs and on Linux. We may also port it for Windows too.

384
00:31:41,820 --> 00:31:46,820
But that implies that we need to test it everywhere and make sure that it doesn't break. Because if it

385
00:31:46,840 --> 00:31:53,840
it breaks, we got flooded by requests of users. Hey, it doesn't work, fix it, it crashes, whatever.

386
00:31:54,520 --> 00:31:59,520
So of course, we don't want to be in this situation because we don't have enough time to spend on it.

387
00:32:00,500 --> 00:32:06,780
So we want to reduce the amount of user support requests, bugs, and whatever. And that motivates

388
00:32:06,930 --> 00:32:13,900
us to make a better quality software. And to any help in this regard is highly appreciated also.

389
00:32:14,200 --> 00:32:19,060
Yeah, I saw you're on TestFlight and also the, I think, the Google Play beta program as well.

390
00:32:19,510 --> 00:32:20,760
Not on Google Play beta.

391
00:32:21,230 --> 00:32:25,420
We used it in the beginning, but we found that it has some limitations.

392
00:32:25,570 --> 00:32:33,680
And one of the limitations was in the beginning, it was interesting to discover that we got many five-star reviews in beta version on Google.

393
00:32:33,810 --> 00:32:35,920
But they don't go to the main Play Store.

394
00:32:37,300 --> 00:32:40,260
So we decided to use a separate TestFlight app.

395
00:32:40,340 --> 00:32:45,480
And that became more flexible solution because here we don't depend on anything and we can deploy.

396
00:32:45,900 --> 00:32:47,420
We have continuous builds.

397
00:32:48,140 --> 00:32:58,700
Every commit on master, every change provides a build in the slide, which we can automatically test and change and see what's going on there without any dependence on Google Play Store.

398
00:32:59,180 --> 00:33:01,260
But using this Firebase based thing.

399
00:33:01,440 --> 00:33:04,080
And it also helps us to collect some data from crashes.

400
00:33:04,700 --> 00:33:09,980
It's not super privacy friendly in terms that it still goes through Google.

401
00:33:10,340 --> 00:33:18,300
And there were requests to make a beta program, which just goes as is as pure APK without any Google stuff.

402
00:33:18,720 --> 00:33:23,540
Although it will be a bit harder for us to collect fresh reports, but that also should be feasible.

403
00:33:23,760 --> 00:33:26,880
So it requires someone to spend time on that.

404
00:33:27,040 --> 00:33:28,620
And any support here is also appreciated.

405
00:33:29,860 --> 00:33:31,200
Yeah, I don't know if you guys have found this.

406
00:33:31,200 --> 00:33:34,440
I found this maybe a few months ago because I was always curious.

407
00:33:35,880 --> 00:33:37,400
There's this GitHub project.

408
00:33:37,620 --> 00:33:39,020
It's called GitHub Release Stats.

409
00:33:39,400 --> 00:33:41,520
and it tries to estimate the amount of downloads

410
00:33:41,800 --> 00:33:44,260
that you get from releases on GitHub.

411
00:33:45,600 --> 00:33:46,760
Because I know that's quite frustrating

412
00:33:46,860 --> 00:33:47,940
because GitHub doesn't tell you

413
00:33:48,240 --> 00:33:50,800
how many times your releases get downloaded.

414
00:33:51,380 --> 00:33:53,400
So I don't really know the accuracy of it,

415
00:33:53,400 --> 00:33:55,900
but it seems pretty accurate as far as I can tell

416
00:33:56,020 --> 00:33:57,700
based on other things I've used it with.

417
00:33:58,000 --> 00:33:59,800
But it's called GitHub Release Stats,

418
00:34:00,020 --> 00:34:00,780
if anybody's listening.

419
00:34:01,060 --> 00:34:03,520
It's somewhat useful if you have a project on GitHub

420
00:34:03,620 --> 00:34:05,100
and you're curious how many downloads it gets.

421
00:34:05,400 --> 00:34:07,860
So I want to talk a little bit about usability here

422
00:34:07,880 --> 00:34:14,300
because organic maps, a lot of your identity is on this clean experience. It's on the offline

423
00:34:14,639 --> 00:34:20,720
experience. It's something that I think a lot of different people could benefit from. And so I want

424
00:34:20,720 --> 00:34:27,639
to start by just asking, what is your target demographic? Is it anybody who wants that

425
00:34:27,860 --> 00:34:34,840
experience? Do you find that it's mostly people commuting to work? Is it people hiking? What do

426
00:34:34,860 --> 00:34:38,960
you tend to see? And I know it's hard to maybe summarize this when you have such a large community,

427
00:34:39,440 --> 00:34:46,040
but how would you describe that? The current state of our community is more shifted to the

428
00:34:46,730 --> 00:34:54,040
hiking side, to cycling maybe, maybe less than hiking because of the nature of offline maps

429
00:34:54,520 --> 00:35:00,600
and the open street map data quality and lack of online features. The idea is to also introduce

430
00:35:00,620 --> 00:35:06,240
some online features, for example, like public transport, that will open cities for us.

431
00:35:06,740 --> 00:35:10,700
People who live in cities, who commute, commuters, and not only in cities, of course,

432
00:35:11,420 --> 00:35:14,340
but that will be a completely different category of users.

433
00:35:14,880 --> 00:35:23,040
But at the moment, we see many people are using it also as a navigator device in their cars,

434
00:35:23,820 --> 00:35:26,760
because CarPlay and Android Auto are also supported.

435
00:35:27,040 --> 00:35:28,500
There are many things to improve there, of course.

436
00:35:28,820 --> 00:35:29,380
We'll do it.

437
00:35:29,540 --> 00:35:30,680
just question of time and resources.

438
00:35:31,480 --> 00:35:34,460
But we see that many people historically,

439
00:35:34,560 --> 00:35:36,760
when we were working on Maps with me and Maps.me,

440
00:35:36,900 --> 00:35:39,880
we targeted the travelers first.

441
00:35:40,340 --> 00:35:42,360
Because obviously when you go to some country,

442
00:35:42,980 --> 00:35:44,960
there were times of expensive roaming also.

443
00:35:45,160 --> 00:35:46,180
Now it's less critical,

444
00:35:46,420 --> 00:35:48,560
but still there are some connectivity issues.

445
00:35:48,680 --> 00:35:50,940
Sometimes roaming also costs money.

446
00:35:51,480 --> 00:35:53,140
People prepare for the trip.

447
00:35:53,460 --> 00:35:54,740
They plan the route.

448
00:35:54,880 --> 00:35:55,920
They download maps.

449
00:35:56,500 --> 00:35:58,160
They look for interesting places,

450
00:35:58,600 --> 00:36:04,520
side things, whatever, and then go there, you rent a car, you have maps with you already prepared,

451
00:36:04,760 --> 00:36:10,820
working out of the box without even depending on local SIM card or network or whatever, it just

452
00:36:11,000 --> 00:36:18,220
works. So this case is still popular also with organic maps. We may need to tune more the app for

453
00:36:18,460 --> 00:36:23,200
cyclists. We have many requests to improve the routing quality. Cyclists are very demanding in

454
00:36:23,220 --> 00:36:25,540
in terms of which route to choose and how to go.

455
00:36:26,260 --> 00:36:32,820
And there are different types of bikes, of course, MTB guys, one routes, city bikers,

456
00:36:33,200 --> 00:36:33,680
electric bikes.

457
00:36:34,280 --> 00:36:39,060
So we are thinking how to make it usable yet simple.

458
00:36:39,720 --> 00:36:45,500
So this is the trickiest part because there is a product, a good example of solving every

459
00:36:45,780 --> 00:36:45,860
problem.

460
00:36:46,410 --> 00:36:48,340
There is an app called Osmond.

461
00:36:48,960 --> 00:36:49,720
So we know those guys.

462
00:36:49,960 --> 00:36:50,920
I was going to ask about them.

463
00:36:51,680 --> 00:36:51,880
Yeah.

464
00:36:52,600 --> 00:36:55,580
So we know these guys personally and we support each other also.

465
00:36:55,880 --> 00:37:00,560
And they also have open source products under LGPL license.

466
00:37:00,980 --> 00:37:01,780
That's a core difference.

467
00:37:02,200 --> 00:37:05,100
In Organic Maps, we have Apache 0 to 0 license.

468
00:37:05,600 --> 00:37:08,280
So you can fork it and do whatever you want.

469
00:37:08,460 --> 00:37:14,580
Even if you don't want to share any changes, your local changes, you're allowed to do that.

470
00:37:15,000 --> 00:37:16,700
With LGPL, you are not allowed.

471
00:37:16,760 --> 00:37:20,940
You should publish everything what you do in your fork back.

472
00:37:21,360 --> 00:37:24,680
But coming back to Osman, so it's like a Swiss knife for everything.

473
00:37:25,700 --> 00:37:28,880
It can do whatever you want, but it's super complex.

474
00:37:30,400 --> 00:37:31,540
It's hard to explain.

475
00:37:31,900 --> 00:37:34,120
It's super complex, and Organic Maps is the opposite.

476
00:37:34,860 --> 00:37:36,840
So we try to make it simple.

477
00:37:37,760 --> 00:37:41,980
And if you try both products, you will see how big is the difference.

478
00:37:42,390 --> 00:37:44,800
And we try to keep it simple, and it's hard to keep it simple.

479
00:37:46,340 --> 00:37:51,940
It's fascinating, too, because the OSM, OSM, OSM is OpenStreetMap.

480
00:37:51,940 --> 00:37:55,600
So you guys should be using the same exact maps data.

481
00:37:56,300 --> 00:37:58,340
So it's actually controlled for.

482
00:37:58,910 --> 00:38:03,400
The only difference is how you guys interact with that same maps data.

483
00:38:03,410 --> 00:38:09,260
So it really is a good apples-to-apples comparison of kind of the usability differences and who the target demographic is.

484
00:38:09,660 --> 00:38:14,260
How would you describe the target demographic between OSM and OrganicMaps?

485
00:38:15,040 --> 00:38:32,300
Osmond is more for professionals who know what is needed, what's required, who needs those tuning settings, who is ready to spend time to learn how to tune up so it will perfectly do whatever the person wants in whatever custom way.

486
00:38:33,260 --> 00:38:39,640
Organic maps is for people who, we have many users actually, Osmod users also using organic maps in

487
00:38:39,800 --> 00:38:44,640
cases that they don't want to think, they don't, well they want just something simple, just find

488
00:38:44,780 --> 00:38:49,880
something, go there or in few clicks, then they also use organic maps, we have those cases too. So

489
00:38:50,180 --> 00:38:55,000
this is our main audience. Of course we want to cover more and more people by offering them more

490
00:38:55,040 --> 00:39:02,360
functionality, but we try to do it in an easy way, in a simple way. We spend 80% of time thinking how

491
00:39:02,380 --> 00:39:07,800
to make it easier and only 20% of time implementing it. Because the hardest part is to make it simple.

492
00:39:09,300 --> 00:39:14,700
It's easy to make it complex, super easy to make everything complex. So you just put it on top of

493
00:39:14,840 --> 00:39:20,840
something and then you get some monster which just doesn't work as you expect. In many cases,

494
00:39:20,870 --> 00:39:28,200
you need time to learn how it works. That's not about organic maps. Here we target users who don't

495
00:39:28,200 --> 00:39:34,580
want to think, who just wants to get somewhere, wants to find something, wants to mark something,

496
00:39:35,320 --> 00:39:42,300
to do something easily, obviously, even without any experience with maps. And even if, I don't know,

497
00:39:42,370 --> 00:39:47,500
there is no internet, there is nothing where you can find some help. So it should just work. And if

498
00:39:47,500 --> 00:39:53,960
you have ideas how to make it simple, let us know. We are open to everything that simplifies, that makes

499
00:39:53,980 --> 00:39:59,960
organic maps even simpler, even easier to use. The iOS versus Android experience,

500
00:40:00,780 --> 00:40:05,000
is it exactly the same? Are there any differences that users should know about?

501
00:40:06,020 --> 00:40:12,820
There are some differences, but not significant. So historically, we focused more on iOS first,

502
00:40:13,000 --> 00:40:18,000
and Android was following it because of the audience and because we started first,

503
00:40:18,220 --> 00:40:26,760
the first release of Maps with me in 2011 was in App Store because also in many cases iOS UX and UI

504
00:40:27,060 --> 00:40:33,520
have user interface, user experience are better than in Android devices. And because it's easier to

505
00:40:34,100 --> 00:40:38,660
start there because Apple ecosystem is monolithic, it doesn't have the zoo of different versions,

506
00:40:38,920 --> 00:40:44,720
devices, vendors, issues, screens, whatever, whatever. So that's an easier start and then we polish it on

507
00:40:44,760 --> 00:40:51,000
iOS, we try to implement something similar on Android. Although opposite cases there also

508
00:40:51,280 --> 00:40:55,340
happened several times when we did something first for iOS and then ported it back. But

509
00:40:55,810 --> 00:41:00,900
we try to keep apps in sync as much as possible. So they are more or less mostly in sync.

510
00:41:01,320 --> 00:41:07,420
Very nice. And then you mentioned public transit earlier as something being in progress. What does

511
00:41:07,420 --> 00:41:12,200
that currently look like? Is that an OSM limitation? Is that an organic maps limitation? Do you mind

512
00:41:12,220 --> 00:41:21,480
just speaking on that? Oh, yeah, that's the topic. So, as I mentioned before, we want to open a new

513
00:41:21,780 --> 00:41:27,840
audience, commuters in Organic Maps. And I'm personally using some other apps, including Google

514
00:41:28,060 --> 00:41:34,240
Maps, including local traffic transit data maps, including some other things, and Apple Maps also,

515
00:41:34,860 --> 00:41:41,280
to estimate when and how can I get my public transport to someplace. And I frequently observe

516
00:41:41,300 --> 00:41:48,760
that the proposed routes are inefficient. Even those giant companies, big companies, even local

517
00:41:48,960 --> 00:41:54,100
companies, local transport companies cannot always provide you with an efficient route, especially

518
00:41:54,160 --> 00:42:00,340
it has many changes, not just one bus or one tram or train, whatever, but several changes. There is

519
00:42:01,080 --> 00:42:08,260
a lot of space for improving there. And now we, of course, thinking about how to better implement it.

520
00:42:08,400 --> 00:42:16,220
The initial idea was to do it also offline first, meaning that we would be limited by the frequency of map data updates.

521
00:42:17,140 --> 00:42:27,540
And meaning that we in this way, we would not support live changes in traffic, which is quite important in some cases when transport is delayed or rescheduled or whatever.

522
00:42:28,380 --> 00:42:38,080
So that's why we decided to go here and experiment with online live information about public transport in two steps.

523
00:42:38,280 --> 00:42:51,240
So first step is we want to release the live or where it's available live where it's not available at least static some schedule information and attach it to public transport stops on the map.

524
00:42:51,290 --> 00:42:57,800
So you can, for example, select a stop on the map and see the schedule when the next tram or bus or train comes.

525
00:42:58,150 --> 00:43:04,660
And if there are any delays and if there is this data, live data available, then it will also show you is it delayed or not.

526
00:43:04,660 --> 00:43:06,940
Is it on time or not as a first step.

527
00:43:07,860 --> 00:43:19,280
And as a second step, we plan, of course, to do a full expected from many users routing based on public transport data, on live public transport data, which will not just build a route right now.

528
00:43:19,400 --> 00:43:29,080
You can also build a public transport route in organic maps, but it's limited to offline and it's limited to subways and light rails only in some large cities.

529
00:43:30,060 --> 00:43:32,260
So it works already there, but it's offline.

530
00:43:32,320 --> 00:43:33,840
You cannot see the time.

531
00:43:34,780 --> 00:43:35,700
You cannot see the schedule.

532
00:43:36,100 --> 00:43:39,780
It's also quite important in some countries to see the schedule, for example, for ferries.

533
00:43:40,370 --> 00:43:44,280
Right now, organic maps can build the route through ferry, but there is no schedule there.

534
00:43:44,930 --> 00:43:48,460
So in some countries it's frequent, in some it's not.

535
00:43:48,670 --> 00:44:05,020
This is our vision and idea that only if we provide actual, up-to-date, live data compared, ideally better, with what Google Maps or other maps are providing, then users may think about switching to organic maps.

536
00:44:05,680 --> 00:44:07,660
So we want to do it right.

537
00:44:08,000 --> 00:44:11,660
We want to do it properly, of course, from a privacy perspective also.

538
00:44:11,900 --> 00:44:12,840
We want to do it right.

539
00:44:13,420 --> 00:44:16,860
And we want to also contribute to OpenStreetMap in this regard.

540
00:44:16,960 --> 00:44:22,920
And we already started a project which helps to attach scheduled information feeds to OpenStreetMap stops.

541
00:44:23,280 --> 00:44:31,380
That also helps a lot to improve the OpenStreetMap data quality in many countries where stops were not added on the map yet, for example.

542
00:44:31,660 --> 00:44:36,160
So we have a tool, online tool, GTFS OpenStreetMapMatcher,

543
00:44:36,700 --> 00:44:40,780
which helps contributors and editors to update OpenStreetMap data

544
00:44:41,000 --> 00:44:42,780
with relevant public transport information.

545
00:44:43,680 --> 00:44:48,580
And we plan to develop it also as a part of our support

546
00:44:48,880 --> 00:44:51,120
for online public transport schedules.

547
00:44:51,960 --> 00:44:53,240
We want to contribute back also.

548
00:44:53,440 --> 00:44:56,360
And there are already good improvements there.

549
00:44:56,690 --> 00:45:00,320
So if you want more details, just contact us or check our GitHub.

550
00:45:00,640 --> 00:45:07,440
There is some information here, or maybe we'll publish more details in the news post when we release the feature.

551
00:45:07,730 --> 00:45:10,820
Finally, I hope it will happen soon in the upcoming months.

552
00:45:11,140 --> 00:45:12,320
So we'll see.

553
00:45:13,160 --> 00:45:22,380
It's exciting because I was actually going to directly ask you, maybe in like one or two questions, I have just a final little list here I've been creating as we're going along.

554
00:45:23,660 --> 00:45:27,080
And it was, you know, how do you deal with the restriction of no real time data?

555
00:45:27,140 --> 00:45:33,340
I feel like that is the one very nice, legitimate use case for having an internet connected

556
00:45:33,600 --> 00:45:33,800
experience.

557
00:45:34,210 --> 00:45:39,440
And so that does, I think if there is going to be anything that needs to be online in

558
00:45:39,440 --> 00:45:42,040
a maps program, I think that's the one feature I'd really enjoy.

559
00:45:42,360 --> 00:45:43,700
How do you balance that?

560
00:45:44,040 --> 00:45:46,180
Do you think it's going to be opt in, opt out?

561
00:45:46,580 --> 00:45:51,140
How do you kind of envision the flow looking like for users so that they know when it's

562
00:45:51,230 --> 00:45:51,840
online and offline?

563
00:45:52,010 --> 00:45:54,520
Because now we have this whole identity of everything being offline.

564
00:45:55,020 --> 00:46:00,520
So when you add one thing that's online, even if it's done in a privacy-respecting way, I could imagine some community pushback.

565
00:46:01,220 --> 00:46:03,640
So I don't know how you're kind of juggling that.

566
00:46:04,160 --> 00:46:06,740
We, of course, plan to do it very explicitly.

567
00:46:07,080 --> 00:46:13,760
For now, the idea is that when you select public transport stop, before doing any request to internet,

568
00:46:14,120 --> 00:46:20,480
to our CDN where we will store prepared, processed information for schedules,

569
00:46:21,420 --> 00:46:26,100
Before doing any internet requests, you will get asked, do you want it or not?

570
00:46:26,340 --> 00:46:44,240
Because there's already a setting in Organic Maps left from Maps.me times where you can set the app, for example, disable any access to internet, ask when necessary for every request, or you can allow it for any request, for example, and we want to respect this setting.

571
00:46:44,400 --> 00:46:50,120
So you can explicitly control, but of course, we want to stay privacy focused, privacy friendly.

572
00:46:50,340 --> 00:46:55,860
So no requests and if requests will go, they will go to our servers where we don't collect

573
00:46:56,490 --> 00:46:59,780
any logs, don't store any user information.

574
00:47:00,010 --> 00:47:05,520
So it's just pre-processed, prepared chunks of data which will be cached and downloaded

575
00:47:05,630 --> 00:47:08,560
by clients and they will be also used offline.

576
00:47:09,460 --> 00:47:15,820
If you pre-downloaded, got some information about your area, some schedules, then you

577
00:47:15,840 --> 00:47:21,360
don't have connection anymore for example, the old cached information will still be useful

578
00:47:21,720 --> 00:47:27,940
in many cases because usually static schedules don't change frequently. In Switzerland for example

579
00:47:28,000 --> 00:47:34,020
they change their schedule once per year so that should be good enough in many cases even without

580
00:47:34,620 --> 00:47:39,280
online internet connection. We also investigate get direction and investigate the case maybe of

581
00:47:39,680 --> 00:47:45,800
distributing some static information schedules information with map data directly or downloading

582
00:47:45,820 --> 00:47:52,480
separately, or we have some ideas here. We need to understand how users will approach this new

583
00:47:52,700 --> 00:47:57,660
feature and get some feedback first to choose the best way. There, so you heard it here. If you're

584
00:47:58,000 --> 00:48:04,520
an organic maps user and you want to help guide the direction of this, that's the call to do so

585
00:48:04,760 --> 00:48:10,860
before it rolls out. You know, on that note, one of our SecLorians in the Signal group also asked,

586
00:48:10,900 --> 00:48:15,960
what happens if there's no funding or a key maintainer leaves? Is there a succession plan?

587
00:48:16,380 --> 00:48:20,980
How do you think about your longevity? So just in general, I'd love to hear a little bit more about

588
00:48:21,400 --> 00:48:25,440
kind of you guys as an organization and kind of what this looks like behind the scenes.

589
00:48:26,760 --> 00:48:32,320
Everything is open source. So even if something happens with us maintainers, the code stays there.

590
00:48:32,540 --> 00:48:39,180
So organic maps is available. You can download, you can fork it, you can continue doing whatever

591
00:48:39,200 --> 00:48:45,640
you want with it. So our role here is to, with our experience, to push the project into the right

592
00:48:45,820 --> 00:48:51,740
direction, keeping important goals in mind and keeping important values. Otherwise, we would

593
00:48:52,200 --> 00:48:59,560
implement second Osman many years ago. So in terms of hit by bus principle, you cannot stop open

594
00:48:59,760 --> 00:49:07,260
source, right? So it's open. That's the key. Yeah. Over the years, I've been kind of burned on some

595
00:49:07,280 --> 00:49:12,340
open source projects, right? Like I find something I really love. It becomes a new part of my

596
00:49:12,500 --> 00:49:18,300
workflow. I use it for six months and it really becomes a part of my life. And then the maintainer

597
00:49:18,400 --> 00:49:23,740
drops it. So I think that's kind of where people might be asking that question from. And so even

598
00:49:23,920 --> 00:49:29,260
if there was a fork, like what if there's a gap there? Is there maybe some more protections than

599
00:49:29,260 --> 00:49:35,200
a normal open source project for someone who has that concern? We like what we do. I don't know

600
00:49:35,220 --> 00:49:42,380
what will happen in the future, but at this moment, I say that this is the best place for me to learn,

601
00:49:43,010 --> 00:49:48,000
to get new experience in different areas. So this is where I learn about many, many things.

602
00:49:48,470 --> 00:49:55,160
So I was in different roles on the project from engineer to support to marketing person to CEO.

603
00:49:56,620 --> 00:50:03,099
I mean, during all those years in Maps with me, Maps Me, now in Organic Maps. And you never get

604
00:50:03,120 --> 00:50:14,260
such an interesting experience and losing that no yeah yeah and then um i saw on your website that

605
00:50:14,400 --> 00:50:20,480
your your organization is based out of toland in estonia and then you mentioned that you're you're

606
00:50:20,480 --> 00:50:27,760
out of switzerland so you guys are a global team what does that kind of look like yeah we all are

607
00:50:27,780 --> 00:50:32,680
different countries right now and working from different countries remotely.

608
00:50:34,240 --> 00:50:41,080
We opened the registered company in Estonia because it was easy for remote registration and

609
00:50:41,320 --> 00:50:48,720
because we wanted to have some legal protection of course because it's way different if you publish

610
00:50:48,960 --> 00:50:55,280
some apps in stores as a physical person or as an organization. So we needed some easy simple

611
00:50:55,300 --> 00:51:00,880
solution without a lot of overhead throwing in a lot of money or time to support it so that was

612
00:51:01,230 --> 00:51:07,020
the easiest option and we are open to to changes if they will improve something so

613
00:51:07,760 --> 00:51:14,560
we're considering different other options also where discussions about even some maybe non-profit

614
00:51:14,770 --> 00:51:20,660
stuff something else and we had already compared different options they all have their pros and

615
00:51:20,680 --> 00:51:28,440
cons and still at the moment our main focus is on development and scaling the development on getting

616
00:51:28,920 --> 00:51:34,960
it right in terms of organizing the process everything so to get frequent releases frequent

617
00:51:35,180 --> 00:51:43,440
features bug fixes and the different business entity right now is not a blocker but we are open

618
00:51:43,440 --> 00:51:50,640
to discuss any other options if they improve the user experience then we are open of course we are

619
00:51:50,660 --> 00:51:53,660
users first. So users drive our decisions.

620
00:51:55,480 --> 00:51:59,780
Very nice. And then, you know, just in the next, let's just say five years, what do you

621
00:52:00,640 --> 00:52:05,620
all kind of envision as kind of the future of organic maps? Like, how would you like

622
00:52:05,620 --> 00:52:06,140
to see things?

623
00:52:07,440 --> 00:52:15,640
Oh, that's a very good question. So I think in five years, we definitely get at the level

624
00:52:15,640 --> 00:52:22,700
comparable with Google Maps, Apple Maps and some other maps and we will be better in some

625
00:52:23,340 --> 00:52:31,260
regards because we see how the nations grow when our user base grows and if this process

626
00:52:31,560 --> 00:52:36,020
continues there is a high chance that we get enough resources to scale the development,

627
00:52:36,300 --> 00:52:42,519
scale the product and invest time, invest money into also server infrastructure for example

628
00:52:42,600 --> 00:52:50,540
to do properly efficient public transport at scale, to do live traffic data, privacy focused,

629
00:52:50,680 --> 00:52:56,700
of course, opt-in also at scale, very requested feature, as I mentioned, satellite imagery.

630
00:52:57,140 --> 00:53:03,320
And of course, we did some questionnaire and our users responded, why are they still using Google

631
00:53:03,520 --> 00:53:09,320
Maps on some other maps? Because they have actual up-to-date business information with photos and

632
00:53:09,340 --> 00:53:16,380
reviews. So this is also a very important part of the product which needs efficient approaches,

633
00:53:16,560 --> 00:53:21,300
not just to implement it technically, but the main problem of such features is

634
00:53:22,260 --> 00:53:27,120
vandalism and the quality of the data. How to keep it free of advertisement, free of scam,

635
00:53:27,360 --> 00:53:33,440
free of bad things. And big companies like Google or Apple can afford some people,

636
00:53:33,660 --> 00:53:38,400
pay some people who will maintain it, keep it of good quality, review, whatever.

637
00:53:39,110 --> 00:53:42,860
In our case, we cannot afford some moderation.

638
00:53:44,030 --> 00:53:48,280
So we need to think about how to scale it properly,

639
00:53:48,500 --> 00:53:52,300
like OpenStreetMap or Wikipedia were scaled maybe or something similar.

640
00:53:52,550 --> 00:53:58,140
So if someone has any ideas how to do it right at scale for billion of users,

641
00:53:58,480 --> 00:54:02,500
our target is at least billion of users, and we feel it's feasible,

642
00:54:02,780 --> 00:54:09,780
then yeah, any ideas are welcome. On the note of traffic data, this comes back. I just have a few

643
00:54:09,780 --> 00:54:14,720
more questions to kind of round this out, but a couple more coming up here. So I remember there

644
00:54:14,820 --> 00:54:19,260
was a story, I forgot who it was from, but they had a wheelbarrow and they put a ton of Android

645
00:54:19,520 --> 00:54:24,880
phones in it with Google Maps and they started walking down a street and it pretty much like

646
00:54:25,240 --> 00:54:29,800
they got Google Maps to show that street is completely congested because that's how they

647
00:54:29,820 --> 00:54:31,940
they, you know, source that traffic data.

648
00:54:32,480 --> 00:54:36,940
How do you source traffic data if, you know, theoretically you're not going,

649
00:54:37,330 --> 00:54:40,860
unless you're just going to rely on your own users to send pings of their route.

650
00:54:42,220 --> 00:54:43,080
But what does that look like?

651
00:54:43,130 --> 00:54:45,620
Do you have any ideas of how you would source traffic data privately?

652
00:54:47,580 --> 00:54:50,160
So the data can be anonymized, of course.

653
00:54:50,460 --> 00:54:55,980
And the main source of data would be, of course, our own users after explicit opt-in, of course.

654
00:54:56,160 --> 00:55:03,120
There are ways maybe to think about some external providers, but it depends, of course, on conditions.

655
00:55:03,720 --> 00:55:09,980
We need to think to make it affordable and privacy friendly to use some initial data to fit it in.

656
00:55:09,980 --> 00:55:14,860
But we would prefer to start with public data and user generated data.

657
00:55:15,280 --> 00:55:26,840
And here the question is only in the volume of the data, because if you get enough users everywhere, then you get enough data to show the proper traffic information.

658
00:55:27,560 --> 00:55:32,220
But actually, if you think about it, this is the use case for congested cities, mostly.

659
00:55:33,040 --> 00:55:40,500
And sometimes it's the case for people traveling for long distance between countries or between regions, between cities.

660
00:55:40,900 --> 00:55:48,900
So it's not useful in 100% of use cases when you drive the car, but of course, it's very helpful to plan and to see this information.

661
00:55:49,140 --> 00:55:55,960
So we are looking for people who will help us to lead this direction, for example, traffic information.

662
00:55:56,040 --> 00:56:01,840
So we have now a very active contributor who leads the public transport direction feature.

663
00:56:02,360 --> 00:56:22,880
And if someone wants or feels capable enough to drive this feature, we would offer any help, any expertise, any ideas we already have to make it real and implement traffic information, which will be free for everyone, actual, privacy-friendly, at scale.

664
00:56:24,080 --> 00:56:24,940
That would be nice, right?

665
00:56:25,160 --> 00:56:39,260
Do you envision this being an organic maps exclusive thing, like you can only find it there? Or would this be somehow something like OSM, where any other open source apps program or even Apple and Google theoretically could utilize that data too, just out of curiosity?

666
00:56:39,640 --> 00:56:49,700
That's a quite feasible option because then if many projects, many products can contribute to the same data source, then the data quality may improve.

667
00:56:50,220 --> 00:56:52,980
So this is one of possible options and we consider it too.

668
00:56:53,480 --> 00:56:56,500
But again, it depends on someone actively driving it.

669
00:56:56,860 --> 00:57:05,740
So if we find a way to scale, if we find a person who will be ready to lead that, to help with that, yeah, why not?

670
00:57:06,440 --> 00:57:07,180
Everything is possible.

671
00:57:07,620 --> 00:57:12,600
And the last major question I had here was something I wrote down myself and a Techlorian

672
00:57:12,820 --> 00:57:16,700
asked about it because I don't know if you saw this, but Pokemon Go, I never played it,

673
00:57:16,780 --> 00:57:18,760
but so many of my friends would play it.

674
00:57:18,900 --> 00:57:23,660
And I was coaching high schoolers who would go on runs and they brought their phones with

675
00:57:23,780 --> 00:57:30,760
them and they play Pokemon Go on their runs as well, which for me drives me crazy because

676
00:57:30,800 --> 00:57:32,700
I'm like, you're supposed to disconnect when you go for a run.

677
00:57:34,540 --> 00:57:37,540
But there was a company called Niantic, Niantic.

678
00:57:38,100 --> 00:57:42,000
And essentially, it came out recently that they were using those real world movement data

679
00:57:42,640 --> 00:57:45,860
to build AI and build proprietary map data.

680
00:57:46,600 --> 00:57:49,100
And so I just kind of wanted your thoughts on that.

681
00:57:49,100 --> 00:57:53,220
I feel like this is exactly the situation where organic maps is like, yeah, see, told

682
00:57:53,260 --> 00:57:54,920
you so, like, we don't do this kind of thing.

683
00:57:55,040 --> 00:57:57,180
Of course, Pokemon Go is not a maps program.

684
00:57:57,360 --> 00:58:01,000
It's not Apple Maps, but it actually kind of is in a way like the whole point of Pokemon

685
00:58:01,060 --> 00:58:02,940
Go is to go to a specific location.

686
00:58:03,060 --> 00:58:04,140
It tells you how to get there.

687
00:58:04,720 --> 00:58:06,320
and there's something you do when you get there

688
00:58:06,420 --> 00:58:07,660
and then you go to your next stop.

689
00:58:08,240 --> 00:58:10,740
So I'm just curious for your thoughts, I guess.

690
00:58:13,040 --> 00:58:15,000
Well, that was a nice use case,

691
00:58:15,360 --> 00:58:19,260
how to collect the data for free, almost for free.

692
00:58:20,480 --> 00:58:22,860
So just a business, you know, how it's done,

693
00:58:23,040 --> 00:58:23,940
just a business for someone.

694
00:58:25,080 --> 00:58:28,200
And yeah, I know many products and companies

695
00:58:28,520 --> 00:58:31,340
collecting the data in different ways for their own needs.

696
00:58:31,600 --> 00:58:33,580
And of course, it's usually legally covered.

697
00:58:33,660 --> 00:58:39,900
when you press accept without reading agreement you may be skipping something important already mentioned there.

698
00:58:40,040 --> 00:58:43,460
So we don't plan, we don't want anything like that.

699
00:58:44,060 --> 00:58:55,360
Although we have ideas about improving OpenStreetMap data by running, for example, just an idea to record the video in real time

700
00:58:55,880 --> 00:59:01,580
when you drive on the road or you go walk on the street, record it locally, analyze it locally,

701
00:59:01,660 --> 00:59:07,720
extract useful house numbers, street names, signs or whatever.

702
00:59:08,420 --> 00:59:10,780
And then of course opt in explicitly

703
00:59:11,540 --> 00:59:12,860
contributed back to OpenStreetMap.

704
00:59:13,780 --> 00:59:13,840
- Wow.

705
00:59:14,540 --> 00:59:15,200
- That would be nice.

706
00:59:15,540 --> 00:59:16,520
- That's so incredible.

707
00:59:17,060 --> 00:59:18,560
I mean, it just automates the current,

708
00:59:19,660 --> 00:59:20,760
what you described is no different

709
00:59:20,920 --> 00:59:21,840
than how it currently works,

710
00:59:21,880 --> 00:59:23,540
which is someone has to go and take photos,

711
00:59:23,940 --> 00:59:24,780
opt in to contributing,

712
00:59:24,860 --> 00:59:28,660
but that's just automating it via videos instead of photos.

713
00:59:28,720 --> 00:59:30,120
- Yeah, and with OpenStreetMap,

714
00:59:30,260 --> 00:59:31,480
everything should be very explicit.

715
00:59:31,680 --> 00:59:33,780
The community doesn't like automated imports

716
00:59:34,300 --> 00:59:35,200
and there are reasons for that.

717
00:59:35,360 --> 00:59:38,400
So if it's user control, but hinted by the app,

718
00:59:38,400 --> 00:59:40,800
for example, just confirm you saw it,

719
00:59:41,180 --> 00:59:42,220
is it the right sign?

720
00:59:42,460 --> 00:59:43,940
Is it the right speed limit for the road?

721
00:59:44,600 --> 00:59:45,920
Then yeah, why not?

722
00:59:46,400 --> 00:59:47,560
Yeah, very nice.

723
00:59:48,120 --> 00:59:51,360
Well, is there anything that we missed

724
00:59:51,640 --> 00:59:53,360
or that you feel like our audience should hear

725
00:59:53,740 --> 00:59:54,840
before we start rounding this out?

726
00:59:55,060 --> 00:59:56,340
So that's the end of my questions.

727
00:59:56,920 --> 01:00:11,320
Recently, I got a question from one user on GitHub, why the project, the codename of the project mentioned in many places was called O-M-I-M.

728
01:00:12,980 --> 01:00:19,100
And it started in Minsk and Belarus, where I'm from, originally from, in 2010.

729
01:00:19,820 --> 01:00:23,480
And it was one month we spent in Minsk.

730
01:00:23,720 --> 01:00:25,860
One month in Minsk.

731
01:00:26,320 --> 01:00:28,180
So that's the reason of this acronym.

732
01:00:29,440 --> 01:00:35,240
And that was the day when we decided to take some vacation to try if we will be able to

733
01:00:35,320 --> 01:00:41,440
build, to prototype some technology which can be useful on phones in offline.

734
01:00:41,760 --> 01:00:45,360
We didn't know when we started it in 2010, will it work or not?

735
01:00:45,600 --> 01:00:51,760
We didn't know how interesting and fruitful and experience the road will be in the future.

736
01:00:52,120 --> 01:00:59,820
We just took our time, gathered together with my friends, colleagues, and tried to build something new, something unique.

737
01:01:00,000 --> 01:01:07,240
And now in six years, looking back, I see it as one of the best tries which I did in my life.

738
01:01:07,480 --> 01:01:13,040
So I already spent more than a decade on improving working maps.

739
01:01:13,400 --> 01:01:16,360
And this was one of the best journeys.

740
01:01:16,580 --> 01:01:19,200
And I hope it will be even more exciting journey.

741
01:01:19,460 --> 01:01:21,640
So thanks for inviting me here.

742
01:01:21,880 --> 01:01:22,760
Thanks for your questions.

743
01:01:23,060 --> 01:01:33,180
And I hope our time, our work makes this world a little bit better and makes your life a little bit easier in some cases when you use maps.

744
01:01:33,860 --> 01:01:36,960
And if you have any ideas, improvements, always welcome.

745
01:01:38,380 --> 01:01:39,000
Yeah, thank you so much.

746
01:01:39,080 --> 01:01:45,260
And I know, you know, these things are very much just out of the goodwill of the people who put them together.

747
01:01:45,560 --> 01:01:51,380
So is there any place where the people listening can connect with you all outside of just downloading organic maps, I assume?

748
01:01:52,100 --> 01:01:57,780
Yeah, we have all our contacts channels on organicmaps.app website.

749
01:01:58,180 --> 01:02:05,720
You will easily find us directly by my GitHub username and social networks username is Biodranic.

750
01:02:06,220 --> 01:02:08,640
Alexander Barsik can Google also my personal website.

751
01:02:09,020 --> 01:02:12,460
So we're open to any contacts, any communication ideas.

752
01:02:12,900 --> 01:02:14,240
Please let us know what you think.

753
01:02:15,220 --> 01:02:20,360
Any good words of support also helpful when we share it in our internal contributors'

754
01:02:20,500 --> 01:02:28,680
chats everyone enjoys hearing how helpful the product is so we we like what we do this is the

755
01:02:28,720 --> 01:02:34,260
most important thing like what you do and make this world better yeah it's something i hear from every

756
01:02:34,420 --> 01:02:40,860
project like the the amount of it's not always bad criticism but the amount of criticism to

757
01:02:41,720 --> 01:02:47,799
praise ratio is pretty skewed and so those nice things that all of you listening say to any of

758
01:02:47,820 --> 01:02:51,920
your favorite projects. It like really does mean a lot to the people behind them. So I'm glad that

759
01:02:52,220 --> 01:02:57,340
you guys still get a lot of nice words. And I'll definitely encourage everybody listening who uses

760
01:02:57,500 --> 01:03:02,080
Organic Maps to send along some kind words to you all. Yeah. And of course, I would like to say a lot

761
01:03:02,080 --> 01:03:11,580
of thanks to every contributor, every user, everyone who donated money, everyone who told his friends

762
01:03:11,720 --> 01:03:16,499
or her friends or parents about Organic Maps. Thank you for your support. Organic Maps wouldn't be

763
01:03:16,520 --> 01:03:21,080
possible without you, without your support. So thank you very much. We are really grateful for

764
01:03:21,600 --> 01:03:27,260
all the support, for every dollar you donate, for every comment, every feedback. We read everything.

765
01:03:27,390 --> 01:03:31,480
We try to respond to everything. So don't hesitate. Stay in touch.

766
01:03:32,960 --> 01:03:34,020
Great. Thank you so much, Alexander.

767
01:03:35,000 --> 01:03:35,920
Thank you. Thank you, Henry.

768
01:03:36,920 --> 01:03:41,120
And I hope you liked that one as much as I did. It was very much a nice sit down,

769
01:03:41,740 --> 01:03:46,480
relaxed conversation with Alexander. If you enjoyed this interview and you want to

770
01:03:46,480 --> 01:03:51,320
this podcast, keep it growing, and allow us to continue to invite on some amazing guests. You can

771
01:03:51,400 --> 01:03:55,420
become a TechLorean in the show notes. You'll get access to a private signal group. You get access to

772
01:03:55,420 --> 01:04:00,580
a private RSS feed. Here are credits in both our videos and on the website, depending on the tier

773
01:04:00,680 --> 01:04:05,120
that you pick. And of course, you get to just keep this podcast going and support the work that we

774
01:04:05,220 --> 01:04:08,640
are doing. If you enjoyed this interview and you learned something from it, make sure to also drop

775
01:04:08,700 --> 01:04:12,800
a like, leave a rating. I noticed Techlore Talks does not have as many ratings as surveillance

776
01:04:12,800 --> 01:04:16,900
reports. So I definitely hope that if you are listening on a platform like Apple, YouTube,

777
01:04:17,140 --> 01:04:20,720
or Spotify, you give a like or leave a rating. So thank you very much for that.

778
01:04:21,220 --> 01:04:24,280
And I will see you all next time on Techlore Talks. Thank you for listening.