<?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 Adam Perry on Medium]]></title>
        <description><![CDATA[Stories by Adam Perry on Medium]]></description>
        <link>https://medium.com/@dikaiosune?source=rss-44f114aaf91a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*F6oq6B7g4qQZhLHSL7HreA.png</url>
            <title>Stories by Adam Perry on Medium</title>
            <link>https://medium.com/@dikaiosune?source=rss-44f114aaf91a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:19:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dikaiosune/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[Expo Security Update 1/29/18: minor leak resolved; no known users affected]]></title>
            <link>https://blog.expo.dev/expo-security-update-1-29-18-minor-leak-resolved-no-known-users-affected-9a83f1751ec6?source=rss-44f114aaf91a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a83f1751ec6</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Adam Perry]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 22:04:52 GMT</pubDate>
            <atom:updated>2018-01-29T22:35:24.474Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>If you read nothing else here: we just want to note that to the best of our knowledge no one was affected by this issue, as it was a leak of a very low-value secret that would have required significant knowledge to cause to leak. </strong>We deeply value the trust of the developer community, and we believe the best way to maintain and build that trust is to be fully transparent whenever we have any security concerns.</p><p>Going forward, we’ll be documenting more about the security guarantees of various Expo products. We also have some recommendations outlined near the end of this article.</p><h3>Discovery</h3><p>On Friday, January 26th, 2018, we were alerted by a developer that they saw one of their passwords in their standalone app build logs. By default these logs are only visible to the user who initiated the build, which we’ll cover below. We confirmed that the “P12 Password” requested during the iOS standalone build setup was indeed being logged to the standalone build logs.</p><p>The <a href="https://en.wikipedia.org/wiki/PKCS_12">Wikipedia article</a> on the PKCS12 certificate format has some good primer information on what is contained in the file. When we build users’ standalone apps for iOS, we have to perform Apple’s <a href="https://developer.apple.com/library/content/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html">code signing process</a> on the built binary, and the P12 we ask users to generate or provide is used as one of the inputs to that code signing process. Specifically, we use a “distribution” certificate/key pair bundled in the P12 to sign standalone apps for the App Store. When uploading this P12 from users’ machines, in addition to uploading the file over TLS/HTTPS and encrypting it at rest in our database, we also require that it have a password as an extra layer of protection. Unless you reuse the password from another service, this password is only used to unlock the P12 file. If you let us generate the certificate for you, we generate a random password with high entropy.</p><p>When originally building the log viewing feature for standalone builds, we allowed access to the logs by requiring that you know the URL of the logfile, which included a random UUID (the “build ID”) and was only obtainable via authenticated request to our GraphQL API. It isn’t possible to get a list of all logs available in the S3 bucket, but public access is available if you know the URL. Because the URL is constructed from the build ID, which developers sometimes publicly share for support requests, we concluded that there was a remote possibility (if and only if the build ID were revealed) these logs could be leaked by a determined attacker.</p><h3>The Hypothetical Attack</h3><p>In order to obtain someone else’s P12 password, an attacker would have to perform something like these steps:</p><ol><li>Learn that log URLs are publicly accessible and also deduce how they are constructed. This could have been accomplished by analyzing the network traffic in their web browser while viewing the standalone build output of their own build.</li><li>Obtain the victim’s build ID, and also associate that build ID with the victim’s Expo account and the specific app slug they were building for. This information is generally not posted publicly all together, but none of these three items are typically considered private information.</li><li>Download the log file for that standalone build, and find the P12 password.</li></ol><p>Once they had the P12 password, there’s honestly not a lot they would be able to do with it. In the absolute worst case scenario, if the attacker also gained access to the victim’s actual P12 file <em>and</em> to their Apple developer account credentials, they would be able publish apps as that developer to the App Store. We are not aware of any vulnerabilities which would expose that information to an attacker via Expo’s service, and we take many precautions with the signing keys our users upload, including encrypting them at rest, twice, in our database so that an attacker would have to compromise several separate services to read that data if they gained database access. On up-to-date versions of exp , we also never receive developers’ actual Apple credentials — all authentication is done locally on their computer.</p><p>If the attack described here had occurred, a much more likely scenario would have been attempting to use that password to access services where that password may have been reused (including Expo).</p><h3>Mitigation and Resolution</h3><p>Upon being notified of this information being visible in the log output, we immediately disabled access to the S3 bucket where logs are stored. This <a href="https://status.expo.io/incidents/0w9s9h8nm0mk">made logs unavailable</a> for much of Friday.</p><p>We then worked to implement two changes that we felt would allow us to re-enable log access:</p><ol><li>Adding secrets filtering to the log upload service which processes the files before they are uploaded to S3. Build logs will now display “XXXXXXXX” instead of any substring that matches any credentials which have been provided to the build service.</li><li>Changing our log URL format to be randomly generated. In practice our tools do not rely on the specific structure of the log URL, so it was easy to make these URLs non-guessable.</li></ol><p>In the future we also plan to broker access to these logs through our authenticated service, but we’re confident that in the short term these two steps mitigate the vulnerability that was discovered.</p><p>Finally, before restoring access to logs for developers, we also archived all build logs that had been generated before these two changes. This appears to developers as an AWS “AccessDenied” error on the log viewer. If you need to access the logs from a build from before Friday 1/26/18, please email <a href="/service/mailto:support@expo.io">support@expo.io</a>.</p><h3>Recommendations</h3><p>If you uploaded your own distribution P12 and ran a build with it before last Friday, we recommend checking whether the password you used for the P12 is reused anywhere else. If it is, we <strong>strongly</strong> encourage you to change that password. While we are not aware of these passwords having been compromised, it is always a possibility.</p><p>While to our knowledge no-one’s actual P12 files leaked, if you want to cycle those as well you can revoke them in the Apple developer portal and run a new build with exp build:ios -c to clear the credentials from our database. Note that this will also clear your push notification credentials, which will prevent existing binary builds from receiving notifications properly. In the near future we plan to allow these credentials to be managed separately. If you have an app which cannot afford push notification unavailability, please email <a href="/service/mailto:security@expo.io">security@expo.io</a> and we’ll help you cycle the right credentials manually.</p><p>We also recommend enabling two-factor authentication for your Apple developer account if you haven’t already. Expo <a href="https://github.com/expo/expo/issues/160#issuecomment-348375652">added support for Apple accounts with 2FA in November 2017</a> (now turned on by default, no flag needed). Side note: as part of that update, our servers no longer receive your Apple password at all during the standalone build setup flow — it’s only used on your computer.</p><p>Finally, if you aren’t already doing so, we strongly recommend using a <a href="https://www.consumerreports.org/digital-security/everything-you-need-to-know-about-password-managers/">password manager</a> with unique passwords for separate accounts.</p><h3>Going Forward</h3><p>While this was ultimately a minor issue that to our knowledge has not been actively exploited, the trust of the developer community is important to us. We’ll continue improving the security of our services, and in the near future we plan to start maintaining some public documents about various security properties of Expo’s services.</p><p>If you have questions, comments or concerns, please post here, the <a href="https://forums.expo.io/">Expo forums</a>, or for sensitive questions you can email in to <a href="/service/mailto:support@expo.io">security@expo.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a83f1751ec6" width="1" height="1" alt=""><hr><p><a href="https://blog.expo.dev/expo-security-update-1-29-18-minor-leak-resolved-no-known-users-affected-9a83f1751ec6">Expo Security Update 1/29/18: minor leak resolved; no known users affected</a> was originally published in <a href="https://blog.expo.dev/">Exposition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expo SDK 21.0.0 is now available]]></title>
            <link>https://blog.expo.dev/expo-sdk-21-0-0-is-now-available-be33b79921b7?source=rss-44f114aaf91a------2</link>
            <guid isPermaLink="false">https://medium.com/p/be33b79921b7</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[expo]]></category>
            <dc:creator><![CDATA[Adam Perry]]></dc:creator>
            <pubDate>Thu, 21 Sep 2017 22:12:29 GMT</pubDate>
            <atom:updated>2017-09-22T10:17:24.983Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/192/1*OuVniMsj8DwtseqcDQ2qZw.png" /></figure><p>I am happy to announce the release of Expo SDK 21.0.0! It is based on <a href="https://github.com/facebook/react-native/releases/tag/v0.48.4">React Native 0.48</a> “August”. Our previous SDK, <a href="https://blog.expo.io/expo-sdk-v20-0-0-is-now-available-79f84232a9d1">20.0.0</a>, is based on <a href="https://github.com/facebook/react-native/releases/tag/v0.47.0">React Native 0.47</a> “July”.</p><h4>AppLoading Improvements: Easier to use, better error handling</h4><p><a href="https://docs.expo.io/versions/latest/sdk/app-loading.html">AppLoading</a> has been extended with new props that make it easier to use and also better able to display errors in development mode. See the <a href="https://docs.expo.io/versions/latest/sdk/app-loading.html">documentation</a> for details. These changes are backwards-compatible, and the old API will continue to work. We do recommend updating sooner rather than later — see <a href="https://github.com/expo/new-project-template/commit/dadecf341ae07e9d89a17f85ba8436f528d47a67">this commit from our template projects</a> for an example of how to update.</p><p>When developing, using the new API lets us show an error screen if an error is hit during the first render of your app, instead of hanging or restarting:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/239/1*Y5I36pn2eLjqB7JjSDly1Q.jpeg" /></figure><p>Note that in production mode the behavior of AppLoading is the same as it was previously — this API is intended to help you diagnose problems during debugging but should not affect users of your app.</p><h4>Loading screen progress in development</h4><p>In the SDK 20 release, we supported a progress bar for building the JavaScript bundle for your app when in development mode. In SDK 21, that progress bar has been extended to also display progress of downloading the bundle. This should make it significantly easier to tell the difference between an error loading your app and a slow network connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/239/1*CR15Xj6nnjdC5bidXIs4yw.gif" /></figure><p>If you are experiencing slow loading times when developing your app, check to see if you have the “tunnel” mode enabled in XDE/exp and try using LAN connections if your phone and computer are on the same network.</p><h4>Splash Screen Improvements</h4><p>The new splash API will continue to be marked as experimental while we keep working on stability and polish, but several important issues have been fixed:</p><ul><li>The transitions between various stages of app loading are smoother, and flashes of white should be eliminated in almost all scenarios.</li><li>Unspecified background colors will correctly fall back to the default of white.</li><li>Miscellaneous bugs from edge cases in the build process have been fixed.</li></ul><h4>Geocoding improvements</h4><p>Several improvements to the Geocoding API are being released with SDK 21:</p><ul><li>iOS and Android return more consistent results when a lookup fails</li><li>Error messages for missing permissions are clearer</li><li>Several native crashes are prevented by performing input validation in JavaScript</li><li>The result of the reverse geocode call now includes isoCountryCode (many thanks to <a href="https://github.com/justinmcp">justinmcp</a> for contributing a fix!)</li></ul><h4>Camera: Video Recording and EXIF metadata</h4><p>The Camera API now supports video recording! See <a href="https://docs.expo.io/versions/latest/sdk/camera.html#recordasync">the documentation</a> for details about starting and stopping recording.</p><p>The Camera API also returns <a href="https://en.wikipedia.org/wiki/Exif">Exif metadata</a> about pictures taken. This does involve a small breaking change in the API (see below for details).</p><h4>SecureStore</h4><p>The SecureStore API now works on Android L and below. We’ve tested on the versions of Android we support (4.4 and up) but Android device manufacturers may customize the cryptographic algorithms they include with devices. Since we can’t test on every type of Android device, please let us know if you encounter issues with SecureStore on specific types of Android devices.</p><p>SecureStore allows you to write any string value, while previously it was more conservative about the values it accepted. The performance of this API on Android is also better and supports storing larger values (previously Android had a limit of about 200 bytes per value).</p><h3>New APIs</h3><h4>AuthSession</h4><p>AuthSession is the easiest way to add browser-based authentication to your app. This API is designed to drastically reduce the boilerplate needed for browser redirect-based authentication flows (common with OAuth-based systems), and makes it much easier to manage redirect URL whitelists for development and when working in teams. We recommend checking out <a href="https://docs.expo.io/versions/latest/sdk/auth-session.html">the documentation</a> for more details.</p><p>For an example of how to use the new AuthSession API, check out the <a href="https://exp.host/@community/with-facebook-auth">with-facebook-auth</a> example project (<a href="https://github.com/expo/examples/tree/master/with-facebook-auth">source</a>).</p><h4>react-native-gesture-handler</h4><p>We now support using <a href="https://github.com/kmagiera/react-native-gesture-handler">react-native-gesture-handler</a> as part of our experimental DangerZone APIs. If you’re not familiar with Krzysztof Magiera’s library, definitely check it out! There is an example in the <a href="https://expo.io/@community/native-component-list">Native Component List</a>, and Brent has also published a couple of example projects using the new API:</p><ul><li><a href="https://github.com/brentvatne/swipe-action-gesture-handler-experiment">https://github.com/brentvatne/swipe-action-gesture-handler-experiment</a></li><li><a href="https://github.com/brentvatne/map-gesture-handler-example">https://github.com/brentvatne/map-gesture-handler-example</a></li></ul><p>We do have a <a href="https://docs.expo.io/versions/latest/sdk/gesture-handler.html">documentation page</a> for this API, although for the time being it just points to the GitHub repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/239/1*-51vM-wG1xqGBmeGbK3tbQ.gif" /></figure><h4>Google AdMob</h4><p>SDK 21 now supports displaying ads through <a href="https://docs.expo.io/versions/latest/sdk/admob.html">Google Admob</a> in addition to our previous support for Facebook Ads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/239/1*fTd26kA2-X12npIAPxNMpA.gif" /></figure><h4>Payments on Android</h4><p>The Payments API is now supported on Android! Check out <a href="https://docs.expo.io/versions/latest/sdk/payments.html">the documentation</a>.</p><h3>Breaking Changes</h3><h4>Camera</h4><p>The takePicture function is now called takePictureAsync and now returns an object with many keys, instead of just returning the URI. The URI is available under the uri key of the returned object.</p><p>Previously this function would return a value like:</p><p>&quot;file://path/to/your/file.jpg</p><p>And will now return an object like:</p><p>{ &quot;uri&quot;: &quot;file://path/to/your/file.jpg&quot; }</p><h4>SecureStore</h4><p>Several methods have been renamed:</p><ul><li>setValueWithKeyAsync →setItemAsync: The order of the arguments has been reversed to match typical key-value store APIs. This function used to expect (value, key) and now expects (key, value).</li><li>getValueWithKeyAsync →getItemAsync: Trying to retrieve an entry that doesn’t exist returns null instead of throwing an error.</li><li>deleteValueWithKeyAsync →deleteItemAsync</li></ul><h4>Payments on iOS</h4><p>We’d previously announced Stripe support on iOS as part of our experimental DangerZone APIs. The Payments API was using the Stripe SDK on iOS. We learned that Apple sometimes rejects apps which contain the Stripe SDK but don’t offer anything for sale. To help your App Review process go more smoothly, we’ve decided to remove the Stripe SDK and experimental Payments API from apps built with the Expo standalone builder. We’re still excited to give developers a way to let users pay for goods when they need to and we’ll announce more ways to do so shortly.</p><h3>Bugfixes</h3><ul><li>Camera now generates blank images in emulators/simulators instead of erroring</li><li>Text-to-speech is initialized lazily, which prevents native crashes that occurred in some situations on Android</li><li>Google sign-in has received several fixes for standalone apps; the “system” behavior should now work as expected</li></ul><h3>Library Updates</h3><ul><li>Lottie has been updated to version 2.2.0.</li></ul><h3>XDE &amp; exp Developer Tools</h3><h4>Improved error logging with stack traces</h4><p>Unhandled promise rejections should now print a stack trace in XDE and exp!</p><p>Stack traces are now included on console.warn and console.error . These stack traces are collapsable in XDE, and are truncated to a subset of stack frames in exp. If you console.log an error object, the stack trace is included there as well.</p><h4>Better error messages when using Node APIs</h4><p>It’s pretty common for an app to hit an error when adding libraries that are intended to be used in Node rather than React Native. Our developer tools will now attempt to print a specific error message if the error was caused by a missing Node API.</p><h4>LAN IP works correctly with Node 8+</h4><p>In some situations, the “LAN” setting was failing with Node 8. This was a problem with a dependency we used for detecting the machine IP address, and has been <a href="https://github.com/expo/xdl/commit/99660a1c3803c187df29dea791b7789dc643c9b3">fixed</a>.</p><h3>Upgrading Your App</h3><p>Here’s how to upgrade your app to Expo SDK 21.0.0 from 20.0.0:</p><ul><li>Close XDE or your exp CLI server</li><li>In app.json, change sdkVersion to &quot;21.0.0&quot;</li><li>In package.json, change these dependencies:<br>- react-native to &quot;https://github.com/expo/react-native/archive/sdk-21.0.2.tar.gz&quot;<br>- expo to &quot;^21.0.0&quot;<br>- react did not change from SDK 20(&quot;16.0.0-alpha.12&quot;)<br>- jest-expo to &quot;^21.0.0&quot; (if you use it)<br>- sentry-expo did not change from SDK 20(&quot;~1.6.0&quot;)</li><li>Delete your project’s node_modules directory and run npm installagain (or use <a href="https://github.com/yarnpkg/yarn">yarn</a>, we love yarn)</li><li>Reopen your project in XDE and press “Restart” to clear the packager cache, or run exp start -c if you use use exp.</li><li>Update the Expo app on your phones from the App Store / Play Store. XDE and exp will automatically update your apps in simulators.</li><li>Make sure to check the breaking changes section of this post!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be33b79921b7" width="1" height="1" alt=""><hr><p><a href="https://blog.expo.dev/expo-sdk-21-0-0-is-now-available-be33b79921b7">Expo SDK 21.0.0 is now available</a> was originally published in <a href="https://blog.expo.dev/">Exposition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expo Sketch → Expo Snack]]></title>
            <link>https://blog.expo.dev/expo-sketch-expo-snack-a444f8dec72b?source=rss-44f114aaf91a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a444f8dec72b</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Adam Perry]]></dc:creator>
            <pubDate>Sat, 01 Apr 2017 00:51:05 GMT</pubDate>
            <atom:updated>2017-04-01T01:37:12.487Z</atom:updated>
            <content:encoded><![CDATA[<p><em>TLDR: We’re making </em><a href="https://snack.expo.io/"><em>Expo Snack</em></a><em> the official name of our prototyping tool which we first released as Sketch.</em></p><h3>Sketch</h3><p>About 2 weeks ago, we <a href="https://blog.expo.io/sketch-a-playground-for-react-native-16b2401f44a2">launched Sketch</a>, a new tool for prototyping and sharing React Native screens, inspired by CodePen, JSFiddle and others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*clvaN4mu08uKWczobqOY3w.png" /></figure><p>We were really thrilled to see the community’s response:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*FqAuCvYblok9_KYpDGsnNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qiVvnT5NtyzL-x_y-FpKkA.png" /></figure><p>We’re also incredibly excited by how much use it’s getting. In the last two weeks, we’ve seen <strong>tens of thousands of sketches</strong> saved for sharing, and users have collectively spent over <strong>100 days</strong> on the Sketch site.</p><p>It’s been used in <a href="https://github.com/facebook/react-native/issues/13025">multiple</a> <a href="https://github.com/facebook/react-native/issues/13221">bug</a> <a href="https://github.com/facebook/react-native/issues/13159">reports</a> on the React Native repository to provide easily accessible reproductions of reported issues.</p><p>We’ve also been incredibly flattered that the team building the Apollo Client GraphQL library is <a href="http://dev.apollodata.com/">using Sketch on their landing page</a> to demo their product:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_WR0iXVGU9QuC71DDhQIg.png" /></figure><p>And we’re very eager to see where it shows up next! We have a bunch of plans for improving the product, and we think more and more Expo and React Native developers will find it useful in their day-to-day work.</p><h3>Naming is Hard</h3><p>We’d be remiss in talking about the success of this project without acknowledging a major issue: the name. When we were building Sketch, we were aware of the name collision with <a href="https://www.sketchapp.com/">Bohemian Coding’s Sketch product</a>. We absolutely adore their app, and in a case of sketch-ception, the design and mockups for Expo Sketch were in fact made in Bohemian Coding’s Sketch. At the time, we thought that the two tools served such different purposes and are so dissimilar that there wouldn’t be any confusion.</p><p>We were wrong about that, and lots of people let us know in a <a href="https://news.ycombinator.com/item?id=13868885">diverse</a> <a href="https://www.facebook.com/groups/react.native.community/permalink/942412302561015/?comment_id=943046739164238">set</a> of <a href="https://www.reddit.com/r/reactnative/comments/5zefu5/sketch_a_playground_for_react_native/">venues</a>. While many commenters were *<em>ahem</em>* not particularly diplomatic, it was important to hear the underlying concern that the potential for confusion was much greater than we’d expected.</p><p>We grew increasingly certain that we’d want a new name so that there’d never be confusion from teammates’ talking about “sending over that sketch demo for the Sketch mockup,” and so that we’d leave open the future possibility of integrations between our product and Bohemian Coding’s.</p><h3>Snack</h3><p>We originally picked Sketch as the name for a lot of reasons, and wanted to have a new name that would still capture many of those but also didn’t cause users any confusion.</p><p>We think <strong>Snack</strong> is a pretty good name, and have decided to rename Sketch to Snack. Anyone familiar with Expo’s recent history will know that we have a <a href="https://blog.expo.io/exponent-expo-b172fb6725a7">bunch of practice renaming things</a>, and this should go pretty smoothly. Links to <a href="https://sketch.expo.io/">https://sketch.expo.io</a> will continue to work (go ahead, click it!), as will any previously generated embed codes.</p><h3>New feature: embedding!</h3><p><em>Did he just say embed codes?</em></p><p>He did! We hadn’t announced this formally yet, but if you have been using Snack recently, you may have noticed that after you save your snack you’re presented with an option to generate an embed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*im4ZrhT1Wp5o-q1gBrFCqg.png" /><figcaption>The button bar after saving a Snack</figcaption></figure><p>Clicking <strong>Embed Code</strong> will present you with a modal:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YOgWKB9gMNvCUz3edwLsuA.png" /><figcaption>An embed preview with the code available to copy</figcaption></figure><p>This embed code is what’s used on the Apollo landing page I linked above. If you want to embed a React Native demo anywhere on the web, try it out!</p><h3>Let Us Know What You Think</h3><p>Talk to us! We’re reachable in several places:</p><ul><li>The comments here</li><li><a href="https://mobile.twitter.com/expo_io">Twitter</a></li><li><a href="https://forums.expo.io/">Expo community forums</a></li><li><a href="https://slack.expo.io/">Expo community Slack</a></li></ul><p>What would be a killer feature for you to have when using Snack? Yes, we know that you would like to be able to include any NPM package! We’re looking into it. What else?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a444f8dec72b" width="1" height="1" alt=""><hr><p><a href="https://blog.expo.dev/expo-sketch-expo-snack-a444f8dec72b">Expo Sketch → Expo Snack</a> was originally published in <a href="https://blog.expo.dev/">Exposition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>