Yeah, it is pretty ambiguous, but because of the encapsulation of the module, it should only call on subclasses of `PM::WebScreen` so I imagine a subclass would look like:

```ruby
class AboutScreen < PM::WebScreen
  title "About"

  def content
    # This can be a URL String, an NSURL, a string, 
    # or a file name that references a file in the resources directory
    "AboutView.html"
  end

  def load_started
    puts "Started Loading"
  end

  def load_finished
    puts "Finished Loading"
  end

  def load_failed(error)
    puts "Load Failed: #{error}"
  end

end
```

Though I'm open to changing it to be more descriptive/specific.