If it's sensitive, use SSL/HTTPS and get a username/password - but
maybe wait until you need it (ie, on first upload?) rather than it
being a road block when the app is first created.

On Wed, Dec 19, 2012 at 5:23 PM, Mittchel van Vliet <[email protected]> wrote:
> Thanks for your help Nic.
> Everything sounds pretty clear to me and the data is rather sensitive; it
> might be contact info.
>
>
>
> 2012/12/19 Nic Wise <[email protected]>
>>
>> SSL: it depends on the data. SSL is fairly cheap and easy to do, but
>> if the data is not sensitive at all, maybe you dont need to. It's easy
>> to change later tho (ie, before release, but after development)
>>
>> Authentication: A username/password is quite a good way (or rather,
>> email + password) if they need to get at it from other devices. If
>> it's just from the one device, you could use the UDID (or generate a
>> GUID) and use that, so you know which device it is. If they later need
>> to register to use the website (via the phone?), then associate a
>> username/password with that account.
>>
>> You could just ask for an email to identify them, and set a random
>> password until they set one (and they can't use the website until they
>> set one)
>>
>> It does depends on how secure the data needs to be. Instapaper just
>> went on a username (email) for ages, tho it now has passwords. But the
>> data in there is pretty generic....
>>
>>
>> On Tue, Dec 18, 2012 at 5:07 PM, Mittchel <[email protected]> wrote:
>> > Hello everyone,
>> >
>> > The title isnt really self explanatory, so I will explain my situation
>> > in
>> > detail.
>> > I'm in the inception fase of building an iOS application and I came
>> > across a
>> > little problem which hopefully some of you can help me out with.
>> >
>> > The situation:
>> > My App will export some data to the cloud via REST and JSON, I figured
>> > this
>> > is light weight so performance will be at best. The user should be able
>> > to
>> > access this 'data' on other devices and maybe even via the web, so I
>> > need
>> > some sort of authentication.
>> >
>> > Since I'm using REST with SSL; is it safe to send plain text
>> > username/password or should I encrypt it even though SSL takes care of
>> > this?
>> > Furthermore, I think it's annoying that someone has to login with
>> > username/password; do you guys see some sort of 'identification' type
>> > which
>> > would be more user friendly or is the username/password thing the best I
>> > can
>> > do?
>> >
>> > Hopefully it's clear enough, if not; let me know what I forgot!
>> >
>> > Regards,
>> > Mittchel
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> > http://monotouch.2284126.n4.nabble.com/Sort-of-Device-identification-tp4657871.html
>> > Sent from the MonoTouch mailing list archive at Nabble.com.
>> > _______________________________________________
>> > MonoTouch mailing list
>> > [email protected]
>> > http://lists.ximian.com/mailman/listinfo/monotouch
>>
>>
>>
>> --
>> Nic Wise
>> t.  +44 7788 592 806 | @fastchicken
>> b. http://www.fastchicken.co.nz/
>>
>> mobileAgent (for FreeAgent): get your accounts in your pocket.
>> http://goo.gl/IuBU
>> Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa
>> Earnest: Self-employed? Track your business expenses and income.
>> http://earnestapp.com
>> Nearest Bus: find when the next bus is coming to your stop.
>> http://goo.gl/Vcz1p
>> London Bike App: Find the nearest Boris Bike, and get riding!
>> http://goo.gl/Icp2
>
>



-- 
Nic Wise
t.  +44 7788 592 806 | @fastchicken
b. http://www.fastchicken.co.nz/

mobileAgent (for FreeAgent): get your accounts in your pocket.
http://goo.gl/IuBU
Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa
Earnest: Self-employed? Track your business expenses and income.
http://earnestapp.com
Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p
London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch

Reply via email to