Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React Native for Android

code.facebook.com

Post reply on HN
Print view View original

231–240 of 248 posts

Re: React Native for Android

#231

Post by wasd »

aikah wrote: post #124
wasd wrote: post #91

Slightly off topic but I'm curious about using React Native vs WebView with native wrapper and components. I'm a developer who primarily codes in Ruby. I'm working on a side project that will be mostly CRUD and have no DOM updates. The application will need to support web, mobile, and tablet. I'm considering using React so I can use React Native but I'm afraid I'm adding a level of unnecessary complexity. Originally,…

do you need a mobile app or a mobile website ? that's the first question you need to ask yourself.

Dumb question but suppose I need a mobile app. Then what question do I ask myself after :)?

Re: React Native for Android

#232

Post by muzmath »

aikah wrote: post #161
muzmath wrote: post #156

Earlier quoted context omitted.

Do you consider a facebook production app a least common denominator?

Do you really believe the facebook production app is built 100% with React Native ?

Did you read the article before downvoting me?

Let me spell this out for you...

A Facebook app, is an app made by facebook, which obviously i'm referencing the one that they are talking about in the article your commenting on. And yes, it was made using React Native. Any more questions before you read the article?

Re: React Native for Android

#233

Post by muzmath »

sehr wrote: post #183
aikah wrote: post #179

Earlier quoted context omitted.

Ads Manager =/= Facebook app for "users"

I think I see where the confusion is, muzmath said 'a' facebook app (i.e. Ads Manager), not 'the' facebook app. Main FB app is definitely not using 100% react native. That being said, Ads Manager users are still mostly just "users". I know a middle aged woman using it to manage ads for her side business for example, regular people are using 100% React Native apps daily.

Your right, when I say a facebook app, I literally mean an application, developed by facebook.

Re: React Native for Android

#234

Post by lewisl9029 »

pjmlp wrote: post #210
lewisl9029 wrote: post #117

Earlier quoted context omitted.

I was mostly referring to development paradigms and methodology in my original post, but in terms of tooling, I personally haven't see any tooling on the native side even approach the increased productivity provided by the instantaneous feedback loops that countless hot-reload implementations can offer for the web. https://github.com/gaearon/babel-plugin-react-transform/ http://gaearon.github.io/react-hot-loader/ htt…

You mean like development with Smalltalk and commercial Common Lisp environments? Or designing GUIs WYSIWYG with Delphi, XAML with Blend, the UNIX 4GL in the 90?

Yes, Smalltalk and Common Lisp environments probably did offer similar experiences.

Tooling for web development has probably been heavily inspired by the tooling available for CL and Smalltalk, but I don't think it's fair to say it's still playing catch up. The tooling ecosystem for the web has long since caught up to the best native ever had to offer, and is now advancing the state of the art faster than any other tooling ecosystem out there today.

Re: React Native for Android

#235

Post by aianus »

andreamazz wrote: post #224
aianus wrote: post #34

Earlier quoted context omitted.

Unfortunately everyone writes iOS first nowadays because rich people overwhelmingly own iOS devices.

That, and because development is way easier.

I'm curious why you say that.

You have to learn a whole new Apple-only programming language to do iOS (Swift or Objective-C) in addition to the iOS framework/libraries. Not to mention buying a Mac and paying Apple $100 for a developer account.

Android, on the other hand, was pretty straightforward to get started with for me as someone with Java experience.

Re: React Native for Android

#236

Post by kbutler »

windsurfer wrote: post #189
GrinningFool wrote: post #159

Earlier quoted context omitted.

> This not a big deal when pushing layout around a webpage, > but it can be crippling for app development as the app > grows in complexity and you crave native-quality > interactions Even on the fastest phones, web-based (including wrapped web components) simply don't offer the native experience. They come close, but there's always a slight but perceptible performance difference; and often a visual difference dependi…

> Even on the fastest phones, web-based (including wrapped web components) simply don't offer the native experience. They come close, but there's always a slight but perceptible performance difference Honestly I used to believe this, but not after the release of the iPhone 5 and 6. Though there is no perceptible difference, it takes a lot of work to mimic the UI in terms of animations, opacity, and response actions,…

I'd like to believe that, but can you cite some web-app or webview-based example applications?

Re: React Native for Android

#237

Post by whatever_dude »

volent wrote: post #206

"OS X - Only OS X is currently supported" Why is this becoming popular ?

Yeah, it made me really sad. This is not a comment on this project specifically, but it seems to be the way the world is going - so many platform specific dependencies that even a cross-platform project is made specifically with one development platform in mind and that is considered normal.

I've been in Windows for a long time and it uses to be the opposite a long time ago - everything would be released on Windows only and Macs were left abandoned - so I guess I'm seeing the other side now. Not a super fan of Microsoft, but still annoyed I'll have to eventually switch just because of stuff like this.

Re: React Native for Android

#238

Post by ufmace »

lispm wrote: post #216
lewisl9029 wrote: post #152

Earlier quoted context omitted.

Filesystem watching is only part of the equation though. Live reload has been available for the web and various other platforms for a long time, but the traditional approach to live reloading does not preserve application state. These new hot reload implementation allows your app to be reloaded with your new changes without affecting the state of the application, and is not practical unless your application has been…

That's why Common Lisp / CLOS has functionality like * CHANGE-CLASS (change the class of an object to a different class), * update-instance-for-different-class (updating the object after a class change, one can provide methods which will be lazily called when needed), * update-instance-for-redefined-class (updating the object after redefining a class, one can provide methods which will be lazily called when needed),…

Which can be really cool, but has its downsides:

Hey cool, I can change these classes live!

Let's solve this tricky problem by changing the class at runtime. Cool, it works, now on to the next problem.

2 years later...

What's causing this super-weird bug? It's like the code isn't doing what it says at all.

1 week of debugging and head-banging later...

Oooh, something got screwed up in that runtime class change code. Fixed.

2 years later, repeat...

Re: React Native for Android

#239

Post by whatever_dude »

rail2rail wrote: post #67
jbigelow76 wrote: post #15

Earlier quoted context omitted.

Why aren't Apple and Google making it this easy to develop apps? Apple has no incentive to make it easier for app developers to port their code to other platforms.

Has Apple ever chosen a non-native app for its annual design awards?

You mean not including the vast number of Unity based games that are there?

Re: React Native for Android

#240

Post by tracker1 »

bad_user wrote: post #181
lewisl9029 wrote: post #87

Earlier quoted context omitted.

Speaking as a web developer, this is sad, but true. However, what's even sadder to me is the fact this continues to be true despite the fact that, believe it or not, the web has been the platform where most of the innovation in UI development paradigms has been taking place in the past few years. And I don't just mean in terms of the sheer number of new things coming out. The web community pioneered UI development pa…

I was pleasantly surprised that the latest Chrome for Android delivers push notifications for Facebook due to a new W3C API, and Facebook's mobile web interface has been in good shape for some time, so right now Facebook's native app is completely optional. Which is a good thing, given how many permissions Facebook's app requires. Apparently this was announced back in April, but I just noticed it, due to Facebook bei…

I disagree... They've removed functionality from the mobile web interface. Specifically, I'm unable to tag friends when sharing a post. When I share a video link (youtube, etc) it no longer creates a thumbnail or embeds the link as it does on desktop web. I'm unable to tag friends inside new/shared posts, only in comments.

I won't use the full client because it eats my battery, and they separated the messenger interface requiring yet another app with battery eating features.

Post reply on HN