Redis pub / sub has worked fantastically for me - reached 100k+ concurrent users with ~80 msg / sec, but benchmarked much higher. It was the easiest, fastest, and most reliable solution I found (about ~4 years ago)
In this app I did not have to worry about that, but I can recommend https://github.com/sunnylqm/react-native-storage for dealing with storing on the device if you want to manually do things. I haven't built an app with React Native yet that does rely on local storage; however, with Redux and the redux-storage library it should be no problem
I do very much like Redux, but definitely that whole data flow layer can be intimidating. Wes Bos has a great free course on react / redux ( https://learnredux.com/ ) that can help that learning process, and there is the excellent courses on https://reacttraining.com/ if you are willing to invest a little bit of money on learning.
With all that said, you don't _need_ to use Redux or anything else to work with storing data. It might be a good idea to try manually storing with the aforementioned storage library just so you can get something working and feel like you're making progress; and then spending some time with Redux and (https://github.com/michaelcontento/redux-storage
provides support for storing data with react native). Good luck!
Yes, quite easy! I have very little android dev experience. Android integration was excellent, I had zero issues. It was easy to ship to the play store (faster and less painful than iOS. And if you need to modify something, you don't need to wait days to get it re-approved).
For errors I'll always log the full stack trace (in JS, at least). This helps a ton for when errors occur, but I find that often times it's not explicit errors that are a problem (e.g., making sure the right message is sent and received from a queue system). Of course, setting breakpoints can give more information, but it's not always obvious where a breakpoint needs to be set (e.g., when a new person comes on the team) - for me, logging points me to where I need to set breakpoints, speeding up my development time.
I'll be posting a follow up about the machine learning bit in the near future. It uses not just words, but also phrases. For the meme / buzzfeed posts, more weight is given to content you write vs. links / articles you post (and we only take into account what you say if you do share a link, not the content the buzzfeed post itself).
It doesn't really try to distinguish sarcasm. Depending on the sample size (ours used 75k people with ~750m words / phrases), it could conceivably detect sarcasm. Yeah, totally. /s (Maybe, but probably not)
canvas can better handle drawing thing which involve tons of objects, as you're working with pixels instead of DOM elements. here's an example of canvas being used for parallel coordinates: http://bl.ocks.org/syntagmatic/2420080
Very cool! D3 was intimidating to me, and personally screencasts similar to this are helpful when trying to get a broad overview of a library. Even better, all the code for each video is provided with a live code editor.
Thanks! You're not thick, it's just that this isn't really the best visualization choice for the data since the rings are independent and not hierarchical (like in http://mbostock.github.com/d3/ex/sunburst.html).
You are absolutely right about the scale for the bar charts, oversight on my part which I have fixed now. The adding to 99% is a rounding error (you can see the fully number value by mousing over a bar) - thanks a ton for your feedback!
