Jason,

It is awesome to see your enthusiasm.  My personal preference would be that we 
don’t work from the Apigee SDK.  That codebase is quite old and is definitely 
not the way we would architect it from scratch today.

Your idea of using RESTKit or AFNetworking is great.  As you select libraries 
to use, be mindful of their license compatibility with Apache.  RESTKit is 
Apache 2.0 already, so that is perfect.

The one question I have is unit / e2e testing.  That is something that is 
really missing in the current iOS SDK.  At one point, there was some work done 
with Lua to create a little framework for testing but it never really went 
anywhere.  Having guardrails in place from the start would make it a lot easier 
for other developers to get in and help work on the project.

#4, interoperation with Swift would be great.

What are you thinking about for handling JSON?

And of course, #5 would be icing on the cake :)

Rod


-- 
Rod Simpson
@rockerston
rodsimpson.com

On November 11, 2014 at 8:44:48 PM, Jason Kristian (jas...@apps4u.com.au) wrote:

HI All , Ive been looking at updating the iOS SDK which Ive got some good ideas 
for now there are a few options on what can be done for example with could 
build on the current SDK or fork apogee iOS sdks ,  
or we can start fresh and use a networking Library as it core like AFNetworking 
or RESTKit which its self is build on AFNetworking, IM happy to put the time 
into this and I can spare one staff member to help me but I don’t want t start  
as I think these core idea need to be decided by the Usergrid community. So I 
would love some feed back on how this should be designed Ive got some of my own 
Idea which I’ll share now.  

1- I think it should be package managed from the start. — CocoaPods  
2- I think it should take advantage of other libraries — why reinvent the 
wheel. there are plenty of good networking libraries at are well supported that 
will handle networking better .  
3- I should be easy to extend easy to add new collection model classes.  
4- I use Good objective-c convention to better interoperate with Swift.  
5- Be fun to use..  


Any thought would be good as I said I’m happy to put the work in I just need a 
path to follow. these Idea are just mine if this is not what every one whats 
then I’ll go along with whats decided .  




Jason Kristian | Director | Apps 4 U Pty Ltd.  
ph: +61 075699 8109  
mob: +61 0411 389 392  
e: Jason Kristian <mailto:jas...@apps4u.com.au>  



Reply via email to