jodell

cd /Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources
grep -rohE 'xcode.lang.(\w*)' * | sort -u

codebutler

require 'httparty'
require 'json'

class Crashlytics
  include HTTParty
  base_uri 'https://api.crashlytics.com/api/v2'

  def session(email, password)
    self.class.post('/session.json',
      body: {email: email, password:password}.to_json,

kpgalligan

In general, avoid both. We should be using EventBus where possible, and passing arguments to Fractivities by reference rather than value.

However, saving state may need a more complex object, and you may need to pass data to Fractivities that can't be done with a reference.

In almost all cases, use Serializable. Be careful to write tests that actually attempt to serialize these objects. They won't actually be serialized until they need to be, which may not work if not tested.

Parcelable is "faster", but requires lots of explicit code that can be done incorrectly. Its also easy to forget updating the state manipulation methods when updating the objects themselves.

Comparison http://www.developerphil.com/parcelable-vs-serializable/