I've got a new client and we're currently scoping out the requirements for a new iPhone app project.
The iPhone app is going to have to talk to the client's web server. The client has quite a complex website and a login/registration system in place already.
What they don't have is any kind of API for the iPhone App to communicate with the server.
The app is going to need to enable login and new registration. Some of the data in the app will require authentication and some won't.
Client wants to start on the right foot with the API and has asked me for some good examples of existing well documented JSON APIs. And bizarrely enough I can't think of any! I've integrated my apps with plenty of APIs but none of them really stood out as great examples of best practices when sending/receiving data!
Any suggestions/thoughts on good example APIs and login protocols would be gratefully received!
> I've got a new client and we're currently scoping out the requirements for a new iPhone app project.
> The iPhone app is going to have to talk to the client's web server. The client has quite a complex website and a login/registration system in place already.
> What they don't have is any kind of API for the iPhone App to communicate with the server.
> The app is going to need to enable login and new registration. Some of the data in the app will require authentication and some won't.
> Client wants to start on the right foot with the API and has asked me for some good examples of existing well documented JSON APIs. And bizarrely enough I can't think of any! I've integrated my apps with plenty of APIs but none of them really stood out as great examples of best practices when sending/receiving data!
> Any suggestions/thoughts on good example APIs and login protocols would be gratefully received!
> Cheers
> Nick
> -- > You received this message because you are subscribed to the Google Groups "Brighton iPhone Creators" group.
> To post to this group, send email to brighton-iphone-creators@googlegroups.com.
> To unsubscribe from this group, send email to brighton-iphone-creators+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/brighton-iphone-creators?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Brighton iPhone Creators" group.
> To post to this group, send email to brighton-iphone-creators@googlegroups.com.
> To unsubscribe from this group, send email to brighton-iphone-creators+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/brighton-iphone-creators?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups "Brighton iPhone Creators" group.
>> To post to this group, send email to brighton-iphone-creators@googlegroups.com.
>> To unsubscribe from this group, send email to brighton-iphone-creators+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/brighton-iphone-creators?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Brighton iPhone Creators" group.
> To post to this group, send email to brighton-iphone-creators@googlegroups.com.
> To unsubscribe from this group, send email to brighton-iphone-creators+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/brighton-iphone-creators?hl=en.
>>> -- >>> You received this message because you are subscribed to the Google Groups "Brighton iPhone Creators" group.
>>> To post to this group, send email to brighton-iphone-creators@googlegroups.com.
>>> To unsubscribe from this group, send email to brighton-iphone-creators+unsubscribe@googlegroups.com.
>>> For more options, visit this group at http://groups.google.com/group/brighton-iphone-creators?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups "Brighton iPhone Creators" group.
>> To post to this group, send email to brighton-iphone-creators@googlegroups.com.
>> To unsubscribe from this group, send email to brighton-iphone-creators+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/brighton-iphone-creators?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Brighton iPhone Creators" group.
> To post to this group, send email to brighton-iphone-creators@googlegroups.com.
> To unsubscribe from this group, send email to brighton-iphone-creators+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/brighton-iphone-creators?hl=en.
I'd counter claim that there's no designated initializer for
uiviewcontroller, because apple found objectivec inconvenient at this point
;). Makes the rest of it kind of pointless IMHO - you vs apple, apple will
win.
As a quick hack, of course, they "fixed" the "don't specify filenames" part
when they made "nil" a valid filename. For me personally thats ugly but
bearable as a workaround.
(similarly, with coredata, I ignore apples very annoying source code
examples that do:
Since Xcode still doesn't support refactoring, this approach saves a lot of
maintenance bugs.)
Side note: anyone else find it funny that apple generates "initwithnibname"
methods for every VC in a Storyboard app - even though storyboards by
definition avoid that method entirely - and doesn't generate the method
they actually use? Much fun for Developers there :)
---
Some Mississippi's due to Apple's poor autocorrect
On 25 May 2012, at 10:11, Will Johnston <willjohns...@me.com> wrote:
-- You received this message because you are subscribed to the Google Groups
"Brighton iPhone Creators" group.
To post to this group, send email to
brighton-iphone-creators@googlegroups.com.
To unsubscribe from this group, send email to
brighton-iphone-creators+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/brighton-iphone-creators?hl=en.