On Tue, Mar 21, 2017 at 7:22 AM, Dan Garry wrote:
> The size of your app can significantly reduce downloads [1].
> [1]: https://segment.com/blog/mobile-app-size-effect-on-downloads/
That article seems super sketchy. They took a 3MB app, increased it to
100MB+, and interpolated the retention cha
Dan,
On Tue, Mar 21, 2017 at 6:24 PM, you wrote:
>
> Please do not twist my words. I said technical considerations are relevant,
> not that customer needs do not come first. If something is incredibly
> difficult to do, that is factored in to prioritisation, alongside the size
> of the audience a
În 21 martie 2017 20:24:49 EET, Dan Garry a scris:
>On 21 March 2017 at 18:02, Strainu wrote:
>
>> 2017-03-21 18:17 GMT+02:00 Dan Garry :
>> > On 21 March 2017 at 14:34, Gerard Meijssen
>
>> > wrote:
>> >>
>> >> Technical considerations are imho less relevant. What trumps it is
>> >> functional
Hi Chris,
Thanks for the comments. Would you and Edward be willing to meet with me
(and anyone else who might be interested, such as Lodewijk as well as
someone from WMF Communications) to discuss the current situation and
brainstorm ideas about how to improve it? We could set up a meeting
off-lis
On Tue, Mar 21, 2017 at 11:24 AM, Dan Garry wrote:
>
> Sadly, as is typical with this mailing list, we've now delved into a world
> of hypotheticals, idealisms, and misrepresentations. It would not be a
> productive use of time (and, indeed, donor money) for me to participate
> further in this th
On 21 March 2017 at 18:02, Strainu wrote:
> 2017-03-21 18:17 GMT+02:00 Dan Garry :
> > On 21 March 2017 at 14:34, Gerard Meijssen
> > wrote:
> >>
> >> Technical considerations are imho less relevant. What trumps it is
> >> functionality.
> >
> >
> > Technical considerations are very relevant if
2017-03-21 18:17 GMT+02:00 Dan Garry :
> On 21 March 2017 at 14:34, Gerard Meijssen
> wrote:
>>
>> Technical considerations are imho less relevant. What trumps it is
>> functionality.
>
>
> Technical considerations are very relevant if one is doing something
> technical, for example developing an
Hoi,
Apple maps do not provide the same maps (not as up to date) as OSM does for
a country like Haiti. That has nothing to do with "ignoring technical
difficulties" but has everything to do with the quality of the service
provided.
When you consider that work IS done on historic maps in an OSM con
As a programmer myself I understand that free vs non-free causes more work
for you. However you cannot ignore one of the foundations of the wikimedia
movement because it makes a little more work for you. I honestly don't
understand why you thought that Apple maps would be acceptable at all. You
hav
On 21 March 2017 at 14:32, John wrote:
> This reminds me of en wiki's non-free policy.
> https://en.wikipedia.org/wiki/Wikipedia:Non-free_content_criteria#1
> highlights the point fairly clearly Usage of non-free materials is often
> easier and higher quality than using the free equivalent . Howe
On 21 March 2017 at 14:34, Gerard Meijssen
wrote:
>
> Technical considerations are imho less relevant. What trumps it is
> functionality.
Technical considerations are very relevant if one is doing something
technical, for example developing an iOS app or a maps tile service.
> Our maps have to
Hoi,
Technical considerations are imho less relevant. What trumps it is
functionality. Our maps have to be good everywhere and as far as I know OSM
is superior in places where there is profit to be made from maps.
Current maps world wide and historical maps are what we need. How would you
use the
This reminds me of en wiki's non-free policy.
https://en.wikipedia.org/wiki/Wikipedia:Non-free_content_criteria#1
highlights the point fairly clearly Usage of non-free materials is often
easier and higher quality than using the free equivalent . However
Wikimedia's mission and goal's are to support
Hey Magnus,
There are a few other factors to consider in addition to those listed. For
example, development cost. Our maps tile service is not compatible with the
iOS app out of the box. This isn't surprising; Apple wants you to use
things like Apple Maps rather than your own solution. Android is,
14 matches
Mail list logo
