MrAwesomeSauce

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.

Great job!

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 :)

Co-author of the book here.

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 :)

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.

Thanks a million, happy to have Android out so soon since so many people have been waiting.

Thank you, I'm glad you like it so far! :)

Hi HN community,

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!

Hi HN, author of the app here!

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 :)

[1] Issue List: https://github.com/gitpoint/git-point/issues

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].

[1] https://github.com/tastejs/hacker-news-pwas/issues/36

Scratch that, according to this issue (https://github.com/Polymer/hn-polymer-2/issues/3) it may not be an API issue and is probably because of stale service worker data not being refreshed.

Thought it may have been because of a different API but looks like the service worker is configured to always return the fastest retrievable data, hence why it's obtaining stale data from the service worker cache.

Issue has been opened for it: https://github.com/Polymer/hn-polymer-2/issues/3

Nope never mind, navigating within the app works but navigating out back to hnpwa.com doesn't. I'm noticing the same on Chrome desktop and iOS safari.

Opened an issue for it: https://github.com/sveltejs/svelte-hackernews/issues/10

Yep you're 100% right, that's something we've discussed [1] and definitely something we still need to do [2].

[1] https://github.com/tastejs/hacker-news-pwas/issues/7#issueco... [2] https://github.com/tastejs/hacker-news-pwas/issues/4

The browser back button? Hmmm it seems fine for me, not noticing any weird behaviour.

Not all of the implementations are using the same API hence why the data isn't displayed the same on each :P

We've discussed standardizing the specifications [1] for each of the apps which covers how they're hosted, how they fetch their data, etc... That's something we still need to do so hopefully sometime soon we'll have each of the apps standardized similarly.

[1] https://github.com/tastejs/hacker-news-pwas/issues/7#issueco...

Thanks for pointing this out! I had thought they all fit mobile devices just fine but I'm most probably wrong. They should all definitely be fully responsive on mobile, feel free to log an issue on their implementations if you would like to :)

As others mentioned, throttling your settings will show you that the differences actually aren't that negligible. With the Chrome devtools, throttling network connections to Regular 3G and CPU slowdown to 10X will give you a rough estimate of how mobile devices with flaky connection interact with these applications.

Another thing is that each of these implementations pre-cache most (if not all) of their static resources with a service worker -> and that's why repeat visits on each site is quite fast. Using incognito or clearing the site data and unregistering the service worker and then loading the site as a first-time visit under those throttled conditions will let you easily notice how much faster some of the implementations are then others (for example: Preact and Angular)

Would be great to have Elm on there as well! Contributions are open to any Hacker News implementation that meets the specs :)

I do somewhat agree with the opinion of making it open source. Imagine how much better the platform could be with constant developer input. But I understand that might not be an easy decision to make.

I've used DatoCMS and I actually really liked it. However the pricing model is quite steep for the service it provides. I feel that if open sourcing isn't in the horizon, at least consider expanding what the Free and Basic models provide.

Yeah I was thinking the same thing, there was another post discussing the same topic which also picked up traction fast and after a day it seemed buried and gone. Very bizarre.

This is the third most popular story in Hacker News of all time [1], and I couldn't be happier. This can't have been easy to write but the more posts like this, the more likely people who suffer the same issues at their workplace will share their experiences.

[1] https://hn.algolia.com/?query=&sort=byPopularity&prefix&page...

I see you've added a few things after I put up my PR! I like how you've added a little dropdown up top to select a different city and not have to repeat the whole thing :)

This looks great, however results aren't showing at all for some reason :( (on mobile)

Will take a look at it on my laptop when I reach the office, but this is a great idea and something I've been thinking would be super useful if I had!

This really is amazing. Probably one of the best clients that's out there at the moment. I recently built a one myself with Angular (https://github.com/hdjirdeh/angular2-hn) so I'm always amazed with all the different clients out there with their own unique twist.

I've always been interested in using Vue, how do you like the framework? Also, which Hacker News API are you using to power this? I'm on mobile so I can't see any of the requests at the moment. But since this is SSR, I probably wouldn't be able to see the API calls anyway.

If you can't provide proper criticism, then keep your opinions to yourself. This is a simple Todo app that OP built as a side project, not sure what you were expecting.

Yeah I still think there's room for improvement, and I'll be looking into different ways to make it faster (server side rendering being one of them)

Fixed

Yep, that's definitely the next thing I need to think about. I agree, this is something that needs to work with JS disabled.