This looks really interesting and I'd love to try it, but these "refer your friend to jump ahead in line" tactics are pretty annoying. Stop pushing people to share it before they've even tried it, and let them share it after they actually enjoy using it.
And by the time they email me an say that I can download I'll have forgotten what this project was and what all the hype was about making me less likely to use it and even less likely to spread the news.
We've got so many beta requests, we can't process them fast enough. So, just refer as many people as you can, and we'll bump you up somewhere in the "waiting list". Ingenious. ;-)
So I just started developing a react native Android app and a react desktop app in electron and it's actually been a very rewarding experience so far. Some thoughts I have on this:
1. I'd be interested to see the Android emulator and live reload in Deco. I'm using Genymotion and the live reload seems to work about half the time (as in I usually have to save the file twice to see my changes). It also sometimes can't connect to Chrome devtools. At some point I'll dive into webpack, genymotion, watchman, and devtools to see if I can fix these things but it'd be nice to have everything work smoothly out of the box.
2. Speaking of devtools, devtools! I could imagine some really nice UI that wraps devtools directly into Deco but I didn't see that in the video (admittedly I skipped around a little).
3. I love the built in styling bar. Right now styling for me involves having a color palette tab, a CSS reference, and an HTML/React native UI components reference tab open.
4. I have one more problem that could probably be solved with a 10 minute investment on my part: react with electron and react native require different nodejs versions. React native needs at least v4.0 and I believe electron only works with 0.12.9 and below. Currently I switch between them using "n". I suppose this problem is unique to my situation but this is also the kind of thing an IDE could handle with project settings.
Well this kind of devolved into me listing my pain points with React but I'm excited to try this editor and I just signed up for the waitlist!
To point #4, if your toplevel react+electron vs. react native projects are in distinct working directories, then you can use tools like ndenv[1] to manage node/npm versions using a .node-version file at the root of each project directory, as well as a configurable 'global' default setting. ndenv is great for this, since it uses PATH to do its work, and is therefore far more widely compatible with tooling than nvm. (nvm unfortunately requires executing within a bash w/ a mess of shell functions injected into it.)
This is interesting, definitely. One thing people should be aware of if they're new to the React Native environment is that this technology comes built in. It is a big reason why React Native is such a huge success so far. You don't need an IDE and switching to one instead of using your own tools seems like a pretty big negative to me.
Tools such as rnpm allow for automated installation of new extensions (all of which are available on npm).
Extension installation is as simple as:
rnpm install react-native-video
Deployment is now as simple as:
react-native run-android
react-native run-ios
No XCode, no Android Studio, etc. and you get live reloading, Chrome debugging, etc.
To me this is an ideal workflow, but others may disagree. Some may choose to build IDEs such as this on top of the existing architecture, that's cool too. I just want people who are starting out to be aware that there isn't much new here in terms of work flow efficiency.
Yes, for sure, a lot of the awesomeness is built into React Native. That's why we love it. Some developers will prefer an IDE, some will prefer the workflow you mentioned, and some will make their own. :)
>It is a big reason why React Native is such a huge success so far. You don't need an IDE...
Sorry if this a stupid question, but is this true if one is also targeting electron for the 'big 3' desktops for the HN crowd (rather than just mobile OSs)?
React Native is a platform for building _native_ iOS and Android apps (with no DOM (HTML or CSS)). Electron is about web apps for the desktop. Different things.
Very nifty! One question I have is that many React Native components that expose native functionality tend to have an extra step in the install process that looks like this: https://github.com/ProjectSeptemberInc/gl-react-native/raw/m... - where you have to drag in and link the library in xcode. Are these types of components handled automagically too?
I recently worked on a RN project, after months of not touching it, and found out that there's a new thing called rnpm (https://github.com/rnpm/rnpm) that solves this issue.
RNPM is pretty good, but it doesn't work with some libraries that require slightly unique initialization steps or paths. I imagine this will eventually lead to some kind of postinstall hook in the module packages, which will be picked up by RNPM.
Any info on platforms supported (Mac, Windows, Linux)? I know React Native's toolset is mostly built for OSX with some native tool dependencies (e.g. Homebrew) and am afraid this will be repeated here.
Are you sure there's an app to download? No offense but this seems like some shady promotion to just build an email list. Not one person here has said they've used the application or that they've got an invite.
Thanks for asking this question. I couldn't find it anywhere on the site. Should probably be added as a separate entry on top ("Platforms" or something).
This is one of the most useful-looking things I've seen on HN for some time, going by the video. It's a step closer to being able to live art-direct (as it were) sitting with a developer.
This is great! Helps a ton for someone new to react native, lowers the already low barrier to entry. Integration with microsoft code push (https://github.com/Microsoft/react-native-code-push) could be cool.
I'm very excited to try this out. We've built one (very simple) React Native application so far and felt like the build chain could use some improvements.
Do you plan on supporting imports instead of require?
Why not just use browser-based React inside a wrapper like Electron to build desktop apps? Is performance much better when using a desktop implementation of React Native?
This looks like a really cool piece of software, but I think a lot of it's best features should be unbundled or made available in the IDE you already use.
Namely:
* Simple package search + install without opening a web browser
* React-native hot-reloading
* Scaffolding of added components, with required props filled in
I really don't want to use a different IDE, and lose everything I've got in my current IDE - I use webstorm, so this would be Live Templates, key bindings, etc.
That said, I'm really excited to see people building software that makes building react-native apps easier. It's not that it's too difficult right now - rather, it's awesome that the development workflow is so hackable, and that the react-native (and react) ecosystems seem to be evolving so rapidly, and are so willing to try out new ideas.
I apologize that this comment is slightly off topic but does it worry anybody else that people are putting so many of their eggs in the React basket? Considering how fickle the world of front-end libraries can be..
This looks way better than things like Framer. Not only the code is more flexible (not a DSL nor their own API) but it's actually a React component that you can use anywhere. The IDE looks rad too.
This looks pretty awesome. I really like the import package feature with the scaffolding. That looks like it saves a ton of time on whatever you're building.
OR you could just install react native CLI tools, then use the BUILT IN hot module reloading (which is basically like LiveReload for web editing), and just do it yourself without this bloated piece of thing.
Now would you rather rely on something that one person made? Or would you rely on a huge group of amazing folks, which would GLADLY help you with your project, such as the folks from Discord channel or ExponentJS on Slack.
Look, you're clearly passionate about React-Native, but surely there has to be a better way to channel it than this?
How about an article explaining why it's better not to rely on on something like this, and why your way is better. Complete with samples to git clone. Then you can present it with your own thread. I am sure if you think about it, you'll realise it's a better approach.
I mean you don't need to trash someones project like a total klabnik. It's not a good way to live, trust me.
I disagree. This seems to strike a good balance between ease of use and power. It offers a visual tool for layout while still placing the code front and center.
so i need to learn IOS and Android development to learn what's going on behind the scenes as well? Ideally right? But that's definitely not a prerequisite of building RN apps. Abstractions are great if its done well..
Why the bad karma? Look, there are people that like Emacs (like me) and there are people, especially designers, that like drag-and-drop. Even if all it accomplishes is rapid prototyping, there is great value in closing the gap between UXPin and Emacs.
Haha not really, it's bloated. You end up wasting time dragging a slider when you could just put in a number and enable HMR hot module reloading which is BUILT INTO REACT NATIVE. Lol.
You've inundated this thread with uncivil and dismissive comments. I'm sure you do know a lot about this space, but the way you've chosen to express it here is not at all ok.
People go on tilt sometimes, so it's not the end of the world, but we've banned your account for now. If you don't want it to stay banned, email hn@ycombinator.com.
> There are a lot of fanboy lurkers that downvote me because they are friends of the OP on here.
FYI: I'm not a friend of OP but are down voting most of your posts here. If something, you look like the fanboy here.
I now see elsewhere that you are an active react native developer. You should be happy for people building a community around the platform, shouldn't you?
I tried to below, but I continously get downvoted by friends of the OP here. This thing is a joke, the time you spend reading about it and trying to get it installed/setup you could have already read the docs for RN, installed the ACTUAL React Native CLI tools that Facebook THEMSELVES! This is for people that are lazy, don't actualy build a product that gets anywhere, or prototype something that is actually junk and needs rewritten because they had no idea what they were doing, because they didn't read the docs that the creators of RN put SO much effort into maintaining (WITH EXAMPLES!).
I've no idea who the OP is and I've downvoted you. Your comments are rude and inflammatory. I'd imagine most of the other downvotes are from people who feel the same, rather than friends of the OP.
I did look at his repo and it's respectable. Putting aside the personality issues the way we do with Terry Davis (TempleOS) I'd like to hear his complaints about this.
Pretty easy when pretty much anything with any version of Android OS on it constitutes as "Android". For comparison, as of February 8th, 94% of all iOS devices are on iOS 8 or later, with 82% of those on iOS 9.
isn't it what technology is about? Commoditizing what was exclusive before.
I'm personally glad to see tools simplyfying building a mobile app. The end goal rarely being producing the app, and more along the lines of producing value through the app.
I hope it has as big of an impact as what WP did for custom CMS…
This product may die, however I believe competition and the fire to get what you want is more valuable than king making through bad reviews (whether intentional or unintentional). Tbh, Im not going to look at the product because Im more interested in terminal editors at the moment. But criticism should be used to enhamce a product, not degrade the blood sweat and tears that went into it
I applaud effort. I just feel there's some glaring gaps that make alarms go off. I'm sharing those. I know this looks fantastic, but that's when I start checking for a venire. And when I do, those smells popped up.
Facebook releases so fast. So when something is brand new and it's already not using the latest, I feel afraid.
The example project doesn't use the import syntax, it's using require, and feels like it's coming from ECMA5 in a brand new video. I just worry, can they keep up? Facebook releases breaking changes often so it's a valid concern.
Facebook, as well as most of the code out there, is still using CommonJS, since there are very real issues with ES6 modules that are still unresolved[1]
