We just released React Native Paper 2.0

- Material Design 2.0

- Accessibility improvements

- RTL Support

‍️- New components

Check it out and don't forget to give us a star!

The browser communicates with the device via PubNub to send the code. So it needs to be open when previewing the app. But being able to view it on the phone without the browser is useful. Thanks for the feedback.

You cannot do that right now. There are a few libraries already bundled which you can use. But we are planning to work on adding this feature.

Or maybe if I create a custom component inside sketch, it would be nice if it's added as a template in the components toolbar.

That's a great idea! We need to add an accounts system before we can do that, but I'll add that to our list.

We show the QRCode because you need to scan it and open on the phone to be able to view it.

Yeah, we will change the styles to make it more obvious that it's modal. Sorry for the confusion.

I opened the QR code with a QR reader, because when I say the app-store buttons, I assumed the QR code was for downloading the app.

You could:

1) Have the QR code contain a real URL, with the Expo ID appended as a querystring.

3) On the server, redirect to the appropriate app-store depending on the browser used to open the URL, or open sketch if installed.

3) Have Expo interpret the querystring to open the correct "sketch".

I totally disagree with the previous commenter. The real wow with your app comes from installing it, and the barrier is fairly low. Granted it crashed somewhere in the setup between installing expo and sketch, but wow the real time updates on the phone are pretty mind blowing. I say stick with it and don't listen to everything everybody says =).

I actually lost interest and closed the tab when I saw the QR code.

How else would they do it? QR code seems justified in this case.

Sorry, I should have clarified.

I'm not against using QR codes. I just didn't realize that I could close the modal window, and thought that I had to jump through hoops to try out Sketch.

Given the amount of crap that can be found on the internet, I have a very low threshold for losing interest.

A better approach would have been to remind me later than I can scan a QR code to access the page on my mobile device.

The thing is that you need the Expo app on your phone to even try it out. Just closing the modal will show you the code but nothing else unless you installed the app and scanned the QR code.

I understand your point though. I suppose they can improve it.

1. People want to preview the app once they have something to preview. That would probably be a more appropriate time to remind them they can see it on their phones.

2. QR codes are scary (at least for most in the American market; other countries could be different). Instead of a QR code, show a random string the user has to input. We are all used to inputting random numbers/string when doing 2-factor.

1. The point of this is it happens in real time. It starts setup with an actual working demo. Connecting it to your phone first shows that real time update 2. This is an app for developers. Developers are not scared of QR codes.

Exponent is super cool. Super simple to start building an app. I wish I could use it for every RN project I work on. The team is very responsive too. Totally recommend.

Can you elaborate on why you cannot use it for every RN project you work on?

> I am so flabbergasted that I took the idea seriously, looking at what it actually is, it is so clear to me that this is not going anywhere.

Facebook is using RN in production. So I doubt it.

> Then, there is no real data layer at all! You have to interface with Objective-C!

I don't get what you mean. You don't have to interface with any native code if you don't have a very specific need to use a platform specific feature which is not available in RN.

> I just spent 5 minutes looking at React Native and my first and final impression is that this is a complete waste of time.

If you spent just 5 minutes, it clearly means that you don't have enough experience with React Native, and I don't think you should give opinion on anything without at least being familiar with it. I've been working with React Native for months, and yeah, there are technical hurdles. But I'd say the same for Android, or web (I don't have any experience with iOS dev).

There are parts of React Native that suck. But there parts which are amazing. Amazing enough that I'll choose React Native over Java/Obj-C any day. The development speed with React Native is much faster than native Android dev. The DX is getting better day by day.

I get to share code isn't the primary reason why I love React Native, but it's an important thing for companies which want to support multiple platforms.

I'd say let's focus on fixing the parts that suck in React Native, rather than discarding a new tech without even trying it.

Ok hold on, you've been working with it for months? To what end?

Please tell me you're not using a library that's at 0.20 for production.

So you're using ReactNative for pet projects right?

As soon as you get to writing a real app that's beyond a to-do list, you'll be in a world of pain. Just start with having no support for a sqlite/database or an orm layer on top of it, only a key-value store as your first massive and insurmountable stumbling block.

> Please tell me you're not using a library that's at 0.20 for production.

I'm using it in production. And so is Facebook.

No, it's not a pet project, and much more than a TODO list app.

It has been fixed in the new client. Check http://next.scrollback.io