6 ms·

It sounds like you're new to both React Native and the JavaScript ecosystem. I can imagine this being very frustrating for someone regardless of their general p

It sounds like you're new to both React Native and the JavaScript ecosystem. I can imagine this being very frustrating for someone regardless of their general programming chops. I happen to be on a React Native project at work right now. Hopefully I can provide a viewpoint that is helpful and give direct answers to some of your questions. One thing that would be helpful to understand that's missing from the OP, what are you building? > However, seeing the differences between react and react native, this seems overstated. I'm actually not sure which specific differences you're referring to. Perhaps you can clarify? > It was recommended to use javascript and react/react native so I only needed to program once. It's possible to use RN to build an application which runs on both Android and iOS from a single code base. This is possible with a few other environments but none are (IMO) quite as good at affording for a truly native look and feel including dropping down into native code when necessary. Building a really great app is still a grind on execution and perfecting small details is a chore. The standards of quality in the mobile app world are high which leads to average users having higher standards than they might with desktop or web applications. > What were the other benefits? For people who enjoy working in JavaScript, the fact that you can write native applications using mostly JS is a benefit. Some products benefit from being able to share code between a web product and a RN application is a big boost in productivity. I've personally saved hundreds of hours leveraging this. It's not a 1:1 swap but it's close enough to lower the mental burden compared to creating something from scratch. > I thought there was already built components/libraries I could drop in for data management. There are lots of data management libraries for React. Most can be used in a RN app. Maybe the community resources section of the React documentation will be helpful: https://reactjs.org/community/model-management.html https://reactjs.org/community/model-management.html I can provide specific recommendations if you can describe specific needs. Like most ecosystems deciding which tool to use in which situation is a skill which builds up with experience.

mkirklions 9y ago
Here is too much information, but this is how I spend my evenings now... Goal is a finance tech app, although I probably just need a pretty front end, and I can do stuff manually in the background (like invest money, wire transfers, etc...). I do have some database experience, writing to mysql. Was planning on doing that using LAMP, because I have experience already. Features needed: >write to database(should be easy with my previous experience) >Usernames/passwords(I am actually clueless how to start doing this, I have Wordpress if needed) >Accept payments(but again, I can probably do this through wordpress if its too time consuming). Other specs, since its finance and people are going to be putting money into it, its gotta look and feel good. I'm willing to invest many months into building this to be perfect. However, progress feels slow since I'm learning the new javascript react-native syntax. Any tutorials you recommend? Working through the facebook tutorial right now. last trivia question- I was considering using Reflux, but I saw an article saying reflux is dying. I've heard facebook is especially brutal with changes.
- jey 9y ago
  > I was considering using Reflux Redux is the de facto standard now in that space. It seems to have "won". See https://stackoverflow.com/questions/36326210/what-is-the-core-difference-of-redux-reflux-in-using-react-based-application https://stackoverflow.com/questions/36326210/what-is-the-cor... for further discussion.
  - matte_black 9y ago
    Nope, sorry those days are over. Redux is on it’s way out, please refer people to this: https://react-etc.net/entry/rip-redux-dan-abramov-announces-future-fetcher https://react-etc.net/entry/rip-redux-dan-abramov-announces-...
    - jakelazaroff 9y ago
      This article puts a pretty hard spin on what actually happened: Dan Abramov did not announce a "replacement for Redux", nor is he developing a "Future Fetcher" library. The React team is working on a feature that defers state updates until an asynchronous operation is finished, but we don't know how it'll fit into existing state management solutions. Here's the official blog entry and talk where these features were announced: https://reactjs.org/blog/2018/03/01/sneak-peek-beyond-react-16.html https://reactjs.org/blog/2018/03/01/sneak-peek-beyond-react-...
    - acemarke 9y ago
      I'm a Redux maintainer, and that post is utterly and completely wrong in every way. What Dan Abramov showed at JSConf Iceland was a pair of demo apps that illustrated upcoming improvements in React related to async rendering and data cache handling. Those features have no bearing on whether or not you use Redux, and are certainly not "replacements" for Redux. The linked tweet from Kent C Dodds was a joke tweet in a joke discussion thread, and the author of that site has repeatedly shown that either they don't understand the React world, they are very bad at writing and researching, or that they're just flat-out trolling. There's certainly been plenty of discussion lately about when it's appropriate to use Redux, and I'd agree that many people are told to use it blindly without understanding what the tradeoffs are. It's also true that the new React context API (available in the upcoming React 16.3 release) means you won't need to pull in Redux _just_ to avoid "prop-drilling" data all the way down the tree. However, Redux is absolutely not deprecated and not being replaced, and the React team isn't in charge of Redux anyway. Dan Abramov and Andrew Clark, the co-creators, are both now part of the React team, and are no longer active maintainers - Tim Dorr and I are. We _do_ still talk a lot about what the future plans are for Redux, and in fact right now we're working on updating the React-Redux library so that it properly works with the "async rendering" capabilities once those are released (see discussion [0] and an early WIP PR I filed yesterday [1] ). [0] https://github.com/reactjs/react-redux/issues/890 https://github.com/reactjs/react-redux/issues/890 [1] https://github.com/reactjs/react-redux/pull/898 https://github.com/reactjs/react-redux/pull/898

