Building mobile apps is different from building web apps. Developers need to understand the unique demands that mobile apps place on APIs and considerations across different client and back-end platforms. Mobile apps also introduce new issues for security and scalability.
WARNING: These slides contain lots of code.
We Will Discuss »
Why building mobile apps is different
A roundup of different client libraries and frameworks
Considerations for selecting mobile back-end platforms
27. Ruby on Rails ActiveResource + ActiveRecord
Usage
class DogResource < ActiveResource::Base
self.site = http://api.apizoo.com/v1
end
class Dog < ActiveRecord::Base
# the before methods call DogResource methods
before_create :create_resource
before_update :update_resource
before_destroy :destroy_resource
end
44. THANK YOU
Contact us at:
@edanuff
ed@apigee.com
@sramji
sramji@apigee.com
@landlessness
brian@apigee.com
Notes de l'éditeur
Creative Commons Attribution-Share Alike 3.0 United States License
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
Android & iOS default response is a hash/dictionaryRuby on Rails
iOSFun factoid: the app store will reject your app if you don’t properly test your app using the reachability APIAndroidSearch around for Reachability - Connectivity Manager
If you provide and consume the api then auth is what u make it.Oauth 2 is a standard but not too heavyAbout 70% of the reason folks go to a special purpose built client library is auth, the second is object marshaling.The standard clients start to screw you over…Parameter signing are a nightmare for the app developer. RestKit
AndroidSUN JerseySpring MobileTradeoffs are around the App SizeForOauth: do the flow with the web browser but oauth 2 is a really pragmatic spec you can also pass a username and password. It will be up to the app. Client id and the client token. Get back an access token either in the header or as a param.
AndroidSUN JerseySpring MobileTradeoffs are around the App SizeForOauth: do the flow with the web browser but oauth 2 is a really pragmatic spec you can also pass a username and password. It will be up to the app. Client id and the client token. Get back an access token either in the header or as a param.