You've put in the work and now you have a solid understanding of the React library.
On top of that, you have a good grasp of JavaScript and are pu...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
Great concept.
Some constructive criticism: clearly quantity over quality here. Why not build 3 apps or even 1 app but that looks like a real business. I doubt a person who knows how to build an ecommerce, social media and a chat app will not be able to build the productivity or entertainment app. More is not always better.
It would be constructive, had I not mentioned it in the article a couple of times.
That in multiple cases, only one may need to be built (see the social media app section) or that one app can incorporate several of these app types (entertainment app section).
Yep, my bad. I guess what I was referring to is how "complete and finished" the apps actually look. Unfortunate (or fortunately) in web development and the apps business in general, looks(how pretty the app looks) matter more than we think. I personally will be buying this: newline.co/tinyhouse not because the app is revolutionary o with better features than the ones you will build, but I will have an app that looks like a finished product once I finish the course.
If you're going to spend some time building these ideas, why not spend it on building something meaningful? These apps will be just glowing in your portfolio, but are totally useless. Why not solve somebody's actual problem with your skills? You might also suddenly grow a business this way.
Why do you think every developer makes the canonical todo app? From your perspective, that would be "useless". Is every developer teaching how to make a notetaker or todo app in the wrong?
To start building apps, we make what's familiar. What we use and know. And that doesn't therefore make those apps useless because we've seen them before or it wasn't an original idea. Only a very special few can start solving peoples' problems with code right off the bat. People just starting out building apps don't have a concept yet of how to structure it. That's what I've tried to do here--to get React developers to start thinking in terms of what they can build and inspire them to work on something meaningful.
I've built all of the apps that you see in the gifs above. Having these apps on my portfolio has helped me get work as an app developer and consultant. This is a proven approach to getting hired and moving ahead in your career. I bet many ambitious developers looking to get ahead would find that the polar opposite of "useless."
And finally, I want to make clear that I've echoed the need to build apps you find value in throughout the article, for example: "ask what features an app could have to make your daily schedule easier and go from there."
I mean they're useless in terms of utility - probably no one will ever use it, it will just rot in your GitHub repository. Maybe I wasn't clear enough - I don't mean they're totally useless, of course they give value in terms of getting a job. I could overlook that this is a "Learn React in 2020" series for newcomers, sorry 😅
Jakub, I directly talk about making them based off of utility. Please read the post!
Still waiting for your answer about todo apps, by the way.
Because it's an easy example to grasp the technology you want to use.
I've read the post. It doesn't matter that you talk about it. You won't use apps which you've created for your portfolio as it doesn't make any sense (there are plenty of free services out there that already solve your problem). So IMO their only purpose is to learn something, or have something to show off. They will still rot in the repository.
I disagree. It's your choice. There's no "magic" here. Just find a problem which no one solved already, or build something better than someone else.
My point is: learn to build products, not portfolios and apps to show off. Building 1 simple product and giving it to users is a much bigger achievement than building 100 example apps for your portfolio. That's my opinion 😃
I'm interested in helping people become professional React developers, get hired, and level-up in their career, not turn them into entrepreneurs.
Any app you build will be more than useful to you and your career, not counting the new techniques and tools you get a chance to try out and practice. I can't count how many apps I built where the only utility was the chance to apply a new technology that just came out.
And no, they don't 'rot'. In multiple cases old applications that according to you were 'rotting' in my Github have been the basis for useful products that are the backbone of my business today.
Stop repeating falsehoods based on your 'opinion.' This is based on fact--build apps, build your portfolio and you will get ahead in your career.
This is not good advice. People need guidance before they build "products", whatever you mean by that. You admit it yourself: People build todo apps because "[they] are an easy example to grasp the technology you want to use."
Yes--they need to grasp the technology by building apps before they build products. This is what this post is about. There's no need to reiterate your opinion again.
That's exactly what I've said 😃
It's just my opinion, you can disagree with it, just like I can disagree with yours 😃
No, they can build products and learn by doing it. No need to create apps just for portfolio. Your portfolio should consist of built products, not example projects for learning purposes. They might work for some of the employers, but clients don't care.
But again, this is just my opinion 😃
I'm just trying to explain as I clearly see that you don't get my point 😃
Nice. That eCommerce example though 👌🏻
Thanks to you, Jamie!
Great example project ideas! I think building things is the best way to learn.
Hey Travis! I've tried to reach you via Twitter but couldn't 🙁 Are you planning to bring back up Fohkuhs? The download doesn't work 😭
Hey! Sorry about that! I didn't realize how many people used it when I stopped supporting it. 😅
I've added it to my list to revisit, hopefully soon!
Eagerly waiting for your course to start in React12.
Knowledge is wealth, not money. There are many who struggle to understand the basics of programming. And want to give themselves a chance to learn it in a proper way. Books can give you a blueprint, but it's hard to find a teacher who learned it in a difficult way and understand 80% of folks dilemma.
I appreciate Reed, for starting this initiative. It doesn't matter how many apps we build, its about to know - how apps are built.
I really don't understand who has time for this? Any one of these projects, if created properly should take 3++ months work?
Don't get me wrong they're all great ideas individually, and I would be super impressed to see any of them on a developers portfolio I was interviewing; but by no means would I ever expect, or think that a developer NEEDS to create all of this.
You could speak to me personally if you want real answers to these questions. I've made all of the app examples in this post and taught thousands of others to do the same.
Sorry if I came off as an ass, don't get me wrong; as I said they're all great project ideas, and I appreciate you taking the time to suggest them.
My problem is more with the unrealistic expectation our industry has on developers to dedicate huge quantities of (non-work) hours to work on personal projects, something we really don't see to such an extent in other industries.
Personally, I feel like articles like this, implying that developers NEED to spend upwards of 15 months (assuming 3 months more or less for each of these projects) of free time working on a set of large scale applications only further accentuates this trend.
Case in point:
How do you bridge the gap between knowing the fundamentals of React and becoming a professional developer?I wouldn't expect my senior dev's to have a portfolio of side projects this substantial - let alone someone who's only trying to bridge the gap to becoming a professional developer.
Great read! I haven’t been on here long, but this is probably my favorite (and most useful) article so far. In fact, I’m already creating that social media app as I post this.
I should get back on that.
Thank you, Oscar. Enjoy!
great job Reed. It would be fun to learn building real time practical projects and moving beyond "counter" and "Hello world" examples. Looking forward to it.
I Will certainly try one of those, but with Svelte :)
i love svelte too! but unfortunaly where i live pratically doesn't exist jobs with svelte requirement
This is a great article. Nice work for pointing these essential things out. These projects will definitely lighten up your portfolio. The beginner having these projects under there belt will definitely get a job of a React Developer. My special priority goes to ecommerce apps which will contain most of the features. Building apps like UberEats clone, amazon, etc can have a best impact on portfolio. For inspiration, you can check out some of the best UberEats clone app in the market.
great article, I am a python developer and currently learning React.js.
React.js is awesome.
i actually prefer watching a record. i don't understand the reason behind why it's weekly lessons. i want to skip parts that i already familiar with.
Entertainment lit.
Create a static website using Dev.to, Github, stackbit in less than 10 minutes.
CodePerfectPlus ・ Jul 22 ・ 2 min read
Hey I was wondering about the react 12
Are all of it for free?
Hello, There
Thanks for your posting.
your 6th posts attracted me.
by any chance, could you please share 5 sources or tutorials for those?
Wish your kind response