I've seen some murmurings about ODK Collect for iOS here and there on the
net, or on this list. It looks like some work might have been done in this
direction, but links to githubs/etc are broken. What happened with this
and what is the current state of art? How are people dealing with ODK-like
functionality in iOS, or using ODK xml to display forms there? If there
was an objective-c project underway, I might contribute. Just looking for
someone to bring me up to speed on this..!
I've seen some murmurings about ODK Collect for iOS here and there on the
net, or on this list. It looks like some work might have been done in this
direction, but links to githubs/etc are broken. What happened with this and
what is the current state of art? How are people dealing with ODK-like
functionality in iOS, or using ODK xml to display forms there? If there was
an objective-c project underway, I might contribute. Just looking for
someone to bring me up to speed on this..!
I know the iOS issue has been hashed and rehashed here and that there could
be two approaches, one building on the already started ocRosa project and
one that would take advantage of HTML5 (yet to be adopted). It seems like
progress on an iOS app is hampered by the amount of time the volunteer
developer(s) can throw at it and that advances could be made with the
injection of some funding to compensate/incentivize current developers or
hire more. So, my question is, approximately how much would it cost to make
an iOS app happen? I know my office (I work for the U.S. National Park
Service and FEMA) would be interested in chipping in to be able to extend
our existing ODK implementation across platforms. Given the number of
iOS-related posts here, I imagine that others would be willing to do the
same.
Anyone have any thoughts on this?
Thanks,
-Ed
···
On Monday, May 13, 2013 9:29:05 AM UTC-5, Yaw Anokwa wrote:
>
> Hi Wyler,
>
> There is no native iOS client that I know of. Plenty of people ask
> about ODK on iOS, so hopefully someone in the community will build
> one.
>
> Until then, the best way to get ODK running on iOS today is to use
> Enketo (http://www.enketo.org) in the Safari browser.
>
> Yaw
> --
> Need ODK help? Go to http://nafundi.com for custom features, form
> design, implementation support, and user training for ODK.
>
> On Thu, May 9, 2013 at 12:05 PM, Wyler Yerrachione <foundatio...@gmail.com > wrote:
> > Hi All,
> >
> > I've seen some murmurings about ODK Collect for iOS here and there on
> the
> > net, or on this list. It looks like some work might have been done in
> this
> > direction, but links to githubs/etc are broken. What happened with this
> and
> > what is the current state of art? How are people dealing with ODK-like
> > functionality in iOS, or using ODK xml to display forms there? If there
> was
> > an objective-c project underway, I might contribute. Just looking for
> > someone to bring me up to speed on this..!
> >
> > w.
> >
> > --
> > --
> > Post: opend...@googlegroups.com
> > Unsubscribe: opendatakit...@googlegroups.com
> > Options: http://groups.google.com/group/opendatakit?hl=en
> >
> > ---
> > You received this message because you are subscribed to the Google
> Groups
> > "ODK Community" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to opendatakit...@googlegroups.com .
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
At SurveyCTO, we spend a lot of time working on our version of Collect,
which is a very modestly extended and optimized version of the core ODK
version. It seems like it should be simple, but, all told, it's actually a
pretty huge and complex project. Even if you could snap your fingers and
make a v1.0 iOS version come into being, maintaining and sustaining it
would be a seriously non-trivial task. And you'd be crazy to deploy a
survey that relied on an iOS version unless there was a sustained
commitment, by somebody, to support and maintain it.
My guess would be about $100,000 to develop, plus ongoing technical
commitment on top of that. I could be pretty far off, but I doubt my order
of magnitude is wrong. (It's certainly not a $10,000 job, nor is it a
$1,000,000 job.)
And my question is: what are the settings in which iOS is better? I love
Apple products and use them all myself, but they seem wholly unsuited to
fieldwork -- in terms of configurability, in terms of diversity, in terms
of cost, pretty much in terms of anything that I can think of. You're
right, though, that this comes up a lot, so I must be missing something.
I'm open to being wrong..!
Best,
Chris
···
On Wed, Dec 11, 2013 at 3:13 PM, Ed FitzGerald wrote:
I know the iOS issue has been hashed and rehashed here and that there
could be two approaches, one building on the already started ocRosa project
and one that would take advantage of HTML5 (yet to be adopted). It seems
like progress on an iOS app is hampered by the amount of time the volunteer
developer(s) can throw at it and that advances could be made with the
injection of some funding to compensate/incentivize current developers or
hire more. So, my question is, approximately how much would it cost to make
an iOS app happen? I know my office (I work for the U.S. National Park
Service and FEMA) would be interested in chipping in to be able to extend
our existing ODK implementation across platforms. Given the number of
iOS-related posts here, I imagine that others would be willing to do the
same.
Anyone have any thoughts on this?
Thanks,
-Ed
On Monday, May 13, 2013 9:29:05 AM UTC-5, Yaw Anokwa wrote:
Hi Wyler,
There is no native iOS client that I know of. Plenty of people ask
about ODK on iOS, so hopefully someone in the community will build
one.
Until then, the best way to get ODK running on iOS today is to use
Enketo (http://www.enketo.org) in the Safari browser.
Yaw
Need ODK help? Go to http://nafundi.com for custom features, form
design, implementation support, and user training for ODK.
I've seen some murmurings about ODK Collect for iOS here and there on
the
net, or on this list. It looks like some work might have been done in
this
direction, but links to githubs/etc are broken. What happened with
this and
what is the current state of art? How are people dealing with ODK-like
functionality in iOS, or using ODK xml to display forms there? If
there was
an objective-c project underway, I might contribute. Just looking for
someone to bring me up to speed on this..!
At SurveyCTO, we spend a lot of time working on our version of Collect,
which is a very modestly extended and optimized version of the core ODK
version. It seems like it should be simple, but, all told, it's actually a
pretty huge and complex project. Even if you could snap your fingers and
make a v1.0 iOS version come into being, maintaining and sustaining it would
be a seriously non-trivial task. And you'd be crazy to deploy a survey that
relied on an iOS version unless there was a sustained commitment, by
somebody, to support and maintain it.
My guess would be about $100,000 to develop, plus ongoing technical
commitment on top of that. I could be pretty far off, but I doubt my order
of magnitude is wrong. (It's certainly not a $10,000 job, nor is it a
$1,000,000 job.)
And my question is: what are the settings in which iOS is better? I love
Apple products and use them all myself, but they seem wholly unsuited to
fieldwork -- in terms of configurability, in terms of diversity, in terms of
cost, pretty much in terms of anything that I can think of. You're right,
though, that this comes up a lot, so I must be missing something. I'm open
to being wrong..!
Best,
Chris
On Wed, Dec 11, 2013 at 3:13 PM, Ed FitzGerald fitzed@gmail.com wrote:
I know the iOS issue has been hashed and rehashed here and that there
could be two approaches, one building on the already started ocRosa project
and one that would take advantage of HTML5 (yet to be adopted). It seems
like progress on an iOS app is hampered by the amount of time the volunteer
developer(s) can throw at it and that advances could be made with the
injection of some funding to compensate/incentivize current developers or
hire more. So, my question is, approximately how much would it cost to make
an iOS app happen? I know my office (I work for the U.S. National Park
Service and FEMA) would be interested in chipping in to be able to extend
our existing ODK implementation across platforms. Given the number of
iOS-related posts here, I imagine that others would be willing to do the
same.
Anyone have any thoughts on this?
Thanks,
-Ed
On Monday, May 13, 2013 9:29:05 AM UTC-5, Yaw Anokwa wrote:
Hi Wyler,
There is no native iOS client that I know of. Plenty of people ask
about ODK on iOS, so hopefully someone in the community will build
one.
Until then, the best way to get ODK running on iOS today is to use
Enketo (http://www.enketo.org) in the Safari browser.
Yaw
Need ODK help? Go to http://nafundi.com for custom features, form
design, implementation support, and user training for ODK.
I've seen some murmurings about ODK Collect for iOS here and there on
the
net, or on this list. It looks like some work might have been done in
this
direction, but links to githubs/etc are broken. What happened with
this and
what is the current state of art? How are people dealing with ODK-like
functionality in iOS, or using ODK xml to display forms there? If
there was
an objective-c project underway, I might contribute. Just looking for
someone to bring me up to speed on this..!
Actually if one is to rewrite both Collect and JavaRosa core for iOS,
basing on the pricing i have so far seen for related amounts of work, a
realistic estimate would be a figure not less than $200k
···
On Wed, Dec 11, 2013 at 11:38 PM, Yaw Anokwa wrote:
Ed,
Totally agreed with Chris on the estimate. A fully featured iOS
version of Collect is in the $100-200k range.
Collect looks simple, but it's on order of 50k lines of code (30k for
Collect, 20k for the Javarosa core).
Yaw
Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.
At SurveyCTO, we spend a lot of time working on our version of Collect,
which is a very modestly extended and optimized version of the core ODK
version. It seems like it should be simple, but, all told, it's actually
a
pretty huge and complex project. Even if you could snap your fingers and
make a v1.0 iOS version come into being, maintaining and sustaining it
would
be a seriously non-trivial task. And you'd be crazy to deploy a survey
that
relied on an iOS version unless there was a sustained commitment, by
somebody, to support and maintain it.
My guess would be about $100,000 to develop, plus ongoing technical
commitment on top of that. I could be pretty far off, but I doubt my
order
of magnitude is wrong. (It's certainly not a $10,000 job, nor is it a
$1,000,000 job.)
And my question is: what are the settings in which iOS is better? I love
Apple products and use them all myself, but they seem wholly unsuited to
fieldwork -- in terms of configurability, in terms of diversity, in
terms of
cost, pretty much in terms of anything that I can think of. You're right,
though, that this comes up a lot, so I must be missing something. I'm
open
to being wrong..!
Best,
Chris
On Wed, Dec 11, 2013 at 3:13 PM, Ed FitzGerald fitzed@gmail.com wrote:
I know the iOS issue has been hashed and rehashed here and that there
could be two approaches, one building on the already started ocRosa
project
and one that would take advantage of HTML5 (yet to be adopted). It seems
like progress on an iOS app is hampered by the amount of time the
volunteer
developer(s) can throw at it and that advances could be made with the
injection of some funding to compensate/incentivize current developers
or
hire more. So, my question is, approximately how much would it cost to
make
an iOS app happen? I know my office (I work for the U.S. National Park
Service and FEMA) would be interested in chipping in to be able to
extend
our existing ODK implementation across platforms. Given the number of
iOS-related posts here, I imagine that others would be willing to do the
same.
Anyone have any thoughts on this?
Thanks,
-Ed
On Monday, May 13, 2013 9:29:05 AM UTC-5, Yaw Anokwa wrote:
Hi Wyler,
There is no native iOS client that I know of. Plenty of people ask
about ODK on iOS, so hopefully someone in the community will build
one.
Until then, the best way to get ODK running on iOS today is to use
Enketo (http://www.enketo.org) in the Safari browser.
Yaw
Need ODK help? Go to http://nafundi.com for custom features, form
design, implementation support, and user training for ODK.
I've seen some murmurings about ODK Collect for iOS here and there on
the
net, or on this list. It looks like some work might have been done
in
this
direction, but links to githubs/etc are broken. What happened with
this and
what is the current state of art? How are people dealing with
ODK-like
functionality in iOS, or using ODK xml to display forms there? If
there was
an objective-c project underway, I might contribute. Just looking
for
someone to bring me up to speed on this..!
--
If we keep uppermost in our minds the unkind and unjust acts of others, we
shall find it impossible to love them as Christ has loved us; but if our
thoughts dwell upon the wondrous love and pity of Christ for us, the same
spirit will flow out to others.
Yikes! I was imagining this would cost more around the $50K mark. Thanks
for clarifying. Didn't realize how much work would be involved and forgot
about long-term maintenance.
Honestly, the only reason I'm interested in an iOS app is to allow more
people to use our version of ODK with the hardware they already have. For
enterprise level deployments where we control the hardware, the Galaxy Tabs
we use are totally sufficient (and cheaper than iPads).
Though, if anyone else with deeper pockets is listening, I'd still be
willing to chip in on development costs ($5,000 or so).
Thanks,
Ed
···
On Wed, Dec 11, 2013 at 2:49 PM, Daniel Kayiwa wrote:
Actually if one is to rewrite both Collect and JavaRosa core for iOS,
basing on the pricing i have so far seen for related amounts of work, a
realistic estimate would be a figure not less than $200k
At SurveyCTO, we spend a lot of time working on our version of Collect,
which is a very modestly extended and optimized version of the core ODK
version. It seems like it should be simple, but, all told, it's
actually a
pretty huge and complex project. Even if you could snap your fingers and
make a v1.0 iOS version come into being, maintaining and sustaining it
would
be a seriously non-trivial task. And you'd be crazy to deploy a survey
that
relied on an iOS version unless there was a sustained commitment, by
somebody, to support and maintain it.
My guess would be about $100,000 to develop, plus ongoing technical
commitment on top of that. I could be pretty far off, but I doubt my
order
of magnitude is wrong. (It's certainly not a $10,000 job, nor is it a
$1,000,000 job.)
And my question is: what are the settings in which iOS is better? I love
Apple products and use them all myself, but they seem wholly unsuited to
fieldwork -- in terms of configurability, in terms of diversity, in
terms of
cost, pretty much in terms of anything that I can think of. You're
right,
though, that this comes up a lot, so I must be missing something. I'm
open
to being wrong..!
Best,
Chris
On Wed, Dec 11, 2013 at 3:13 PM, Ed FitzGerald fitzed@gmail.com wrote:
I know the iOS issue has been hashed and rehashed here and that there
could be two approaches, one building on the already started ocRosa
project
and one that would take advantage of HTML5 (yet to be adopted). It
seems
like progress on an iOS app is hampered by the amount of time the
volunteer
developer(s) can throw at it and that advances could be made with the
injection of some funding to compensate/incentivize current developers
or
hire more. So, my question is, approximately how much would it cost to
make
an iOS app happen? I know my office (I work for the U.S. National Park
Service and FEMA) would be interested in chipping in to be able to
extend
our existing ODK implementation across platforms. Given the number of
iOS-related posts here, I imagine that others would be willing to do
the
same.
Anyone have any thoughts on this?
Thanks,
-Ed
On Monday, May 13, 2013 9:29:05 AM UTC-5, Yaw Anokwa wrote:
Hi Wyler,
There is no native iOS client that I know of. Plenty of people ask
about ODK on iOS, so hopefully someone in the community will build
one.
Until then, the best way to get ODK running on iOS today is to use
Enketo (http://www.enketo.org) in the Safari browser.
Yaw
Need ODK help? Go to http://nafundi.com for custom features, form
design, implementation support, and user training for ODK.
I've seen some murmurings about ODK Collect for iOS here and there
on
the
net, or on this list. It looks like some work might have been done
in
this
direction, but links to githubs/etc are broken. What happened with
this and
what is the current state of art? How are people dealing with
ODK-like
functionality in iOS, or using ODK xml to display forms there? If
there was
an objective-c project underway, I might contribute. Just looking
for
someone to bring me up to speed on this..!
--
If we keep uppermost in our minds the unkind and unjust acts of others, we
shall find it impossible to love them as Christ has loved us; but if our
thoughts dwell upon the wondrous love and pity of Christ for us, the same
spirit will flow out to others.
I'm not sure what your ODK Aggregate/Formhub/other currently looks like,
but Formhub does have pretty good ODK/iOS support through it's
browser-based forms called enketo. You just bookmark the survey, it works
offline, and draws on the same form you use in ODK Collect. It might be
worth looking into.
···
On Wednesday, December 11, 2013 6:32:56 PM UTC-5, Ed FitzGerald wrote:
>
> Yikes! I was imagining this would cost more around the $50K mark. Thanks
> for clarifying. Didn't realize how much work would be involved and forgot
> about long-term maintenance.
>
> Honestly, the only reason I'm interested in an iOS app is to allow more
> people to use our version of ODK with the hardware they already have. For
> enterprise level deployments where we control the hardware, the Galaxy Tabs
> we use are totally sufficient (and cheaper than iPads).
>
> Though, if anyone else with deeper pockets is listening, I'd still be
> willing to chip in on development costs ($5,000 or so).
>
> Thanks,
> Ed
>
>
> On Wed, Dec 11, 2013 at 2:49 PM, Daniel Kayiwa <kayiwa...@gmail.com wrote:
>
>> Actually if one is to rewrite both Collect and JavaRosa core for iOS,
>> basing on the pricing i have so far seen for related amounts of work, a
>> realistic estimate would be a figure not less than $200k
>>
>>
>> On Wed, Dec 11, 2013 at 11:38 PM, Yaw Anokwa <yan...@nafundi.com wrote:
>>
>>> Ed,
>>>
>>> Totally agreed with Chris on the estimate. A fully featured iOS
>>> version of Collect is in the $100-200k range.
>>>
>>> Collect looks simple, but it's on order of 50k lines of code (30k for
>>> Collect, 20k for the Javarosa core).
>>>
>>> Yaw
>>> --
>>> Need ODK services? http://nafundi.com provides form design, server
>>> setup, professional support, and software development for ODK.
>>>
>>> On Wed, Dec 11, 2013 at 10:24 PM, Christopher Robert <cro...@surveycto.com > wrote:
>>> > Ed,
>>> >
>>> > At SurveyCTO, we spend a lot of time working on our version of Collect,
>>> > which is a very modestly extended and optimized version of the core ODK
>>> > version. It seems like it should be simple, but, all told, it's
>>> actually a
>>> > pretty huge and complex project. Even if you could snap your fingers
>>> and
>>> > make a v1.0 iOS version come into being, maintaining and sustaining it
>>> would
>>> > be a seriously non-trivial task. And you'd be crazy to deploy a survey
>>> that
>>> > relied on an iOS version unless there was a sustained commitment, by
>>> > somebody, to support and maintain it.
>>> >
>>> > My guess would be about $100,000 to develop, plus ongoing technical
>>> > commitment on top of that. I could be pretty far off, but I doubt my
>>> order
>>> > of magnitude is wrong. (It's certainly not a $10,000 job, nor is it a
>>> > $1,000,000 job.)
>>> >
>>> > And my question is: what are the settings in which iOS is better? I
>>> love
>>> > Apple products and use them all myself, but they seem wholly unsuited
>>> to
>>> > fieldwork -- in terms of configurability, in terms of diversity, in
>>> terms of
>>> > cost, pretty much in terms of anything that I can think of. You're
>>> right,
>>> > though, that this comes up a lot, so I must be missing something. I'm
>>> open
>>> > to being wrong..!
>>> >
>>> > Best,
>>> >
>>> > Chris
>>> >
>>> >
>>> >
>>> > On Wed, Dec 11, 2013 at 3:13 PM, Ed FitzGerald <fit...@gmail.com> wrote:
>>> >>
>>> >> I know the iOS issue has been hashed and rehashed here and that there
>>> >> could be two approaches, one building on the already started ocRosa
>>> project
>>> >> and one that would take advantage of HTML5 (yet to be adopted). It
>>> seems
>>> >> like progress on an iOS app is hampered by the amount of time the
>>> volunteer
>>> >> developer(s) can throw at it and that advances could be made with the
>>> >> injection of some funding to compensate/incentivize current
>>> developers or
>>> >> hire more. So, my question is, approximately how much would it cost
>>> to make
>>> >> an iOS app happen? I know my office (I work for the U.S. National Park
>>> >> Service and FEMA) would be interested in chipping in to be able to
>>> extend
>>> >> our existing ODK implementation across platforms. Given the number of
>>> >> iOS-related posts here, I imagine that others would be willing to do
>>> the
>>> >> same.
>>> >>
>>> >> Anyone have any thoughts on this?
>>> >>
>>> >> Thanks,
>>> >> -Ed
>>> >>
>>> >>
>>> >> On Monday, May 13, 2013 9:29:05 AM UTC-5, Yaw Anokwa wrote:
>>> >>>
>>> >>> Hi Wyler,
>>> >>>
>>> >>> There is no native iOS client that I know of. Plenty of people ask
>>> >>> about ODK on iOS, so hopefully someone in the community will build
>>> >>> one.
>>> >>>
>>> >>> Until then, the best way to get ODK running on iOS today is to use
>>> >>> Enketo (http://www.enketo.org) in the Safari browser.
>>> >>>
>>> >>> Yaw
>>> >>> --
>>> >>> Need ODK help? Go to http://nafundi.com for custom features, form
>>> >>> design, implementation support, and user training for ODK.
>>> >>>
>>> >>> On Thu, May 9, 2013 at 12:05 PM, Wyler Yerrachione wrote:
>>> >>> > Hi All,
>>> >>> >
>>> >>> > I've seen some murmurings about ODK Collect for iOS here and there
>>> on
>>> >>> > the
>>> >>> > net, or on this list. It looks like some work might have been
>>> done in
>>> >>> > this
>>> >>> > direction, but links to githubs/etc are broken. What happened with
>>> >>> > this and
>>> >>> > what is the current state of art? How are people dealing with
>>> ODK-like
>>> >>> > functionality in iOS, or using ODK xml to display forms there? If
>>> >>> > there was
>>> >>> > an objective-c project underway, I might contribute. Just
>>> looking for
>>> >>> > someone to bring me up to speed on this..!
>>> >>> >
>>> >>> > w.
>>> >>> >
>>> >>> > --
>>> >>> > --
>>> >>> > Post: opend...@googlegroups.com
>>> >>> > Unsubscribe: opendatakit...@googlegroups.com
>>> >>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>> >>> >
>>> >>> > ---
>>> >>> > You received this message because you are subscribed to the Google
>>> >>> > Groups
>>> >>> > "ODK Community" group.
>>> >>> > To unsubscribe from this group and stop receiving emails from it,
>>> send
>>> >>> > an
>>> >>> > email to opendatakit...@googlegroups.com.
>>> >>> > For more options, visit https://groups.google.com/groups/opt_out.
>>> >>> >
>>> >>> >
>>> >>
>>> >> --
>>> >> --
>>> >> Post: opend...@googlegroups.com
>>> >> Unsubscribe: opendatakit...@googlegroups.com
>>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>>> >>
>>> >> ---
>>> >> You received this message because you are subscribed to the Google
>>> Groups
>>> >> "ODK Community" group.
>>> >> To unsubscribe from this group and stop receiving emails from it,
>>> send an
>>> >> email to opendatakit...@googlegroups.com .
>>> >> For more options, visit https://groups.google.com/groups/opt_out.
>>> >
>>> >
>>> > --
>>> > --
>>> > Post: opend...@googlegroups.com
>>> > Unsubscribe: opendatakit...@googlegroups.com
>>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>> >
>>> > ---
>>> > You received this message because you are subscribed to the Google
>>> Groups
>>> > "ODK Community" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> > email to opendatakit...@googlegroups.com .
>>> > For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>> --
>>> --
>>> Post: opend...@googlegroups.com
>>> Unsubscribe: opendatakit...@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "ODK Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to opendatakit...@googlegroups.com .
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> --
>> If we keep uppermost in our minds the unkind and unjust acts of others,
>> we shall find it impossible to love them as Christ has loved us; but if our
>> thoughts dwell upon the wondrous love and pity of Christ for us, the same
>> spirit will flow out to others.
>>
>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "ODK Community" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/opendatakit/EaZYOfLiZ_8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
The main feature you're missing out on in iOS is file inputs (until iOS 8 launches I hope, or until Apple starts allowing modern third party browsers). The table on this this page shows what I think are the main differences between ODK Collect and Enketo: https://enketo.org/openrosa.
Integration with ODK Aggregate for easier launching of forms should be coming soon if all goes well.
Forgot to suggest that if somebody requires a native iOS app, it will
probably be a lot more cost-efficient to instead develop a hybrid app
around enketo-core https://github.com/MartijnR/enketo-core. Several
groups are working on Android apps using this approach and the enketo-core
library was designed to provide just what is needed in order to do this
relatively easily leaving out the storage and communication layer (and thus
be able to keep the core up-to-date). I don't know much about iOS
development and whether their 'webview' follows modern web standards, but
if it does, it should not be very hard.
The advantage of this approach is that it doesn't require porting any
libraries to another language.
Cheers,
Martijn
···
On Thursday, December 12, 2013 7:30:11 PM UTC-7, mri...@gmail.com wrote:
>
> The main feature you're missing out on in iOS is file inputs (until iOS 8
> launches I hope, or until Apple starts allowing modern third party
> browsers). The table on this this page shows what I think are the main
> differences between ODK Collect and Enketo: https://enketo.org/openrosa.
>
> Integration with ODK Aggregate for easier launching of forms should be
> coming soon if all goes well.
>
I agree I think writing something around enketo would be probably be a
simpler (still far from trivial) approach as you won't have to replicate
javarosa in iOS. You still are able to author forms via xlsforms which is
one of the main advantages of xforms and submissions are odk compliant.
···
On Tuesday, December 17, 2013, Martijn van de Rijdt wrote:
Forgot to suggest that if somebody requires a native iOS app, it will
probably be a lot more cost-efficient to instead develop a hybrid app
around enketo-core https://github.com/MartijnR/enketo-core. Several
groups are working on Android apps using this approach and the enketo-core
library was designed to provide just what is needed in order to do this
relatively easily leaving out the storage and communication layer (and thus
be able to keep the core up-to-date). I don't know much about iOS
development and whether their 'webview' follows modern web standards, but
if it does, it should not be very hard.
The advantage of this approach is that it doesn't require porting any
libraries to another language.
Cheers,
Martijn
On Thursday, December 12, 2013 7:30:11 PM UTC-7, mri...@gmail.com<javascript:_e({}, 'cvml', 'mri...@gmail.com');>wrote:
The main feature you're missing out on in iOS is file inputs (until iOS 8
launches I hope, or until Apple starts allowing modern third party
browsers). The table on this this page shows what I think are the main
differences between ODK Collect and Enketo: https://enketo.org/openrosa.
Integration with ODK Aggregate for easier launching of forms should be
coming soon if all goes well.
You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com <javascript:_e({},
'cvml', 'opendatakit%2Bunsubscribe@googlegroups.com');>.
For more options, visit https://groups.google.com/groups/opt_out.