I've been doing research into how well sites that use popular JavaScript frameworks and libraries perform and built this to make it easier for anyone to see.
This probably goes without saying, but perf.track isn't an exercise to compare the performance of frameworks against each other. There are way too many variables that need to be considered before that can be done, and I built this to instead provide trends and insight to both framework authors and developers.
I like the idea and love the simplicity. Not sure if I would benefit from not looking and editing as I write as I tend to do that all the time, but I'm going to try it with this and see how it pans out.
We're writing it so that new newcomers to React can still pick up the fundamentals of the API while learning React Native at the same time. However, the content is geared towards developers who have at least a basic understanding of JavaScript, so you may need to pick up some of the core concepts of the language first before purchasing a book like this.
With that being said, our first chapter is free and goes through building a stand-alone app from start to finish. You can definitely give that a shot first if you're still unsure :)
That's definitely up to you. The second chapter of this book shares a lot of the fundamentals in one of the earlier chapters in Fullstack React on core concepts of the React API. However if you feel like you would benefit from learning how to build web applications with React first - that can definitely be a better starting point. Otherwise if you're considering building iOS/Android apps with RN without much prior experience with React, this book will be just fine as we don't expect our readers to be proficient with React :)
This really is an addictive game and the attention to detail is amazing. As a web developer myself, I'm quite familiar with building a typical web application but nothing close to this. If you ever decide to write a piece explaining how you built this at the high level, peeps like myself will find it extremely valuable.
Every currently available client that I tried to use was either too simple (single-feature), required payment for the most basic of features (such as commenting on an issue) and/or didn't have the best UI. For all of these reasons, I built GitPoint.
I launched the iOS version of the app two weeks ago and we've already picked up a decent number of users (~3000). With some amazing contributors, we've added a number of new features since then as well as publish the Android version just yesterday!
Please don't hesitate to leave feedback of any kind!
Every single GitHub client I tried to use on iOS was either too simple (single-feature), required payment for the most basic of features and/or didn't have the best UI. That gave me enough reason to build this.
GitPoint is built with React Native and although there are quite a few things that still need to be added to the app [1], launching an Android version is my top priority.
I know the first thing almost everyone would think about before downloading an application like this is security. To use GitPoint, you have to allow the application to authorize your account in order to have complete read/write access to user and repository information. To alleviate any concerns, it's virtually impossible for me to access any user data even if I wanted to with the way the app is set up. Once a user authenticates, their access token gets persisted (with encryption) to the AsyncStorage of their own device and there is no way I would be able to retrieve that sort of information.
As always, I would appreciate feedback of any kind whatsoever :)
I loved React Native Express for being such a concise and useful tutorial to learn with so I'm super glad you made a React version. Really looking forward to going through this when I have the time, looks like an outstanding job.
Genuinely can't thank everybody for all the feedback. A lot of you mentioned that we're not comparing apples to apples here, and you couldn't be more right. I take full responsibility for this, and I really apologize if the site's design made it look that way.
Each of the implementations were built at a completely different time by different authors and are not representative as official library implementations at all. In no way was it our intent to make it seem like a reference of performance comparison between the different libraries, so again I apologize if it comes across that way.
We do need to standardize each of the apps so that they can actually be compared, but until then we'll need to make sure that things are more transparent. In the next few days we'll add some changes to how we display each of the implementations for this [1].
This probably goes without saying, but perf.track isn't an exercise to compare the performance of frameworks against each other. There are way too many variables that need to be considered before that can be done, and I built this to instead provide trends and insight to both framework authors and developers.