<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jake</title>
    <description/>
    <link>https://speakerdeck.com/jakesc</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/jakesc.rss"/>
    <lastBuildDate>2017-08-19 19:43:28 -0400</lastBuildDate>
    <item>
      <title>Networking and Persistence in Mobile Apps at Scale</title>
      <description>In this talk, I present the concept of a Model Store. This is a black-box system which maintains up-to-date model information for a dynamic app. It necessarily has networking, persistence, caching, and change notification capabilities. Through a series of slides and code examples, I illustrate how a well-designed codebase which includes one or more Model Stores can help developers attain a more well-reasoned and high-quality app.

</description>
      <media:content url="https://files.speakerdeck.com/presentations/67ef8f48dc9f413294ac26c5075786d4/preview_slide_0.jpg?8438861" type="image/jpeg" medium="image"/>
      <content:encoded>In this talk, I present the concept of a Model Store. This is a black-box system which maintains up-to-date model information for a dynamic app. It necessarily has networking, persistence, caching, and change notification capabilities. Through a series of slides and code examples, I illustrate how a well-designed codebase which includes one or more Model Stores can help developers attain a more well-reasoned and high-quality app.

</content:encoded>
      <pubDate>Wed, 16 Aug 2017 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/jakesc/networking-and-persistence-in-mobile-apps-at-scale</link>
      <guid>https://speakerdeck.com/jakesc/networking-and-persistence-in-mobile-apps-at-scale</guid>
    </item>
  </channel>
</rss>
