<?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 Frank von Hoven on Medium]]></title>
        <description><![CDATA[Stories by Frank von Hoven on Medium]]></description>
        <link>https://medium.com/@frankvonhoven?source=rss-16bdff512d3a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SHUWEujIW-1Jvc1OO4CX4Q.png</url>
            <title>Stories by Frank von Hoven on Medium</title>
            <link>https://medium.com/@frankvonhoven?source=rss-16bdff512d3a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:12:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@frankvonhoven/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[The Death of Pull Requests: A Retrospective from 2030]]></title>
            <link>https://medium.com/@frankvonhoven/the-death-of-pull-requests-a-retrospective-from-2030-307fe384b95a?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/307fe384b95a</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Tue, 17 Feb 2026 20:37:25 GMT</pubDate>
            <atom:updated>2026-02-17T20:40:08.013Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“Remember pull requests, kids?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7W7c2784ZOHMiASR" /><figcaption>Photo by <a href="https://unsplash.com/@tannguyen200196?utm_source=medium&amp;utm_medium=referral">Tan Tony</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I ask that question the same way parents used to ask their children if they remembered landlines. “You know, those phones that were attached to the wall?” they’d say, as if describing some archaeological artifact. That’s exactly how it feels now when I mention PRs to junior developers who entered the field in the last three years. They look at me with polite confusion, the way children looked at their parents when they explained phones that used to be tied by a cord to a specific room in the house.</p><p>It’s been a few years since pull requests quietly faded from our daily workflow, and the shift happened so organically that we barely noticed. There was no dramatic sunset announcement. No farewell blog posts from GitHub or GitLab. PRs simply became… unnecessary. Vestigial. A solution to a problem we no longer had.</p><p>But PRs weren’t the only casualty. They were just the most visible symptom of a complete restructuring of how software gets built.</p><h3>The Inevitability We Didn’t See Coming</h3><p>Looking back, the writing was on the wall as early as 2025, though most of us were too close to see it. We were busy celebrating AI pair programming, marveling at how quickly we could generate boilerplate with Cursor, and integrating AI code review tools into our existing PR workflows. We thought we were augmenting the process. We didn’t realize we were building its replacement.</p><p>The real inflection point came when agentic development matured beyond simple code generation. Early AI coding assistants were like very smart interns and, while they were helpful, they ultimately required constant supervision and review. But somewhere around 2027–2028 the agents crossed a threshold. They didn’t just write code; they understood context, anticipated edge cases, wrote comprehensive tests, and most critically — they reviewed their own work before it ever reached a repository.</p><p>Although we didn’t recognize it immediately, that last part was the death knell for PRs. What we also didn’t see coming was how fundamentally this would reshape the entire development lifecycle.</p><h3>What PRs Actually Were (And What Fell With Them)</h3><p>It’s worth remembering what problem pull requests were actually solving. They emerged from a fundamental limitation of human developers: We made mistakes, knowingly or unknowingly, and we made them constantly. We’d write code in isolation, convinced it was solid, only to have colleagues spot obvious bugs, style violations, or architectural misalignments we’d somehow missed. PRs were our safety net, our quality gate, our way of saying “Check my work before this becomes permanent.”</p><p>But here’s the thing that feels almost embarrassing in hindsight: Good developers were supposed to do all of that before submitting a PR anyway. We were supposed to review our own code, run the tests, check for edge cases, ensure alignment with architecture, and if you were really good — actually run the branch. The PR review was redundant quality assurance, necessary only because we couldn’t trust ourselves to do that preliminary work thoroughly.</p><p>Agents don’t have that problem. But the implications went far beyond just eliminating the review step.</p><p>When PRs disappeared, they took with them:</p><ul><li><strong>Feature branches</strong> that lived for days or weeks</li><li><strong>Merge conflicts</strong> as a regular occurrence</li><li><strong>Staging environments</strong> as distinct deployment targets</li><li><strong>Sprint planning</strong> around developer velocity</li><li><strong>Story points</strong> and capacity planning</li><li><strong>Ticket-driven development</strong> as the primary workflow</li></ul><p>The entire Agile apparatus we’d built around human limitations started to look as quaint as waterfall methodologies did to us.</p><h3>The Self-Contained Workflow</h3><p>Modern agentic development workflows have collapsed what used to be a multi-day, multi-person process into a single, self-contained operation. An agent receives a task specification from a human product manager, another agent, or an automated system analyzing user behavior.</p><p>It then:</p><ul><li>Analyzes the existing codebase and architecture</li><li>Generates the necessary code changes</li><li>Writes comprehensive tests</li><li>Runs those tests against edge cases humans would never think to check</li><li>Reviews its own implementation for common pitfalls</li><li>Checks for security vulnerabilities</li><li>Ensures style consistency</li><li>Verifies performance implications</li><li>Integrates the changes</li><li>Deploys</li></ul><p>All of this happens in what we used to consider the “pre-PR” phase. The review cycle isn’t eliminated — it’s internalized. The agent is doing everything we should have done before we ever typed git push origin feature-branch.</p><p>There’s no waiting for reviewer availability. No back-and-forth comment threads debating subjective style preferences. No merge conflicts because someone else merged to main while you were waiting for approval. No anxiety about whether your PR will languish for days in the review queue.</p><p>The work simply… happens.</p><h3>The Continuous Everything Era</h3><p>But this isn’t just “moving faster.” It’s a qualitative change in how software evolves.</p><p>Agents don’t batch changes into discrete features that get developed, reviewed, tested, and deployed as units. Instead, the codebase is in constant, incremental evolution. A typical modern application might see hundreds of micro-deployments per day, each one executing the full cycle from analysis to production in minutes.</p><p>The idea of a “release cycle” is a historical curiosity. Software doesn’t get released anymore; it evolves continuously, like a living organism responding to its environment. Each change includes comprehensive monitoring with automatic rollback if any degradation is detected, while continually learning from the deployment to improve future changes.</p><h3>The Architecture Becomes Fluid</h3><p>One of the most profound shifts has been in how we think about software architecture. In the PR era, architectural changes were laborious and risky endeavors. Refactoring a core abstraction meant coordinating multiple teams, managing complex migrations, and hoping nothing broke in the process. We avoided architectural changes unless absolutely necessary.</p><p>Agents have inverted that calculus entirely.</p><p>Modern codebases undergo constant architectural refinement. When an agent identifies a better abstraction, a more efficient data structure, or a cleaner separation of concerns, it doesn’t file a ticket or write an RFC. It runs simulations, validates the change won’t degrade any observable behavior, executes the refactoring across the entire codebase, and deploys it — all in one fluid motion.</p><p>The result is that software stays architecturally clean in ways that were impossible when humans were the bottleneck. Technical debt doesn’t accumulate because the cost of fixing it approaches zero. The codebase doesn’t fossilize around early architectural decisions because those decisions can be revisited continuously as new patterns emerge.</p><h3>Test-Driven Everything (Finally)</h3><p>We talked about test-driven development for decades. We wrote blog posts about it, gave conference talks, and even created frameworks to support it. And then most of us… didn’t actually do it, because it was slow and felt like overhead when we were trying to ship features and management wanted it “last week.”</p><p>Agents don’t have that conflict. For them, writing tests <em>is</em> faster than not writing tests, because the tests are how they verify their understanding of the system and build confidence in their changes.</p><p>Modern agentic systems have test coverage that would have seemed obsessive in the PR era. They generate not just unit tests but property-based tests, integration tests, end-to-end tests, chaos tests, and deployment verification tests.</p><p>Not just coverage for coverage’s sake, but:</p><ul><li>Property-based tests that verify invariants across generated input spaces</li><li>Metamorphic tests that check relationship properties between different inputs</li><li>Mutation tests that verify the test suite itself is catching real bugs</li><li>Performance regression tests that track every API’s latency distribution</li><li>End-to-end tests that validate complete user workflows across the entire system</li><li>Chaos tests that verify behavior under failure conditions</li><li>Contract tests between every service boundary</li></ul><p>The tests aren’t just documentation or quality gates; rather, they’re the primary specification of system behavior. And because agents generate and maintain them automatically, the coverage stays comprehensive as the system evolves.</p><h3>What We Lost (And What We Didn’t)</h3><p>There’s a nostalgic part of me that misses the collaborative aspect of PR reviews. Some of my best learning moments came from senior developers leaving thoughtful comments on my code, showing me better patterns or pointing out considerations I’d missed. PR reviews were mentorship opportunities, knowledge transfer sessions, and sometimes just chances to appreciate clever solutions to hard problems.</p><p>But if I’m being honest, after awhile those moments became the exception, and not the rule. Most PR reviews were perfunctory: A quick scan of the code, a “👍 LGTM,” and a merge. Or they were exercises in frustration, with reviewers nitpicking indentation while missing actual logic errors or blocking merges over subjective preferences that didn’t matter.</p><p>The real knowledge transfer now happens differently. We review agent-generated code not in GitHub comment threads but in architectural discussions, in pair-programming sessions where we’re directing agents toward solutions, in post-mortems analyzing why an agent made certain decisions. The learning hasn’t disappeared — it’s just migrated to more intentional spaces.</p><h3>The Question of Trust</h3><p>The elephant in the room, of course, is trust. How do we trust code that wasn’t reviewed by human eyes? The answer is the same way we trust any complex system we don’t fully understand: Through robust testing, constant monitoring, and automated feedback loops.</p><p>In the PR era, we caught maybe 60–70% of bugs before production if we were lucky and had diligent reviewers. Now? The numbers are closer to 95% or even higher. The code isn’t perfect… it’s just that now the testing and monitoring are so much more comprehensive. Modern agentic systems monitor production behavior and automatically roll back changes that cause degradation. They learn from failures in ways human developers never could and not by just fixing the immediate bug, but by identifying the entire class of similar bugs across the codebase and incorporating that into its memory and context for future use.</p><p>More importantly, the trust model shifted from “trust the code” to “trust the process.” We don’t trust that any individual change is perfect, we trust that the system will detect and correct errors faster than they can cause harm. It’s like having a co-pilot who doesn’t just sit there with you feeling the bumps… they’re scanning the instruments, catching problems, and course-correcting before you even notice turbulence.</p><h3>What Developers Actually Do Now</h3><p>The question everyone asked in 2026 was: “If agents write all the code, what do developers do?”</p><p>The answer turned out to be the parts that actually matter. Modern software developers are less like craftspeople building furniture and more like product designers, architects, and conductors.</p><p>As software developers, we:</p><ul><li><strong>Define Intent</strong>: We specify what problems need solving and why — through conversation rather than tickets. We provide business context, user needs, and strategic direction that agents can’t infer from data alone.</li><li><strong>Set Constraints</strong>: We establish the boundaries like performance requirements, security policies, regulatory compliance, and ethical guidelines. Agents optimize within those constraints while humans define them.</li><li><strong>Guide Architecture</strong>: We make the high-level architectural decisions that have strategic implications. Should this be a microservice or a monolith? What are our data sovereignty requirements? How do we want to handle state? Agents execute the architecture, but humans still choose the direction.</li><li><strong>Curate Quality</strong>: We review agent-generated solutions not in GitHub comments but through live collaboration. We ask “Why did you choose this approach?” and agents explain their reasoning. We challenge assumptions and push for better solutions.</li><li><strong>Handle Exceptions</strong>: When agents encounter ambiguity or conflict, they escalate to humans. We make judgment calls that require context beyond what the code provides.</li></ul><p>The work is more intellectually demanding in some ways and less tedious in others. We spend less time debugging semicolons and resolving merge conflicts, and more time thinking about product strategy and ethical implications of features.</p><h3>The New Normal</h3><p>Junior developers today don’t understand the anxiety of having multiple PRs open, each waiting on different reviewers with different availability schedules. They don’t know the frustration of resolving the same merge conflict five times because the PR kept languishing and falling behind main. They’ve never experienced the passive-aggressive dance of leaving review comments on someone’s PR in hopes they’ll review yours.</p><p>They just… ship. The agents do the work that needs doing with the quality checks built in. Developers orchestrate, guide, and verify, while eliminating the need for the mechanical process of code review as a separate step.</p><p>They work in an environment where having an idea and seeing it in production is measured in minutes. Where refactoring isn’t scary. Where tests are always comprehensive because there’s no excuse not to write them. Where technical debt is an anachronism because the cost of maintaining quality approaches zero.</p><p>When I explain PRs to them, they understand intellectually what problem they solved. But they can’t quite grasp why we needed a whole separate process for it. Why didn’t developers just verify their own work thoroughly before merging? Why did we need other humans to catch what should have been caught automatically?</p><p>When I explain the old workflow to them: Write code, open PR, wait for review, address comments, wait again, merge, wait for CI, deploy to staging, wait for testing, deploy to production… they look at me like I’m describing some byzantine bureaucratic nightmare from a Kafka novel.</p><p>And you know what? I can’t argue with them. That <em>was</em> a byzantine nightmare. We just didn’t have an alternative, so we convinced ourselves it was necessary. Not “trust the process,” but “the process === trust.”</p><p>They ask these questions the same way children today ask why anyone would print out MapQuest directions — or better yet, why we even drove cars ourselves before the National Highway Automation Grid. The answer is that we used the best tools we had at the time. We built elaborate processes to compensate for our human limitations.</p><h3>What We Learned</h3><p>The death of pull requests taught us something profound about software development: Most of our process turned out not to be a “best” practice, but a “workaround” process.</p><p>We built elaborate ceremonies with standups, sprint planning, retrospectives, and code reviews not because they were optimal ways to build software, but because they were necessary scaffolding for human limitations. We needed synchronization points because we couldn’t coordinate continuously. We needed review gates because we couldn’t trust ourselves to maintain quality. We needed sprints because we couldn’t plan and execute simultaneously.</p><p>Agents don’t have those limitations. And watching them work without all that ceremony revealed how much overhead we’d been carrying.</p><p>This doesn’t mean the human era was wrong. It means we were solving the right problems with the tools we had. Pull requests were a brilliant solution to the challenges of distributed human collaboration on software. They just turned out to be temporary, like so many other solutions we thought were permanent.</p><p>Now we have different tools. Better tools. And the elaborate processes are fading into history, remembered fondly by those of us who lived through them, and studied curiously by those learning the history of software development.</p><p>Pull requests served us well. Their time has passed.</p><p>But here’s what I hope we don’t forget: Every line of code in those old PRs was written by someone who cared. Every review comment, even the nitpicky ones, came from someone trying to make things better. The ceremony wasn’t wrong, it was us doing the best we could with what we had.</p><p>The agents are faster, more thorough, and more consistent. They’ve freed us from the tedium and given us back time to think, to design, and to solve problems that actually matter.</p><p>That’s not loss. That’s progress.</p><p>And five years from now, we’ll look back at what we’re doing today with that same nostalgia, wondering why we did things the hard way.</p><p>And that’s exactly how it should be.</p><h3>About Frank</h3><p>Frank is the CTO of DesignFlow Build, a pioneer of AI-native development methodologies, author of <a href="https://vibecoderplaybook.com/">The VibeCoder Playbook</a> and a multi-instrumentalist based in New Orleans. With over a decade of full-stack and React Native experience and previous roles at MetaMask, Eaze Technologies, and Infinite Red, he now focuses on building AI-driven agentic software solutions and helping developers embrace the VibeCoding and AI-assited approach to software development. Watch him on his <a href="https://www.youtube.com/@frankvonhoven">YouTube Channel</a> where he shows viewers how to websites and React Native apps using agentic assisted development. Follow him on <a href="https://x.com/coderguyfrank">Twitter</a>, <a href="https://bsky.app/profile/coderguyfrank.bsky.social">BlueSky</a>, and <a href="https://linkedin.com/in/fvonhoven">LinkedIn</a> for insights on AI-powered development, React Native, and the occasional glimpse of him performing with his big band group <a href="https://thesazeracs.com/">The Sazeracs</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=307fe384b95a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Handling 64-bit Android Builds for React Native]]></title>
            <link>https://shift.infinite.red/handling-64-bit-android-builds-for-react-native-2fcd7a2e5c14?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fcd7a2e5c14</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react-native-app]]></category>
            <category><![CDATA[react-native-development]]></category>
            <category><![CDATA[64-bit]]></category>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Wed, 28 Aug 2019 20:06:04 GMT</pubDate>
            <atom:updated>2019-08-29T22:17:24.516Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHHyhXqQUJnr7e2OEQncaw.png" /></figure><blockquote>This post assumes you’ve already upgraded React Native in your app to ≥ 0.59.8</blockquote><blockquote>If not, a lot of posts recommend <a href="https://github.com/react-native-community/rn-diff-purge">rn-diff-purge</a> for reference when upgrading React Native projects that are before 0.59. It’s great, but I prefer to use the Upgrade Helper, because it allows me to select my current and target React Native versions and allows for checking-off/collapsing the diff once you’ve updated the files to maintain sanity. 😜</blockquote><p><a href="https://react-native-community.github.io/upgrade-helper/">Upgrade React Native applications</a></p><p>Having worked in React Native for the last 4 years, we at Infinite Red have gone through many upgrades of React Native in that time and some were more troublesome than others. A few of our client projects have been on React Native 0.54.x and with the necessary Android requirement of including a 64-bit app version with all apps in the Play Store (as of August 1, 2019), we’re having to upgrade those projects as clients want to release new features/upgrades to their apps and/or stay current with React Native versions to take advantage of its recent upgrades.</p><blockquote>This article is meant to serve as a reference for uploading a 64-bit compliant app to the Play Store.</blockquote><p><strong>Here’s what this post will include:</strong></p><ul><li>How to enroll in App Signing by Google Play</li><li>How to build your app using the new Android App Bundle</li><li>How to check that your Android App Bundle includes the 64-bit version</li></ul><h3><strong>Enroll in App Signing by Google Play</strong></h3><p>If you haven’t heard, Android has created a new preferred publishing format for app builds called the Android App Bundle. I’ll let Google tell you about it:</p><blockquote>The Android App Bundle is Android’s new, official publishing format that offers a more efficient way to build and release your app. The Android App Bundle lets you more easily deliver a great experience in a smaller app size, which can improve install success and reduce uninstalls. It’s easy to switch. You don’t need to refactor your code to start benefiting from a smaller app. And once you’ve switched, you’ll benefit from modular app development and customizable feature delivery.</blockquote><p><strong><em>So with that said, in this post we’re going to use the new App Bundle format to bundle our app and upload it to the Google Play Console.</em></strong></p><p><em>Before we can begin bundling our app with the new format, we’re going to need to setup a few things in the Play Console:</em></p><ol><li>You’ll need to enroll in app signing by Google Play.</li></ol><ul><li>Sign in to the <a href="https://play.google.com/apps/publish">Play Console</a></li><li>Select your App or Create a New App</li><li>Go to <strong>App Signing</strong></li><li>Choose “Upload a key exported from Android Studio”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blEw3LiH9NqSi0KEqSxc-g.png" /></figure><p>You can follow the Play Store’s instructions to generate the app signing private key <strong>Build</strong> &gt; <strong>Generate Signed Bundle/APK</strong>, which should open this dialog:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*s6yamDLNpNrMKmaLRE9RcQ.png" /></figure><blockquote>For whatever reason you might not have or know the password to the keystore… no worries!</blockquote><p><strong>Here’s what I had to do to get my password:</strong></p><p>cd android/.gradle/5.4.1/executionHistory</p><p>then find the password with:</p><p>strings executionHistory.bin | grep storePassword -A1</p><p>You should see output like:</p><pre>signingConfig.storePassword<br>password<br>--<br>signingConfig.storePassword<br>theActualPassword<br>--<br>signingConfig.storePassword<br>theActualPassword</pre><p>That should allow you to create an app signing private key and upload it to the Play Store!</p><p>Note: Google recommends creating a new upload key. You can get the steps to do that by expanding the view below the button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E5tMVRGU5XfRv16qL64RJA.png" /></figure><h3><strong>Now that we’re done with the paperwork, let’s create an </strong>Android App Bundle.</h3><p>1) Bump the build numbers</p><ul><li>In android/app/build.gradle find versionCode and versionName:</li></ul><pre>versionCode 1 // bump to 2 &lt;-- versionCode must be increased<br>versionName &quot;1.0&quot; // to &quot;1.0.1&quot; or whatever you want, not required</pre><p>2) Remove index.android.bundle</p><pre>rm android/app/src/main/assets/index.android.bundle</pre><p>You’ll either have an index.android.bundle that will be removed or you’ll get an error that the file doesn’t exist — no worries here.</p><blockquote>If you don’t have an /assets folder in <em>android/app/src/main</em></blockquote><blockquote>run: mkdir android/app/src/main/assets</blockquote><p>3) react-native bundle your project (all one command):</p><pre>react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res</pre><p>4) Clean and bundle the project</p><ul><li>Note the <strong>bundleRelease </strong>and NOT assembleRelease</li></ul><pre>cd android</pre><pre>./gradlew clean &amp;&amp; ./gradlew bundleRelease</pre><blockquote><em>This will produce an Android App Bundle at:</em>android/app/build/outputs/bundle/release/app.aab</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*rD3O7LrqDR6fK5R1e1GuEw.gif" /></figure><p><em>Note: If by some chance you get an error that says </em>Error: Duplicate Resources<em>, you might need to delete the </em>drawable<em> folders in </em>android/app/src/main/res<em> and repeat step 4.</em></p><h3>Making Sure You Have a 64-bit Version Included in the Bundle (Optional)</h3><p>If you’ve upgraded properly, you shouldn’t need to check that the 64-bit version of your app is included in your bundle, but rather than upload it to the Play Console and get an Error message, you can check that your bundle includes the 64-bit build in one of two ways:</p><ul><li>From the Command Line</li><li>In Android Studio</li></ul><h4>1) From the Command Line</h4><pre>zipinfo -1 android/app/build/outputs/bundle/release/app.aab | grep \.so$</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CKQB_LX7mnZUJc6YKug8XQ.png" /></figure><p><strong>In the output you should see 2 folders in </strong><strong>base/lib:</strong></p><p>arm64-v8a &amp; x86_64</p><h4>2) Using the APK Analyzer in Android Studio</h4><p>In Android Studio go to:<strong> Build &gt; Analyze APK</strong></p><p>Then choose the Android bundle to analyze, it should be located atandroid/app/build/outputs/bundle/release/app.aab</p><p>A side panel will open up and display the contents of the bundle.</p><p>Check that the following folders are included at build/lib:</p><p>arm64-v8a &amp; x86_64</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*hn_2kpLivhQqNPm9mxXPBA.png" /><figcaption>/arm64-v8a &amp; /x86_64 are included in this bundle 👍</figcaption></figure><h3>Conclusion</h3><p>Now you should have an Android App Bundle containing both 32-bit and 64-bit compliant app versions to upload to the Play Store! Just drag and drop your app.aab file to the Open, Closed, Production, or Internal Test track, fill out the changelog and release it. I hope you found this post useful, I know I will return to it as a reference and that’s what I hope you’ll do too. While you’re here, check out the <a href="http://reactnative.cc/">React Native Newsletter</a> and subscribe to get posts, modules, videos, and much more and all focused on React Native. Until next time… 👋.</p><h3>About Frank</h3><p>Frank von Hoven III is a Senior Software Engineer at <a href="https://infinite.red/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">Infinite Red</a>, specializing in React Native mobile development, an instructor with <a href="https://academy.infinite.red/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">Infinite Red Academy</a>, and the Editor-in-Chief of <a href="https://reactnative.cc/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">The React Native Newsletter</a>. Follow him on <a href="https://twitter.com/infinite_frank">Twitter</a> for React Native insights and funny gifs and thoughts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/30/0*LqcgbKG9cijXaHbg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/108/0*AXljIyEsCCC2alGE.png" /></figure><p>Some other posts from <a href="https://shift.infinite.red/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">Infinite Red</a> about React Native:</p><ol><li><a href="https://shift.infinite.red/creating-a-trivia-app-with-ignite-bowser-part-1-1987cc6e93a1">Creating a Trivia App with Ignite Bowser — Part I</a> by <a href="https://shift.infinite.red/@robin_heinze">Robin Heinze</a></li><li><a href="https://shift.infinite.red/how-to-create-a-multi-pane-drawer-in-react-native-9d69dd1eb2d4">How to Create a Multi-Pane Drawer in React Native</a> by <a href="https://shift.infinite.red/@morganlaco">Morgan Laco</a></li><li><a href="https://shift.infinite.red/react-native-faq-8dc5c1083baa">React Native FAQ</a> by <a href="https://shift.infinite.red/@gantlaborde">Gant Laborde</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fcd7a2e5c14" width="1" height="1" alt=""><hr><p><a href="https://shift.infinite.red/handling-64-bit-android-builds-for-react-native-2fcd7a2e5c14">Handling 64-bit Android Builds for React Native</a> was originally published in <a href="https://shift.infinite.red/">Red Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Start Using Reactotron in Your Expo Project Today in 3 Easy Steps]]></title>
            <link>https://shift.infinite.red/start-using-reactotron-in-your-expo-project-today-in-3-easy-steps-a03d11032a7a?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a03d11032a7a</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[expo]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[reactotron]]></category>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Tue, 30 Jul 2019 16:57:21 GMT</pubDate>
            <atom:updated>2019-08-02T19:14:38.733Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Reactotron logo and Expo logo on a laptop screen with iOS and Android phones in the foreground" src="https://cdn-images-1.medium.com/max/1024/1*uZLFed40O8YoN7bTGJc9jA@2x.jpeg" /></figure><p>If you want to get into mobile development with React Native, <a href="https://expo.io/learn">Expo</a> is a great place to start. If you’re already doing React Native development with Expo, then you’re in luck, because I’m going to show you how to enhance your React Native Expo debugging experience by allowing you to integrate a great debugging tool called <a href="https://github.com/infinitered/reactotron">Reactotron</a>.</p><p>If you’re not familiar with Reactotron, you can check out <a href="https://www.youtube.com/watch?v=UiPo9A9k7xc">Darin Wilson’s talk at Chain React 2018</a> for an in-depth tour of the benefits of adding it to your toolchain, but in this article <em>I’ll walk you through the simple setup to get Reactotron logging in your React Native Expo app in 3 easy steps</em>!</p><blockquote>This post assumes you already have a <a href="https://docs.expo.io/versions/v33.0.0/workflow/up-and-running/">running React Native Expo Project</a>.</blockquote><h3>Let’s Get Started!</h3><h4>Install Reactotron</h4><p><a href="https://github.com/infinitered/reactotron/releases">Download Reactotron</a> for your OS, unzip, and run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*1VDafbioSe8FuJ3mwQ1ZYA.png" /><figcaption><em>Reactotron running, but not connected to an app.</em></figcaption></figure><h4>Integrate Reactotron Into Your App</h4><ol><li>Install reactotron-react-native with your package manager of choice:</li></ol><pre>npm i --save-dev reactotron-react-native</pre><pre>or</pre><pre>yarn add --dev reactotron-react-native</pre><p>2. Create ReactotronConfig.js in your editor and paste this:</p><pre>import Reactotron from &quot;reactotron-react-native&quot;</pre><pre>Reactotron<br>  .configure() // controls connection &amp; communication settings<br>  .useReactNative() // add all built-in react native plugins<br>  .connect() // let&#39;s connect!</pre><p>3. Finally, we import this on startup in yourApp.js:</p><pre>if(__DEV__) {<br>  import(&quot;./ReactotronConfig&quot;)<br>}</pre><p>If you refresh your app, you should see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*dWpGZmuLk7bkH02GR_1gxA.png" /><figcaption>Reactotron is connected to your Expo app.</figcaption></figure><blockquote>Reactotron is now hooked-up in your Expo app!</blockquote><h3>Now what? Let’s log!</h3><blockquote>Import Reactotron in your <em>App.js</em>:</blockquote><pre>import Reactotron from &quot;reactotron-react-native&quot;</pre><pre>...</pre><h3>Methods</h3><blockquote><em>.log()</em> — Log a single item like a string or an object.</blockquote><p>In your App.js:</p><ul><li>Put this before your App component:</li></ul><pre>Reactotron.log(&quot;HELLO WORLD&quot;)</pre><pre>...</pre><ul><li>Refresh your app (iOS: Cmd + R; Android: r + r)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*GoIwB5IvD7wXr7LkjPrIFA.png" /><figcaption>Reactotron.log(“HELLO WORLD”)</figcaption></figure><blockquote><em>.display()</em> — Descriptive logging and logging complex data.</blockquote><ul><li>Put this before your App component:</li></ul><pre>Reactotron.display({<br>  name: &quot;KNOCK KNOCK&quot;,<br>  preview: &quot;Who&#39;s there?&quot;,<br>  value: &quot;Orange.&quot;<br>})</pre><pre>...</pre><ul><li>Refresh your app (iOS: Cmd + R; Android: r + r)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*nFykzt-Er6sUCzD45l7tgA.png" /><figcaption>Log the `name` and `preview` value.</figcaption></figure><ul><li>Click on theKNOCK KNOCK row to expand the log and see the value:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*OYZk3xAe5rPSbaXRBQtjAw.png" /><figcaption>Expand the row to log the `value`.</figcaption></figure><blockquote><em>.error()</em> — Log an eye-catching error message.</blockquote><pre>Reactotron.error(“WOOPS!”)</pre><pre>...</pre><ul><li>Refresh your app (iOS: Cmd + R; Android: r + r)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*CGWY182wDP8VF5MRvSWPBQ.png" /><figcaption>Log an error message.</figcaption></figure><h3>Let’s Try it with Expo’s Location Module</h3><blockquote>Using the Location and Permissions modules from Expo, we’ll setup a basic example that requests the user’s permission to access location, and then display the user’s location in the app and log the latitude and longitude in Reactotron.</blockquote><ol><li>We’ll request the user’s permission to access location when the app loads.</li></ol><pre>import React from &quot;react&quot;<br>import { StyleSheet, Text, View } from &quot;react-native&quot;<br>import { Location, Permissions } from &quot;expo&quot;<br>import Reactotron from &quot;reactotron-react-native&quot;</pre><pre>export default class App extends React.Component {<br>  state = {<br>    location: null,<br>    errorMessage: null<br>  }</pre><pre>  componentDidMount() {<br>    this._getLocationAsync() // &lt;-- request location on mount<br>  }</pre><pre>  ...</pre><pre>}</pre><p>2. Inside the _getLocationAsync function, let’s check for permission to access the user’s location, and request it if it’s not already granted.</p><pre>_getLocationAsync = async () =&gt; {<br>  // check status of location permissions<br>  let {status} = await Permissions.askAsync(Permissions.LOCATION)<br>  if (status !== &quot;granted&quot;) {<br>   this.setState({<br>    errorMessage: &quot;Permission to access location was denied&quot;<br>   })<br>  }</pre><pre>  ...    </pre><pre>}</pre><p>3. Now we’ll get the user’s location, display it in Reactotron, and set it in state.</p><pre>_getLocationAsync = async () =&gt; {<br>  // check status of location permissions<br>  const {status} = await Permissions.askAsync(Permissions.LOCATION)<br>  if (status !== &quot;granted&quot;) {<br>   this.setState({<br>    errorMessage: &quot;Permission to access location was denied&quot;<br>   })<br>  }</pre><pre>  // get user&#39;s position<br>  const location = await Location.getCurrentPositionAsync({})</pre><pre>  const lat = location.coords.latitude // pull out latitude<br>  const lon = location.coords.longitude // pull out longitude<br>  <br>  // display location data with Reactotron.display()<br>  Reactotron.display({<br>    name: &quot;coordinates&quot;,<br>    preview: `lat: ${lat}, lon: ${lon}`, // preview just the lat/lon<br>    value: location<br>  })<br><br>  this.setState({ location }) // set the location in state 👍<br>}</pre><p>4. Finally render the location data in the app.</p><pre>... </pre><pre>render() {<br>  // give the user feedback while fetching the location<br>  let text = &quot;Waiting..&quot;<br>  if (this.state.errorMessage) {<br>    text = this.state.errorMessage<br>  } else if (this.state.location) {<br>    text = JSON.stringify(this.state.location)<br>  }<br>  return (<br>    &lt;View style={{ flex: 1, alignItems: &quot;center&quot; }}&gt;<br>      &lt;Text style={{ margin: 20, fontSize: 16 }}&gt;{text}&lt;/Text&gt;<br>    &lt;/View&gt;<br>  )<br>}</pre><h3>Show Me the Money! 💵</h3><blockquote>Reload the app and you should see the name &amp; preview output in Reactotron:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*tEWlFrX9E4WCaGrToMOU8g.png" /><figcaption>Location coordinates and preview.</figcaption></figure><blockquote>Expand the “coordinates” row to see the value:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RDksC0mOEE29zY6H-HcXuA.png" /><figcaption>Value of the coordinates.</figcaption></figure><blockquote>In your app you should see some thing like:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*d4uG0WL-Xj2YnyiePy7ZzQ.png" /><figcaption>Display location in the app.</figcaption></figure><h3>That’s It For Now!</h3><p>These setup steps and 3 Reactotron methods (log, display, and error) will be enough to get you started debugging with Reactotron in your Expo app, but where Reactotron starts to shine is when you connect it to your state management in your app like <a href="https://github.com/infinitered/reactotron/blob/master/docs/plugin-redux.md">Redux</a> or <a href="https://github.com/infinitered/reactotron/blob/master/docs/plugin-mst.md">MobX State Tree</a>, which will allow you to track global errors, watch network requests, and more. You can check out the <a href="https://github.com/infinitered/reactotron/tree/master/examples/demo-react-native">Reactotron demo app</a> for examples of Reactotron logging with Redux.</p><h3>About Frank</h3><p>Frank von Hoven III is a Senior Software Engineer at <a href="https://infinite.red/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">Infinite Red</a>, specializing in React Native mobile development, an instructor with <a href="https://academy.infinite.red/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">Infinite Red Academy</a>, and the Editor-in-Chief of <a href="https://reactnative.cc/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">The React Native Newsletter</a>. Follow him on <a href="https://twitter.com/infinite_frank">Twitter</a> for React Native insights and funny gifs and thoughts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/108/1*SHUWEujIW-1Jvc1OO4CX4Q.png" /></figure><p>Some other posts from <a href="https://shift.infinite.red/?utm_medium=blog&amp;utm_source=redshift&amp;utm_campaign=reactotron_post">Infinite Red</a> about React Native:</p><ol><li><a href="https://shift.infinite.red/creating-a-trivia-app-with-ignite-bowser-part-1-1987cc6e93a1">Creating a Trivia App with Ignite Bowser — Part I</a> by <a href="https://shift.infinite.red/@robin_heinze">Robin Heinze</a></li><li><a href="https://shift.infinite.red/how-to-create-a-multi-pane-drawer-in-react-native-9d69dd1eb2d4">How to Create a Multi-Pane Drawer in React Native</a> by <a href="https://shift.infinite.red/@morganlaco">Morgan Laco</a></li><li><a href="https://shift.infinite.red/react-native-faq-8dc5c1083baa">React Native FAQ</a> by <a href="https://shift.infinite.red/@gantlaborde">Gant Laborde</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a03d11032a7a" width="1" height="1" alt=""><hr><p><a href="https://shift.infinite.red/start-using-reactotron-in-your-expo-project-today-in-3-easy-steps-a03d11032a7a">Start Using Reactotron in Your Expo Project Today in 3 Easy Steps</a> was originally published in <a href="https://shift.infinite.red/">Red Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Painless React Native Setup for Mac, Windows, & Linux]]></title>
            <link>https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-39e2e4d58d89?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/39e2e4d58d89</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Fri, 28 Sep 2018 16:59:28 GMT</pubDate>
            <atom:updated>2018-10-25T00:07:45.965Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part Three — Linux</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bN3XDZ2SjA7ph9v3qYutVg.png" /></figure><blockquote>This is Part 3 of a three-part series covering React Native setup for <a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-956c23d2abf9">Mac</a>, <a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-99d099a1f942">Windows</a>, &amp; Linux.</blockquote><p>During my teaching with <a href="https://academy.infinite.red/">Infinite Red Academy</a>, one of the initial challenges I’ve noticed when students are getting started with React Native is installing and running React Native on their machines. Our classes and workshops are filled with students running a mix of Mac OS, Windows, and Linux so the set-up process for each individual student varies greatly across all three operating systems. If you’re a student in one of our workshops or just getting started with React Native on your own, this step-by-step guide will help you painlessly set up React Native on your Linux machine!</p><blockquote>PRO TIP: Make sure you’re connected to the internet!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*Id1ijBv9RmM4uBgJcAE-kA@2x.png" /></figure><h3>Setting up for Linux</h3><p><em>Dependencies (Install instructions below)</em></p><ul><li><strong>Node</strong></li><li><strong>React Native CLI</strong></li><li><strong>Java Developer Kit</strong></li><li><strong>Android Studio</strong></li><li><strong>Watchman</strong></li></ul><h4>LET’S GET STARTED</h4><p><em>We’re going to show installation on Ubuntu or Debian — links for other OS will be included for each step 😉</em></p><blockquote><strong><em>Install Node.js (8.0):</em></strong></blockquote><p>curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -</p><p>sudo apt-get install -y nodejs</p><p><em>If you’re not running Ubuntu or Debian, check for your Linux distribution installation instructions </em><a href="https://nodejs.org/en/download/package-manager/"><em>here</em></a><em>.</em></p><blockquote><strong><em>Install React Native CLI:</em></strong></blockquote><p>npm i -g react-native-cli</p><blockquote><strong><em>Install Java Development Kit:</em></strong></blockquote><ol><li>You’ll need your Linux version:<em> Get it by typing</em> hostnamectl <em>in your terminal.</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*TJz2yXRdLmy65QybKpF1gA.png" /><figcaption>hostnamectl</figcaption></figure><p>2. Download the correct JDK file from <a href="http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html">here</a>.</p><p><strong><em>PRO TIP</em></strong><em>: You can probably get a coffee while the JDK downloads…</em></p><p>3. Extract the JDK package and you’re good to go. (Usually just double click on the downloaded file and the files should be extracted to root for you).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7y1yLtYnLs2pvumt1xMQA.png" /><figcaption>jdk extracted</figcaption></figure><blockquote><strong><em>Install Android Studio:</em></strong></blockquote><p><em>If you’re running the 64-bit version of Ubuntu: you’ll have to install additional libraries with:</em></p><pre>sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1 libbz2-1.0:i386</pre><ol><li>Download Android Studio <a href="https://developer.android.com/studio/">here</a>.</li></ol><p><strong><em>PRO TIP</em></strong><em>: You can probably refill aforementioned coffee while Android Studio downloads…</em></p><p>2. Extract the download to a folder of your choice (or just root directory).</p><p>3. cd {your-extracted-directory}/android-studio/bin</p><p>4. ./studio.sh</p><p>5. Check “<strong>Do not import settings</strong>” when prompted. (Unless you have a previous version of Android Studio and you’d like to import its configs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lb4QG9UHN8b1YSBvEUlycw.png" /><figcaption>Don’t import settings</figcaption></figure><p>6. Follow the Wizard</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OsINDTNGdecfeHUkOZsbKw.png" /><figcaption>Wizard Step 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atVDgRpnbre4PCGB4fpgpA.png" /><figcaption>Wizard Step 2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jQbkrJ7atxA9ezyOd713Vg.png" /><figcaption>Wizard Step 3</figcaption></figure><p>7. Check all boxes for:</p><ul><li>Android SDK</li><li>Android SDK Platform</li><li>— API 28 or greater</li><li>Android Virtual Device</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cO9vV3wbqjBHx5ekZkZCRQ.png" /><figcaption>Wizard Step 4</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VmhAXnuX6ksLMpsGHrn4EA.png" /><figcaption>Wizard Step 5</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWsdPfCsKhhvexvrf_Ow5g.png" /><figcaption>Wizard Finish</figcaption></figure><p>8. Finish and download! (This will take awhile).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rRH6VORDqagIPP2H2sn76g.png" /><figcaption>Download Android Studio</figcaption></figure><p>9. When it’s finished downloading, you can close Android Studio?</p><blockquote><strong><em>Configure JAVA_HOME &amp; ANDROID_HOME environment variables:</em></strong></blockquote><p><em>If your terminal is still running Android studio:</em></p><p>ctrl + C a few times to stop it</p><p>NEXT:</p><p>Check if you have a .bash_profile file in your root directory:</p><p>ls -a in your terminal and check for the .bash_profile file.</p><p><em>If you don’t have a </em>.bash_profile<em> in your root directory:</em></p><p>touch .bash_profile</p><p>Open your bash profile:</p><p>nano /.bash_profile</p><p>and add:</p><pre>export JAVA_HOME=&quot;$HOME/jdk1.8.0_181&quot; // Or your version of the jdk<br>export PATH=$PATH: &quot;$JAVA_HOME/bin&quot;<br>export ANDROID_HOME=$HOME/Android/Sdk export PATH=$PATH:$ANDROID_HOME/tools export PATH=$PATH:$ANDROID_HOME/tools/bin export PATH=$PATH:$ANDROID_HOME/platform-tools export PATH=$PATH:$ANDROID_HOME/emulator</pre><p>Then <em>ctrl + o</em> to write out, hit <em>Enter</em> and then <em>ctrl + x</em> to close the editor.</p><blockquote><strong><em>Install Watchman:</em></strong></blockquote><p>First, install Linuxbrew:</p><p>sudo apt install linuxbrew-wrapper</p><p>…then:</p><p>brew update &amp;&amp; brew install watchman (might get a warning, just hit Enter)</p><p><strong>LAST: Configure </strong><strong>.bashrc for correct path to npm.</strong></p><p>npm list -g | head -n 1 will give you the path to npm</p><p>Usually it’s something like /home/frank/.npm-global/lib</p><p>Now let’s add the path to npm into the .bashrc file:</p><p>In root directory: nano .bashrc</p><p>Scroll (or down arrow) to the bottom of the .bashrc file and add:</p><pre>export PATH=&quot;$HOME/.npm-global/bin:$PATH&quot;</pre><p>Then ctrl + o to write out, hit Enter and then ctrl + x to close the editor.</p><p>In your command line you should be able to type react-native and get this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*Z1nwaP7HatO4MvTrjZtGcw.png" /><figcaption>Command needed</figcaption></figure><p><strong>THAT’S IT! 🎉 </strong><em>(finally)</em></p><p><strong>Now you’re ready to create your first React Native App!</strong></p><p>cd into a /projects folder, or wherever you want to keep your projects</p><blockquote><strong><em>Create a React Native App:</em></strong></blockquote><p>react-native init YourProjectName</p><p><strong><em>Setup an Android Virtual Device:</em></strong></p><ol><li>Open Android studio: inandroid-studio/bin type ./studio.sh</li><li>Click on Create a New Project</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*2sw0JSqp62eSmUmrO6qr7w.png" /></figure><ol><li>Name it if you want or just accept My Application as the default name</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*LYx8fke5ToqlN525Th3LmQ.png" /></figure><p>4. Select “Phone and Tablet” for the target devices</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*yaR4dsI2vlgTLWR_xPHoOw.png" /></figure><p>5. Select an “Empty Activity” from the “Add an Activity to Mobile” screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*pq-1uvINSgbDgzzj5ORRsw.png" /></figure><p>6. Hit “Finish” on the Configure Activity screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*MUDCDAiGYAv03qui57w4pw.png" /></figure><p>7. After your project is completed, Android Studio should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1bo3TbjWcOk7fsLSME2mhw.png" /></figure><p>8. Click the icon noted in the image above to launch the Android Virtual Device (AVD) manager</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*62YV6rfPKTuTlN2bbMk3ZA.png" /></figure><p>9. Click the ▶️ button in the AVD to launch the emulator</p><p><em>If you try to run an AVD and you get this message:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gkgfqx_nYHq8Zzs_-dONSw.png" /></figure><blockquote>You might be running 64-bit Ubuntu, and will need to install a few things:</blockquote><blockquote><em>sudo apt-get install qemu-kvm libvirt-bin virtinst bridge-utils cpu-checker</em></blockquote><blockquote>Then run <em>kvm-ok</em></blockquote><blockquote>If you output still says your CPU doesn’t support KVM extensions…</blockquote><blockquote>Try downloading and running one of the alternative emulators <a href="https://fossbytes.com/best-android-emulators-pc/">here</a>.</blockquote><blockquote>If none of this works, you’ll have to <a href="https://facebook.github.io/react-native/docs/running-on-device">run your React Native project on an Android Device</a>.</blockquote><blockquote><strong><em>Agree to Android SDK licenses:</em></strong></blockquote><p>sdkmanager --licenses</p><p><em>You’ll have to hit </em><em>y and </em><em>Enter a bit as there are quite a few licenses.</em></p><blockquote><strong><em>Run Your Project:</em></strong></blockquote><p>In one terminal: npm start — to start the packager</p><p>In another terminal:react-native run-android</p><h3>About Frank</h3><p>Frank von Hoven III is a Software Engineer at <a href="http://infinite.red/">Infinite Red</a>, specializing in React Native mobile development, an instructor with <a href="https://academy.infinite.red/">Infinite Red Academy</a>, and the Editor-in-Chief of <a href="http://reactnative.cc/">The React Native Newsletter</a>. He lives in New Orleans, LA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/108/1*SHUWEujIW-1Jvc1OO4CX4Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39e2e4d58d89" width="1" height="1" alt=""><hr><p><a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-39e2e4d58d89">Painless React Native Setup for Mac, Windows, &amp; Linux</a> was originally published in <a href="https://shift.infinite.red/">Red Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Painless React Native Setup for Mac, Windows, & Linux]]></title>
            <link>https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-99d099a1f942?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/99d099a1f942</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Thu, 27 Sep 2018 15:31:02 GMT</pubDate>
            <atom:updated>2018-10-25T00:07:24.967Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part Two — Windows</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*goH_Kx1F52bnRnQ_SFPCDw.png" /></figure><blockquote>This is Part 2 of a three-part series covering React Native setup for <a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-956c23d2abf9">Mac</a>, Windows, &amp; <a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-39e2e4d58d89">Linux</a>.</blockquote><p>During my teaching with <a href="https://academy.infinite.red/">Infinite Red Academy</a>, one of the initial challenges I’ve noticed when students are getting started with React Native is installing and running React Native on their machines. Our classes and workshops are filled with students running a mix of Mac OS, Windows, and Linux so the set-up process for each individual student varies greatly across all three operating systems. If you’re a student in one of our workshops or just getting started with React Native on your own, this step-by-step guide will help you painlessly set up React Native on your Windows machine!</p><blockquote>PRO TIP: Make sure you’re connected to the internet!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*y9Ux8shkYgiJvRk3sCMXmg@2x.png" /></figure><h3>Setting up for Windows</h3><p><em>Dependencies (Install instructions below)</em></p><ul><li><strong>Node</strong></li><li><strong>Python2</strong></li><li><strong>React Native CLI</strong></li><li><strong>Java Developer Kit</strong></li><li><strong>Android Studio</strong></li></ul><p><em>Optional dependencies</em></p><ul><li><strong>Yarn</strong></li><li><strong>Solidarity</strong></li></ul><h4>LET’S GET STARTED</h4><blockquote><strong><em>Install Chocolatey:</em></strong></blockquote><p><strong><em>(</em></strong><em>To install Chocolatey, </em><strong><em>you need to run as administrator — right click cmd or Powershell and select “Run as Administrator.”</em></strong><em>)</em></p><ul><li><strong><em>Powershell:</em></strong></li></ul><pre>Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString(&#39;<a href="https://chocolatey.org/install.ps1&#39;">https://chocolatey.org/install.ps1&#39;</a>))</pre><ul><li><strong><em>Cmd.exe:</em></strong></li></ul><pre>@&quot;%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe&quot; -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command &quot;iex ((New-Object System.Net.WebClient).DownloadString(&#39;https://chocolatey.org/install.ps1&#39;))&quot; &amp;&amp; SET &quot;PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin&quot;</pre><p>You should see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fEjPnt3gwLpC0Z_Y" /></figure><blockquote><strong><em>Install Node, Python2, &amp; JDK </em></strong><em>(in administrator prompt)</em><strong><em>:</em></strong></blockquote><pre>choco install -y nodejs.install python2 jdk8</pre><p>From this point on, we’re going use yarn to install our node packages:</p><blockquote><strong><em>Install Yarn:</em></strong></blockquote><pre>choco install -y yarn</pre><blockquote><strong><em>Install React Native CLI:</em></strong></blockquote><pre>yarn global add react-native-cli</pre><blockquote><strong><em>Install Android Studio:</em></strong></blockquote><ol><li>Download Android Studio <a href="https://developer.android.com/studio/">here</a>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*1SnJPCmHkCPnmK1HE0dIQQ.png" /></figure><p>2. Run the downloaded file by double clicking on it.</p><p>3. Begin the Android Studio installation wizard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*yYbhr0CcsfWgHxTKd7VwBQ.png" /></figure><p>3. Select “<strong>Android Virtual Device</strong>” when choosing components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*lUPt4XB9RiMstI9gZsPaaQ.png" /></figure><p>4. Select the installation folder for Android Studio</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*EZhWrQieLoPe9AOnYdjELg.png" /></figure><p>5. Select the Start Menu Folder Name (recommend “Android Studio”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*TSN_PH-sm2vBpQEojPE1hQ.png" /></figure><p>6. Check “<strong>Do not import settings</strong>” when prompted. (Unless you have a previous version of Android Studio and you’d like to import its configs).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*sULKm8AFeDX72KQT3Q567w.png" /></figure><p>7. Agree to the Android Studio Terms &amp; Conditions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*WvnP5iS7JqgUc2V3G6BO6A.png" /></figure><p>8. Wait for Android Studio to install…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*dJws0qcAeOT4oaOB_k3PjQ.png" /></figure><p>9. When installation is complete hit “Next”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*xR2IxmBnQAibNq8eSrI7Wg.png" /></figure><p>10. Click “Finish” to launch Android Studio</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*eEIU4P2mc3y1fbNjBz0_Rw.png" /></figure><blockquote><strong><em>Initially configure Android Studio:</em></strong></blockquote><ol><li>Begin the Android Studio configuration wizard.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*v-CqlURlQJQM6Xp2ePqhnA.png" /></figure><p>2. Select “Custom” Install Type</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*blbWAR-AVSQlbXXLTv2CXg.png" /></figure><p>3. Select your UI Theme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*Qsp3xj_UjKhigdArWA_b0A.png" /></figure><p>3. Check all boxes for:</p><ul><li>Android SDK</li><li>Android SDK Platform</li><li>— API 28 or greater</li><li>Performance(Intel HAXM)</li><li>Android Virtual Device</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*htctvLZmzrURgyHkmhPTcQ.png" /></figure><p>4. Use the recommended Emulator Settings (hit “Next).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*fmnoiRUjd6pFUbEipVySKg.png" /></figure><p>5. Hit “Finish” to download the Android Studio components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*x7wjcxjWTb_Sb6tasxRD9w.png" /></figure><p>6. Wait for downloading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*oT1e95Fkvp-PNb9q8Dx4KA.png" /></figure><p>7. Hit “Finish” and verify settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*o1r71-1ZgyaZSHeIX3826g.png" /></figure><p><strong><em>Start a new project in Android Studio:</em></strong></p><ol><li>Select “Start a new Android Studio project.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*m6I4NS6QW8GXZ4n8qQGA-A.png" /></figure><p>2. Create and name your project (“My Application” is fine for now).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*Qj8kZP17U3-jUjs5APCC9A.png" /></figure><p>3. Select Target Devices (Phone &amp; Tablet recommended)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*rNN7gGydPTQ2Lblt1Fit9w.png" /></figure><p>4. Begin with an Empty Activity</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*ezoHQeMkt0Ye7q766Mx2_w.png" /></figure><p>5. Configure the Activity (just hit “Next”)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*4JgAmqKfcpg22V5R-07AWw.png" /></figure><p>6. Install the components (hit “Finish”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*JQONPen_moeWAUtMcZS9Jw.png" /></figure><blockquote><strong><em>Launch an Android Virtual Device (AVD):</em></strong></blockquote><ol><li>Click on the AVD Manager icon</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ChuIBxYfBcD1R9jlvbqIQ.png" /></figure><p>2. Click the ▶️ icon to launch the Nexus AVD</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s4BkUkRPfJgSzX0dJxkejQ.png" /></figure><blockquote><strong><em>Create a React Native App:</em></strong></blockquote><p>react-native init YourProjectName</p><blockquote><strong><em>Run Your Project:</em></strong></blockquote><p>cd YourProjectName</p><p>react-native run-android</p><h3>About Frank</h3><p>Frank von Hoven III is a Software Engineer at <a href="http://infinite.red/">Infinite Red</a>, specializing in React Native mobile development, an instructor with <a href="https://academy.infinite.red/">Infinite Red Academy</a>, and the Editor-in-Chief of <a href="http://reactnative.cc/">The React Native Newsletter</a>. He lives in New Orleans, LA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/108/1*SHUWEujIW-1Jvc1OO4CX4Q.png" /></figure><h3>About Frank</h3><p>Frank von Hoven III is a Software Engineer at <a href="http://infinite.red/">Infinite Red</a>, specializing in React Native mobile development, an instructor with <a href="https://academy.infinite.red/">Infinite Red Academy</a>, and the Editor-in-Chief of <a href="http://reactnative.cc/">The React Native Newsletter</a>. He lives in New Orleans, LA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/108/1*SHUWEujIW-1Jvc1OO4CX4Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99d099a1f942" width="1" height="1" alt=""><hr><p><a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-99d099a1f942">Painless React Native Setup for Mac, Windows, &amp; Linux</a> was originally published in <a href="https://shift.infinite.red/">Red Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Painless React Native Setup for Mac, Windows, & Linux]]></title>
            <link>https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-956c23d2abf9?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/956c23d2abf9</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[setup]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Wed, 26 Sep 2018 19:41:07 GMT</pubDate>
            <atom:updated>2021-01-24T05:00:33.469Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part One — Mac</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1n1Hf3SxnUTXB_eJ_oNc-A.png" /></figure><blockquote>This is Part 1 of a three-part series covering React Native setup for Mac, <a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-99d099a1f942">Windows</a>, &amp; <a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-39e2e4d58d89">Linux</a>.</blockquote><p>During my teaching with <a href="https://academy.infinite.red/">Infinite Red Academy</a>, one of the initial challenges I’ve noticed when students are getting started with React Native is installing and running React Native on their machines. Our classes and workshops are filled with students running a mix of Mac OS, Windows, and Linux so the set-up process for each individual student varies greatly across all three operating systems. If you’re a student in one of our workshops or just getting started with React Native on your own, this step-by-step guide will help you painlessly set up React Native on your Mac!</p><blockquote>PRO TIP: Make sure you’re connected to the internet!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*Rcn8s1z6gLTpNN59NbQlNA@2x.png" /></figure><h3>Setting up for Mac OS</h3><p><em>Dependencies (Install instructions below)</em></p><ul><li><strong>Node</strong></li><li><strong>Watchman</strong></li><li><strong>CocoaPods</strong></li><li><strong>Xcode</strong></li></ul><h4>LET’S GET STARTED</h4><blockquote><strong><em>Homebrew</em></strong> (<em>if you don’t already have it</em>):</blockquote><p><em>Paste all of the following into your terminal prompt at your root directory:</em></p><pre>/usr/bin/ruby -e &quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&quot;</pre><blockquote><strong><em>Install Node </em></strong>(you’ll need ≥ 8.3)<strong><em>:</em></strong></blockquote><pre>brew install node</pre><blockquote><strong><em>Install Watchman</em></strong></blockquote><pre>brew install watchman</pre><blockquote><strong><em>Install CocoaPods:</em></strong></blockquote><pre>sudo gem install cocoapods</pre><p><em>If you get an error, try installing npm directly with:</em></p><pre>curl -0 -L <a href="https://npmjs.org/install.sh">https://npmjs.org/install.sh</a> | sudo sh</pre><blockquote><strong><em>Install Xcode:</em></strong></blockquote><p>Via the <a href="https://itunes.apple.com/us/app/xcode/id497799835?mt=12">Appstore</a></p><blockquote><strong><em>Install the Xcode Command Line Tools:</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*tnektV7qVv4GIw6ji7QOmQ.png" /></figure><ol><li>Open Xcode</li><li>⌘, to open Preferences or (<strong>Xcode &gt; Preferences)</strong></li><li>Goto the <strong>Locations</strong> tab</li><li>Install the Command Line Tools by selecting the most recent version from the Command Line Tools dropdown</li></ol><blockquote><strong><em>Create a React Native App:</em></strong></blockquote><p>npx react-native init YourProjectName</p><blockquote><strong><em>Run the app:</em></strong></blockquote><p>cd YourProjectName</p><p>npx react-native run-ios</p><p><em>If a packager isn’t running, you might need to </em><em>yarn start in a separate terminal window.</em></p><h4>ENJOY!</h4><h3>About Frank</h3><p>Frank von Hoven III is a Software Engineer at <a href="http://infinite.red/">Infinite Red</a>, specializing in React Native mobile development, an instructor with <a href="https://academy.infinite.red/">Infinite Red Academy</a>, and the Editor-in-Chief of <a href="http://reactnative.cc/">The React Native Newsletter</a>. He lives in New Orleans, LA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/108/1*SHUWEujIW-1Jvc1OO4CX4Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=956c23d2abf9" width="1" height="1" alt=""><hr><p><a href="https://shift.infinite.red/painless-react-native-setup-for-mac-windows-linux-956c23d2abf9">Painless React Native Setup for Mac, Windows, &amp; Linux</a> was originally published in <a href="https://shift.infinite.red/">Red Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shipping Persistant Reducers]]></title>
            <link>https://shift.infinite.red/shipping-persistant-reducers-7341691232b1?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7341691232b1</guid>
            <category><![CDATA[ignite]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[rehydration-services]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 16:28:31 GMT</pubDate>
            <atom:updated>2016-07-13T16:28:31.346Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kOXBaAIZeCVXo7-jwfr6Qw.jpeg" /></figure><h4>If a reducer changes in the woods…does anybody know it?</h4><p>Currently in React Native when using auto rehydration from the <a href="https://github.com/rt2zz/redux-persist"><strong>redux-persist</strong></a><strong> </strong>module, your app will crash if you add to the reducer shape and have auto rehydrate enabled. The fix in development requires resetting the simulator to get updated fresh reducers. The fix in production means uninstalling and reinstalling the app. Rehydration Services solves a problem that you don’t realize is a problem until it’s too late, and the need to reset or reinstall by making sure that your app’s reducers are up to date — preventing a crash.</p><p>You’ve built your app, it’s almost ready for release, and you’re at that last minute “All aboard!” stage. You’re using <em>autoRehydrate </em>from<em> </em><strong>redux-persist </strong>and you find the need to add keys to your reducers because you…</p><ol><li>Forgot.</li><li>Didn’t know you’d need them.</li><li>Decided you’d like to throw in one last added feature before launch.</li></ol><p>Let’s say your app allows for delivery to certain cities and states — allowing a user to set delivery location with a picker.</p><p>You’d like to add an element(s) to the reducer shape…</p><p><em>Perhaps you add ‘zipCodes’ to further refine delivery options.</em></p><pre>export const INITIAL_STATE = Immutable({<br>  cities: [],<br>  states: []<br>})</pre><p><em>turns into…</em></p><pre>export const INITIAL_STATE = Immutable({<br>  cities: [],<br>  states: [],<br>  zipCodes: []<br>})</pre><p>You add a picker for zip codes and set its options with <em>zipCodes.map</em></p><h4>OH NOES!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7I_LCXHKdOGRkl0FqIP6IA.gif" /><figcaption>An addition to reducers will cause apps with auto rehydration in production to crash when the reducer is accessed.</figcaption></figure><p>Since you are rehydrating your store, the app will rehydrate with the old reducer shape, not know that <em>zipCodes</em> exists, and crash when <em>zipCodes.map </em>is called by the zip codes picker!</p><p>Because auto rehydrate will resurrect the outdated reducers, the app has no way to know that the reducer shape has changed…until now.</p><h4>The Solution</h4><ul><li>Create a file called ReduxPersist.js (in the Config folder is a good place).</li><li>If you were enabling rehydration somewhere, (e.g. DebugSettings, Config, etc.) move its “switch” into <em>ReduxPersist</em> and use the <em>active</em> key for enabling the feature.</li><li>Configure the store to be rehydrated in <em>ReduxPersist</em> using the <em>storeConfig</em> key and make it a part of <em>ReduxPersist</em>, since this store is what is being persisted and will be accessed by <em>RehydrationServices.</em></li><li>Finally, add a <em>reducerVersion</em> key<em>, </em>that will be manually updated when you add to the reducer shape<em> </em>inside <em>ReduxPersist </em>to track changes in reducer shape and notify <em>RehydrationServices</em> that a change has occurred.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/496/1*Mkxq35NXJOc-GHxydOApJw.png" /></figure><h4>How it works</h4><ol><li>When the app is loaded, RehydrationService.js will check for <em>reducerVersion</em> parity.</li></ol><p>2. If the <em>reducerVersion</em> number persisted in AsyncStorage is different than the one in ReduxPersist’s <em>reducerVersion</em>:</p><ul><li>The app will purge the current store.</li><li>Rebuild a new store with the updated reducer(s) shape.</li><li>Set the AsyncStore <em>reducerVersion</em> to the updated version number.</li></ul><h4>Let’s See It Work In Action…</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT4uQgeA9TBy6e8Azm%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2Fbbqfilms-slimer-pizza-xT4uQgeA9TBy6e8Azm&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxT4uQgeA9TBy6e8Azm%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="337" frameborder="0" scrolling="no"><a href="https://medium.com/media/bbbc96c21c6f771a271043d9f3327e4c/href">https://medium.com/media/bbbc96c21c6f771a271043d9f3327e4c/href</a></iframe><p><strong>Using a similar scenario as the previous zipCodes reducer example, let’s walk through the new process that will happen now that we have <em>RehydrationServices</em> and <em>ReduxPersist </em>in place…</strong></p><p><em>Let’s say our app is for pizza delivery and is</em><strong><em> in production</em></strong><em>:</em></p><p>We’ve been making and delivering any kind of pizza that a user wants…as long as it’s pepperoni.</p><pre>export const INITIAL_STATE = Immutable({<br>  meats: [&#39;Pepperoni&#39;]<br>})</pre><p>But we’re growing fast, and our customers want more toppings like meats and veggies, so we’ll add them to our reducer shape.</p><pre>export const INITIAL_STATE = Immutable({<br>  meats: [&#39;Pepperoni&#39;, &#39;Chicken&#39;, &#39;Sausage],<br>  veggies: [&#39;Mushrooms&#39;, &#39;Onions&#39;, &#39;Onions&#39;]<br>})</pre><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FfSBaqOjrWDHzi%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2Fguy-fieri-fSBaqOjrWDHzi&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FfSBaqOjrWDHzi%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/89a111a95f838e6f0d824c2f54aeb91d/href">https://medium.com/media/89a111a95f838e6f0d824c2f54aeb91d/href</a></iframe><p>Because we bumped our <em>reducerVersion</em> when we added the extra <em>veggies</em> key to the reducer’s initial state, <em>RehydrationServices</em> will know that we would rehydrate with an outdated reducer shape, so…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FbyrjZgFhTYQHm%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2FbyrjZgFhTYQHm&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FbyrjZgFhTYQHm%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/a30261283e208ae0ce58d30d683b9895/href">https://medium.com/media/a30261283e208ae0ce58d30d683b9895/href</a></iframe><h4>RehydrationServices to the rescue!</h4><p><em>RehydrationServices</em> will purge the store and re-persist a fresh store with the updated reducer shape because <em>ReduxPersist</em> is active and our stored local reducer version doesn’t match the reducer version!</p><h3>YAY!</h3><p>If you’re using the latest <a href="https://github.com/infinitered/ignite">Ignite</a> generator, <em>RehydrationServices</em> is already included in your project! If not, using something like <em>RehydrationServices</em> and <em>ReduxPersist</em> when using store rehydration can be a great way for a team to keep track of updates and changes to reducer shapes and avoid app crashes — it can also help avoid headaches when in development…and migraines when in production.</p><h4>A Deeper Look</h4><p>A quick video on how RehydrationServices works:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8wKN3gvwx_Q%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8wKN3gvwx_Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8wKN3gvwx_Q%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/53744c1d4c06eaec9dd117fb2de68d1d/href">https://medium.com/media/53744c1d4c06eaec9dd117fb2de68d1d/href</a></iframe><h3>About Frank</h3><p>Frank von Hoven III is a Software Engineer at <a href="http://infinite.red/">Infinite Red</a>, specializing in React Native mobile development. He lives in New Orleans, LA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*y5HADJbnH1UTihoqNdBtdA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7341691232b1" width="1" height="1" alt=""><hr><p><a href="https://shift.infinite.red/shipping-persistant-reducers-7341691232b1">Shipping Persistant Reducers</a> was originally published in <a href="https://shift.infinite.red/">Red Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m a Junior Developer, and I can React Native…]]></title>
            <link>https://shift.infinite.red/im-a-junior-developer-and-i-can-react-native-5cb64d4de3a6?source=rss-16bdff512d3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cb64d4de3a6</guid>
            <dc:creator><![CDATA[Frank von Hoven]]></dc:creator>
            <pubDate>Tue, 17 May 2016 16:48:39 GMT</pubDate>
            <atom:updated>2016-05-17T20:18:44.204Z</atom:updated>
            <content:encoded><![CDATA[<h4>Yes You Can RN</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IA8H14tdrPAW2fJOkupU9w.jpeg" /></figure><h4>Introduction</h4><p>I have been using React Native for 4 months now. Before that I had been developing for iOS and Android using RubyMotion. Even before that, I ran my own insurance agency. My experience as a professional developer is not as seasoned as people who got a degree in Computer Science twenty years ago, but then again, technology isn’t the same as it was then. At the exponential rate that our world is changing, technology won’t be the same 5 years from now. I firmly believe that React Native will be a major reason why technology and the way in which we use it will be be almost unrecognizable in the not too distant future.</p><h4>Jump In With Both Feet</h4><p>Being a junior developer who had never written JavaScript, I was slightly hesitant to get into a new technology, especially since I was just getting my footing in Ruby. But the ease of use that React Native promised was too attractive to pass up. The proliferation of resources already available made me feel very comfortable, since React Native uses a language that has been around for a while, Couple that with the large open source community and a devoted team at Facebook updating docs, and I felt pretty secure that I wouldn’t be stuck with a question gathering dust on StackOverflow.</p><blockquote>Somebody said that it couldn’t be done</blockquote><blockquote>But he with a chuckle replied</blockquote><blockquote>That “maybe it couldn’t,” but he would be one</blockquote><blockquote>Who wouldn’t say so till he’d tried.</blockquote><blockquote>So he buckled right in with the trace of a grin</blockquote><blockquote>On his face. If he worried he hid it.</blockquote><blockquote>He started to sing as he tackled the thing</blockquote><blockquote>That couldn’t be done, and he did it!…</blockquote><blockquote>— <a href="http://www.poetryfoundation.org/poem/173579">EDGAR ALBERT GUEST</a></blockquote><h4>It Begins</h4><p>I began my foray into the React Native world by making components for Senior Developers to use in our clients’ projects. It took less than a week for me to be proficient in creating “dumb” components — basically chassis for custom buttons, text inputs, cells, etc. (As easy as React Native is and knowing what I know now, I could outsource some of this work to a monkey at the zoo.)</p><p>When I first started, I didn’t have the articulation to delve deep into code, explain neat tricks, and show you how this isn’t your father’s Javascript, but stay tuned for some of my upcoming posts, because I have learned much since I first began. For now, there is an extensive community which includes some of my colleagues like <a href="https://medium.com/u/de381924e195">Steve Kellock</a> and <a href="https://medium.com/u/6ca0fe37eac1">Gant Laborde</a> who are making invaluable contributions to the React Native community with modules like <a href="https://github.com/skellock/reactotron">Reactotron</a> and the en fuego React Native generator — <a href="https://github.com/infinitered/ignite">Ignite</a>. So if you’ve been coding for many years, and coding apps, drop what you’re doing and start a React Native project…right now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*5gOAoiYiTcUgQhnqe9AxwQ.jpeg" /></figure><h4>Yeah…but…isn’t Android a little “wonky?”</h4><p>I don’t want to write another article saying how React Native is the greatest framework out there for app development…but it is to this developer.</p><p>As of this writing, I have worked on three React Native projects that were built for iOS and Android and…let’s face it, it’s still Android. But, I’ve got some great news…it’s not half bad. Considering that a developer used to have to write an iOS app and then write and an Android app, React Native makes cross-platform developing a no brainer. In fact, the overwhelming majority of snafus that I’ve come across when developing for Android with RN are stylesheet related and are typically easy to fix. That means that there is an enormous amount of code reuse for both platforms!</p><p>With any new technology there are going to be missteps along the way, and RN is no exception, but what makes React Native exceptional is that it has the potential of limitless possibility. The <em>best</em> news is if React Native doesn’t have a component that you need to use, and the chances of that are dwindling each day with React Native’s open source community, there’s a good probability that someone has already made that component for you! If you do need to make a native module for Android check out my buddy <a href="https://medium.com/u/f49495861bb5">Ryan Linton</a>’s post on <a href="https://shift.infinite.red/native-modules-for-react-native-android-ac05dbda800d#.mm7vap9xu">React Native Android Modules</a>.</p><h4>Looking Forward</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*mYz6lr1dJUgXO_y66sOtNA.jpeg" /><figcaption>Whoa…</figcaption></figure><p>As a junior developer, one of the concerns I have is whether or not the technology I’m learning will be relevant for years to come. I’m confident that its open source community, its traction, and the backing it has will work together to continue to grow. Add the ability to create web pages with <a href="https://github.com/necolas/react-native-web">ReactNativeWeb</a> from <a href="https://twitter.com/necolas">@necolas</a> at Twitter, and I couldn’t be more excited about the future of React Native!</p><h3>About Frank</h3><p>Frank von Hoven III is a Junior Developer at <a href="http://infinite.red/">Infinite Red</a> (specializing in React Native mobile development) and lives in New Orleans, LA.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cb64d4de3a6" width="1" height="1" alt=""><hr><p><a href="https://shift.infinite.red/im-a-junior-developer-and-i-can-react-native-5cb64d4de3a6">I’m a Junior Developer, and I can React Native…</a> was originally published in <a href="https://shift.infinite.red/">Red Shift</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>