mkirklions 9y ago

Here is too much information, but this is how I spend my evenings now... Goal is a finance tech app, although I probably just need a pretty front end, and I can do stuff manually in the background (like invest money, wire transfers, etc...). I do have some database experience, writing to mysql. Was planning on doing that using LAMP, because I have experience already. Features needed: >write to database(should be easy with my previous experience) >Usernames/passwords(I am actually clueless how to start doing this, I have Wordpress if needed) >Accept payments(but again, I can probably do this through wordpress if its too time consuming). Other specs, since its finance and people are going to be putting money into it, its gotta look and feel good. I'm willing to invest many months into building this to be perfect. However, progress feels slow since I'm learning the new javascript react-native syntax. Any tutorials you recommend? Working through the facebook tutorial right now. last trivia question- I was considering using Reflux, but I saw an article saying reflux is dying. I've heard facebook is especially brutal with changes.

jey 9y ago
> I was considering using Reflux Redux is the de facto standard now in that space. It seems to have "won". See https://stackoverflow.com/questions/36326210/what-is-the-core-difference-of-redux-reflux-in-using-react-based-application https://stackoverflow.com/questions/36326210/what-is-the-cor... for further discussion.
- matte_black 9y ago
  Nope, sorry those days are over. Redux is on it’s way out, please refer people to this: https://react-etc.net/entry/rip-redux-dan-abramov-announces-future-fetcher https://react-etc.net/entry/rip-redux-dan-abramov-announces-...
  - jakelazaroff 9y ago
    This article puts a pretty hard spin on what actually happened: Dan Abramov did not announce a "replacement for Redux", nor is he developing a "Future Fetcher" library. The React team is working on a feature that defers state updates until an asynchronous operation is finished, but we don't know how it'll fit into existing state management solutions. Here's the official blog entry and talk where these features were announced: https://reactjs.org/blog/2018/03/01/sneak-peek-beyond-react-16.html https://reactjs.org/blog/2018/03/01/sneak-peek-beyond-react-...
  - acemarke 9y ago
    I'm a Redux maintainer, and that post is utterly and completely wrong in every way. What Dan Abramov showed at JSConf Iceland was a pair of demo apps that illustrated upcoming improvements in React related to async rendering and data cache handling. Those features have no bearing on whether or not you use Redux, and are certainly not "replacements" for Redux. The linked tweet from Kent C Dodds was a joke tweet in a joke discussion thread, and the author of that site has repeatedly shown that either they don't understand the React world, they are very bad at writing and researching, or that they're just flat-out trolling. There's certainly been plenty of discussion lately about when it's appropriate to use Redux, and I'd agree that many people are told to use it blindly without understanding what the tradeoffs are. It's also true that the new React context API (available in the upcoming React 16.3 release) means you won't need to pull in Redux _just_ to avoid "prop-drilling" data all the way down the tree. However, Redux is absolutely not deprecated and not being replaced, and the React team isn't in charge of Redux anyway. Dan Abramov and Andrew Clark, the co-creators, are both now part of the React team, and are no longer active maintainers - Tim Dorr and I are. We _do_ still talk a lot about what the future plans are for Redux, and in fact right now we're working on updating the React-Redux library so that it properly works with the "async rendering" capabilities once those are released (see discussion [0] and an early WIP PR I filed yesterday [1] ). [0] https://github.com/reactjs/react-redux/issues/890 https://github.com/reactjs/react-redux/issues/890 [1] https://github.com/reactjs/react-redux/pull/898 https://github.com/reactjs/react-redux/pull/898