<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tim Shedor on Medium]]></title>
        <description><![CDATA[Stories by Tim Shedor on Medium]]></description>
        <link>https://medium.com/@tshedor?source=rss-4b73fd734c4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oN5oELOpqIKS9Q7glfeemQ.jpeg</url>
            <title>Stories by Tim Shedor on Medium</title>
            <link>https://medium.com/@tshedor?source=rss-4b73fd734c4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:18:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tshedor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Brick Your App: Five Compelling Reasons and a Pizza Analogy to Make Your Data Accessible]]></title>
            <link>https://medium.com/flutter-community/brick-your-app-five-compelling-reasons-and-a-pizza-analogy-to-make-your-data-accessible-8d802e1e526e?source=rss-4b73fd734c4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d802e1e526e</guid>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[sqlite]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[firestore]]></category>
            <dc:creator><![CDATA[Tim Shedor]]></dc:creator>
            <pubDate>Mon, 02 Mar 2020 09:01:01 GMT</pubDate>
            <atom:updated>2020-03-02T09:01:01.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*79AdLz5BDqcpFKjE" /><figcaption>Photo by <a href="https://unsplash.com/@alexander_tsang?utm_source=medium&amp;utm_medium=referral">Alexander Tsang</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Wrangling remote data is an app is as necessary as it is challenging. Often, multiple data stores like an API and a local cache is required. Both sources need to be kept in sync, with translations layers for both and legion control statements that determine which source to use. Of course, this is just the data. At the end of the day, you still have to write your Dart or Flutter (Flart, if you will) app.</p><p>The data persistence layer of an application requires a lot of code, a lot of tears, and a lot of distraction. So we wrote <a href="https://github.com/greenbits/brick">Brick</a> to be the solid foundation for your app’s data.</p><h3>What <em>Exactly</em> is Brick?</h3><p>Think of a <a href="https://www.youtube.com/watch?v=2noLcro9iIw">pizza shop</a>. Every type of pizza is a <a href="https://github.com/greenbits/brick#models">model</a> — pepperoni, cheese, sausage. The customer (your Flutter application) orders a cheese pizza. The cashier enters that order into the restaurant’s ticketing system (in Brick, this is the <a href="https://github.com/greenbits/brick#repository">repository</a>). The cooks (<a href="https://github.com/greenbits/brick#providers">providers</a>) combine raw ingredients (data source, like an API or a Firebase backend) to return a complete model back to the customer.</p><ul><li>A <a href="https://github.com/greenbits/brick#models">model</a> is basic, app-specific data</li><li>A <a href="https://github.com/greenbits/brick#providers">provider</a> works with a remote source to send models converted into that source’s expected data (JSON, SQL, Firestore Maps, etc.) and to fetch and convert that source’s data into models</li><li>A <a href="https://github.com/greenbits/brick#repository">repository</a> fetches and sends models from provider(s) on behalf of your app</li></ul><p>Of course, pizza shops can get complex. There are many ways to buy a pizza — premade, frozen, by the slice. Each is made by a different provider, and it’s up to the repository to determine how to satisfy the order quickly or with the freshest ingredients. This is where Brick shines as the data logic layer by <a href="https://github.com/greenbits/brick/tree/master/packages/brick_offline_first#brick-offline-first">hydrating from a remote source and returning from a local source</a>.</p><p>Brick handles <em>all of this</em> behind the scenes. When writing your Flutter app, <strong>you only write models</strong>. Don’t worry about providers, repositories, or even serialization.</p><h3>1. Brick makes your data accessible offline and online</h3><p>When your app goes <a href="https://github.com/greenbits/brick/tree/master/packages/brick_offline_first">offline, don’t leave your users in the dark</a>. Brick <a href="https://github.com/greenbits/brick/tree/master/packages/brick_offline_first#offlinequeuehttpclient">caches requests</a> so that when connectivity returns, all the data generated by your users is submitted.</p><p>Of course, if your app requires eager loading, make sure that process completes before rendering the rest of the application. For example, if a user has not completed the sign up process on your remote source of truth, they never access a profile page.</p><h3>2. Brick focuses your data access to a single point</h3><p>Instead of including complex logic throughout your app (for example, does the query match in memory? if not, does the query exist in SQLite? if not, retrieve from REST), Brick <a href="https://www.youtube.com/watch?v=jm5i7e_BQq0">contains the logic</a> to munge all these sources together so that <strong>one request becomes one response</strong>. It also <a href="https://github.com/greenbits/brick#query">standardizes queries between all inputs</a> by relying on application data instead of source data:</p><pre>final usersWithBrownHats = await repository.get&lt;User&gt;(query:<br>  Query.where(‘hats’, Where.exact(‘color’, ‘brown’))<br>);</pre><h3>3. Brick does the heavy lifting</h3><p>SQLite migrations? <a href="https://github.com/greenbits/brick/tree/master/packages/brick_sqlite#intelligent-migrations">Automatically generated</a>. Translation between a REST API and a memory cache? <a href="https://github.com/greenbits/brick/tree/master/packages/brick_offline_first#brick-offline-first">Managed</a>. Brick even hydrates associations to provide an ActiveRecord-like experience:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4642e61047671b8cf9e21ce635b5e94e/href">https://medium.com/media/4642e61047671b8cf9e21ce635b5e94e/href</a></iframe><h3>4. Brick doesn’t require retrofitting</h3><p>Unlike other code generator libraries like <a href="https://pub.dev/packages/json_serializable">json_serializable</a>, Brick does not require adding code within existing model classes. To Brick an existing model, simply extend a Brick model and decorate:</p><pre>@ConnectOfflineFirst()<br>class User extends OfflineFirstWithRestModel {<br>  ...<br>}</pre><p>That one annotation <a href="https://github.com/greenbits/brick/tree/master/packages/brick_build#adapters-1">generates all the serializing and deserializing code</a> required to translate your model between your remote sources (<a href="https://github.com/greenbits/brick/blob/master/packages/brick_offline_first/example/lib/app/adapters/kitchen_sink_adapter.g.dart">seriously</a>).</p><h3>5. Brick is extensible</h3><p>Got a GraphQL, websockets, or protobuf server? While these haven’t been written yet (PRs are always open), Brick has <a href="https://github.com/greenbits/brick/tree/master/packages/brick_build">extensive documentation</a> about <a href="https://github.com/greenbits/brick/tree/master/packages/brick_build#creating-a-domain-builder">writing a provider</a> and moving data to and from it.</p><p>As of writing, Brick supports two domains: <a href="https://github.com/greenbits/brick/tree/master/packages/brick_offline_first">OfflineFirstWithRest</a> and <a href="https://github.com/jnhuynh/brick_cloud_firestore/tree/master/brick_cloud_firestore">OfflineFirstWithCloudFirestore</a>.</p><p><a href="https://github.com/greenbits/brick">Brick</a> is still in an alpha-ish release, but we’re stoked to release it to the community now and see where it grows. Please drop us a line <a href="https://github.com/greenbits/brick/issues">for bugs or feature requests</a>, or come by <a href="https://www.greenbits.com/">our offices</a> in Portland and we’ll grab a pizza.</p><p><a href="https://www.twitter.com/FlutterComm">JavaScript is not available.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d802e1e526e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-community/brick-your-app-five-compelling-reasons-and-a-pizza-analogy-to-make-your-data-accessible-8d802e1e526e">Brick Your App: Five Compelling Reasons and a Pizza Analogy to Make Your Data Accessible</a> was originally published in <a href="https://medium.com/flutter-community">Flutter Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Unsolicited Redesign of the English Language]]></title>
            <link>https://medium.com/@tshedor/an-unsolicited-redesign-of-the-english-language-9e057b4a1ea9?source=rss-4b73fd734c4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e057b4a1ea9</guid>
            <category><![CDATA[english-language]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Tim Shedor]]></dc:creator>
            <pubDate>Sat, 14 Nov 2015 23:24:29 GMT</pubDate>
            <atom:updated>2015-11-20T17:52:15.871Z</atom:updated>
            <content:encoded><![CDATA[<p>The English language is pretty great. I use it every day. But I think it could be better, so I gave it a contemporary look. In the words of one close friend, “Grammar means nothing,” so I focused on the aesthetics and usability.</p><h4><strong>First, punctuation.</strong></h4><p>Can this sentence stand on its own, or does it need a comma? Was the semicolon born of <a href="https://en.wikipedia.org/wiki/Semicolon">a typesetter’s wet dream</a>? What the hell is “~”? <a href="https://owl.english.purdue.edu/engagement/3/7/98/">Hyphens</a>, <a href="http://grammarist.com/grammar/en-dash/">en dashes</a>, or <a href="http://www.chicagomanualofstyle.org/qanda/data/faq/topics/HyphensEnDashesEmDashes/faq0002.html">em dashes</a> (<em>Oxford ladies: call me</em>)?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*G_HPMttfDftv9o_NM-MNmw.png" /><figcaption>Comma.</figcaption></figure><p>Commas are worthless, actually (<em>AP Style ladies: call me</em>). User experience is awful when <a href="http://www.amazon.com/Eats-Shoots-Leaves-Tolerance-Punctuation/dp/1592402038">it’s not clear</a> whether to use a comma for pacing prepositions or conjoining punctuation. Almost always comma use is quite simply an unnecessarily frivolous application.</p><h4><strong>Next pronunciation.</strong></h4><p>Say choir out loud. Now say it like it reads (<em>cho-ere</em>). This is how you lose users. Words should sound like they read so whenever two vowels are next to each other only the first matters. Though you could argue against pronunciation guidelines you’ll realize you’re rationalizing archaic specifications.</p><h4><strong>Spelling.</strong></h4><p>Weird rules (“I before E except after C”) exist to keep feisty copy editors employed. Then there’s Y which heinously bats for both teams. Sure it’s the 21st century and we’re tolerant to choice but to simplify the interface Y’s are replaced with E’s to keep everething straight.</p><h4><strong>Possession?</strong></h4><p>Thee don’t have a clue. Either <a href="http://www.its-not-its.info/">it’s</a> with an apostrophe or its definitive. No more apostrophes; the world is ours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*G_HPMttfDftv9o_NM-MNmw.png" /><figcaption>Apostrophe, inverted.</figcaption></figure><p>Contractions shouldnt go because thee keep things concise. <a href="http://thenextweb.com/apple/2013/08/13/my-ios-7-redesign-concept/">Unsolicited redesigns are all about minimalism</a>.</p><h4><strong>Linking verbs.</strong></h4><p>Linking verbs are onle used be people <a href="https://www.thrillist.com/lifestyle/nation/my-life-living-midwestern-nice">who like to be passive</a> and take a long time to get to their point too long in me opinion. We should be active. Evere sentence punches with force and gusto. Grammar sounds exciting!</p><h4><strong>Words that sound the same.</strong></h4><p>There their theere. Eour eoure. Two to too. But butt. Bam. There. Eour. To. But (I like big butts but to Ts equals to mane).</p><h4><strong>Prepositions.</strong></h4><p>Previousle this confused users. Sometimes thee arrived before the subject and sometimes thee announced fashionable lateness. The grammar parte starts on time and eouve been uninvited prepositions. Painting a prettier picture? <a href="http://bigreaders.myfastforum.org/archive/the-writing-of-charles-dickens-a-sample__o_t__t_416.html">Grab a brush Dickens</a>.</p><h4><strong>Conjunctions.</strong></h4><p>Dual thoughts birth the ampersand. Have an idea &amp; have an explanation. Discourage run-on sentences &amp; dont let users ruin there own experience.</p><p>This revised English language reads deliciousle &amp; I appreciate eour consideration.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e057b4a1ea9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Without Words]]></title>
            <link>https://medium.com/@tshedor/ux-without-words-2e4a603ff2b6?source=rss-4b73fd734c4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e4a603ff2b6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Tim Shedor]]></dc:creator>
            <pubDate>Sat, 14 Nov 2015 22:38:11 GMT</pubDate>
            <atom:updated>2015-11-15T17:38:11.673Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Words that were in such abundance that they lost all value” — Hector, 1.9</blockquote><h3>UX Without Words</h3><p>One month ago, my roommates and I launched <a href="https://itunes.apple.com/us/app/exchange-audio-adventure-tour/id1037549324?ls=1&amp;mt=8">our first app</a>. Our elevator pitch: a location-based story app. Users must physically go to locations dictated by the app to hear the next chapter.</p><p>The main narrative of <a href="http://theexchangeapp.com/">The Exchange</a> follows a transplant through a world where words have become currency. Payments are not brokered with cash; they occur through “Exchanges” — one-to-one conversations that participants exit with unchanged word counts.</p><p>We wanted the story to be totally immersive. We had the real-life component — visiting the scenes — and we needed an interface to match that. The main plot describes the printing press as a revolutionary machine. If we had words in the app, the world would be broken.</p><p>With the challenge apparent, we focused on our core goal first — explain the story. The constraint put experience before glitz, and in my opinion, for the better. <a href="https://twitter.com/benbrignell/status/640624975725088768">Hamburger button be damned</a>.</p><h3>Step 1: Minimize interaction.</h3><p>The well-worn rule of no screen is further than three clicks was gospel. If an explanation was<em> required</em>, we nixed the idea. There are always other trees to bark up.</p><p>In our message center (the audio narrative was supplemented by texts/location pins), we didn’t want to create a false impression of interaction. So we removed the text input and keyboard to ensure a read-only experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*onWyKGpv8L_XfG1N6flJpg.gif" /></figure><p>When interaction was required, we didn’t reinvent the wheel. Onboarding? Dot pagination with intuitive swipe. Audio controls? Hidden drawer denoted by Apple’s control center bar. By relying on a user’s past experiences, we saved their energy (and thinking power) for the story.</p><h3>Step 2: Utilize efficient iconography.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4p3i4i20cq52NxvNO2nInQ.png" /><figcaption>Icons by North Bryan</figcaption></figure><p>Icons have saturated the modern UI landscape, and for good reason. They occupy much less real estate than text, they’re universally understood, and they add a playfulness words can’t quickly achieve. In a strange way, icons make technology more approachable than familiar, natural language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LMcfvAUJvYZvopdeiZFONQ.png" /></figure><p>The icons became our primary (read: only) method of direct communication with the user. We were careful to use them sparingly, and again, to not reinvent the wheel.</p><h3>Step 3: Don’t go overboard.</h3><p>Of course, this post must conclude on an admission of defeat. The usability made sense to us (<em>classic</em>), but not to the first friends we showed it to. After rounds of “OK, how about now?”, we conceded to adding a tutorial that explained what the app was and what to expect from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sEzBWxsQtQH65JWLD-T07w.png" /><figcaption>Onboarding screens designed by <a href="http://slavetothedetails.com/">John Kellyn Resman</a></figcaption></figure><p>So, no. <a href="https://itunes.apple.com/us/app/exchange-audio-adventure-tour/id1037549324?ls=1&amp;mt=8">The app</a> is not <em>completely </em>word-free. But it’s understandable, and it drives the story. Which is exactly what it needs to do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e4a603ff2b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>