<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 24/02/2014 14:51, Matthias
Wessendorf wrote:<br>
</div>
<blockquote
cite="mid:CAAg5f2S_ueOLwnFFyXARwuMVU7fezNj_WL839T7Sw+F_6B+RLw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div><br>
</div>
<div class="">
<div>
<div>
I like this approach. I'd rather be feature
driven than library driven. I think most yours
will be looking for what we can do for them
before looking at what native libs we provide.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>Not sure - I guess both;</div>
<div><br>
</div>
<div>If I need a sync client, I ususally have a client
platform already in mind, rather than just looking for
sync.</div>
<div><br>
</div>
<div>
I'd be looking for "iOS sync" </div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I can see what you mean, but the main reason you're on the website
is that you want to sync, you don't want "to iOS". :)<br>
<br>
In the full website mockup we have platform pictures just above the
use case list that I linked to, so that visitors will know that
these features apply to Android/iOS/JS/Cordova similar to the
current site (just more pretty :), it's not like we're completely
leaving the platforms out of the picture.<br>
<br>
Hylke<br>
<br>
<br>
</body>
</html>