If so, you need to watch this video.

I'm gonna share with you all of the steps you need to take in order to give your project the highest chance of success.

If you're working on a project you most likely are going to need some form of Web hosting, which is perfect because today's video sponsor is atlantic dot net and they're giving you an entire year of free hosting on their servers.

And these are actually fairly powerful servers.

They're even more powerful than the servers my own website run on.

So you get an entire year completely for free on their servers.

And if you use the code, Kyle, you get an additional $50 of credit that you can use towards additional things such as additional storage, C panel or whatever you want.

On top of that, these servers have incredible redundancy and backup procedures, so you know that your data is always going to be there and always going to be safe.

You don't have to worry about it going down or disappearing or being deleted.

It's always going to be there so highly recommend you check out atlantic dot net and use the code Kyle for an additional $50.

Welcome back to Webb.

Have simplified my name's Kyle, and my job is to simplify the web for you so you can start building your dream project sooner.

So that sounds interesting.

Make sure you subscribe to the channel for more videos just like this one.

Now, the very first thing that you need to consider when building out a project is what is the exact purpose?

Were function of your project?

What is your project?

Solving isn't going to solve some problem for a user.

Is it going to be solving a problem for you?

What exactly is the core essence of your project?

And this may sound like an easy question, but most people think of an idea where they think of a problem.

They think of a solution, and then they just go and try to start building it.

But you really need to de still exactly what the purpose of your project is and exactly why people would use it or why you would use it that way.

You know the exact most important parts of your application was take, for example, Let's say I want to build a course platform for all of my courses and all of my videos in that I know that the most important thing that people are using this platform for is that they can learn Web technologies through my videos and my courses.

So I know that the most important part of my project is not that it's a course video platform.

It's that it teaches people how to learn Web development on that platform.

So now I know the purpose of my project is to teach people.

And it's not to build some project that host courses, so it usually that purpose is going to be something that's not concrete.

It's usually what your users are getting out of your project and not so much what your project is now.

Already, if you've thought this through your miles ahead of most people when it comes to building a project, and the second thing that you can do is to think about your target audience.

This is something that most people completely ignore when they're building a project.

Most of the time, the project audience may just be yourself, and you may be building a project purely for you to use.

And that's perfectly OK.

You know, the target audience is you, and you can kind of skip this step.

But a lot of people want to build projects for other people.

Commercial projects were just fun projects that other people can use.

So you need to really sit down and think, What is the exact persona of the person using my project?

Let's take, for example, that course platform I talked about for me.

The persona of the people on my platform are going to be people that are looking to learn Web development.

And most likely they're gonna be beginner to intermediate level Web developers looking to learn Web development.

So I know that my target audience is going to be that group of people.

You can even break it down further, such as where these people live.

For me, it would be global.

People all across the world are watching my videos, so I don't really have a specific region.

But if you're making something vocal, you may know it's only gonna be people that live in your city or your country.

that are going to use your project.

Also, depending on the project that you build, you may have different genders.

Were age groups that are more likely to use your project, so knowing that is really important overall, By understanding Thea's act audience that you're going to be serving as well as the exact purpose of your application, you're able to very easily narrow down the most important and core concepts of your application.

Which leaves is perfectly into our third point, which is that you want to figure out what are the core components of your application.

What is the most important thing that your project is going to do for me with my course platform?

The most important and core feature is people watching videos.

I need to have some way for people to watch videos on my platform.

That is the only thing that matters.

User authentication is not that important.

Payment processing, not that important.

Just having a way for people to watch video is pi far the most important and core feature of what my application will do, and you need to plan out what that core feature is for your project, and you may think this core feature is really big.

You say the entire project is important, but I promise you you can cut a lot of things out of your project.

Like, for example, my course platform.

You can cut out the payment processing.

You can cut out the user authentication and just do the simplest thing of making video that people can watch.

And you may think that's crazy, because how can I sell courses without payment, processing and user authentication?

But I can handle payments outside of my course platform through PayPal, for example, and just manually due payments that way.

And instead of having user authentication, I could just email people a generic password, which will unlock the page for them.

So I could just have a single password protected page, which uses the same password for everyone and then send that out.

Obviously, this is not ideal for a real world large scale application, but when you're getting started, just knowing that single most important component and doing everything else later as late as possible is a great way to get started because you only have to build a small component of your project instead of something very large.

So now that we understand exactly what the core component of our application is, we can jump into step number four, which is to figure out exactly what technologies and languages you're going to use to build out that feature.

So for me, that course platform that I talked about, the main thing that I need is an easy way for people to watch your videos.

So I'm probably going to want to have some kind of video players.

So I'm gonna look for video player libraries because I don't want to use the built in HTML one.

I also would want to look into video streaming, so I would need to look at something like Cloudflare, which can host and stream my videos for me.

Or maybe something like video that can handle video streaming as well.

That's gonna be really important for my project.

But when it comes to other things such as a database, I don't initially need a database, so I don't need to really think about that too much.

And then when it comes to architecture, where if I want to do, maybe J w.

T for authentication or if I want to do it front end app that has an A p I.

This is something that you want to consider based around what your core component is.

For my example here, I could go with either a normal server rendered app or I could do a front end up with an A P I in the back end.

It really doesn't matter.

Honestly, I could even do a static rendered application that just uses that single password to authenticate users onto the page.

You really just need to figure out what technologies are going to play into your core component and then build out those core components.

If you have, for example, a really simple blogged, there's really no point in building out using all these really fancy cool technologies when you could simply just use Gatsby a static site generator, and make a simple block that way incredibly easily.

So make sure that when you're planning out your technologies, you don't do anything to overkill.

You just figure out what your application does to figure out what technologies best match.

Also, I highly recommend that you go with technologies and languages that you're already familiar with because trying to build the project and learn a new language and learn a new framework.

And learning new architecture all of the same time is a recipe for disaster.

You want to know as much up front as you can.

So going with technologies and languages you already know, we'll give you a much higher chance of success, and that now leads us into our fifth point, which is going to be developed.

A design for this portion, your application.

So go into your favorite design tool or even just get a pen and paper out and sketch up just a rough you eye of what your application is going to look like.

Not every project is going to have a user interface so you can skip this if you don't.

But I can assume that most projects being built has some form of user interface for user interaction.

So you want to sketch up what that's going to look like, so that you can really easily iterated on that inside of your design tools, which are much quicker to build than actually writing out this with HTML CSS, for example.

So go through an injury three year designs and as you're building out your designs.

Make sure you're constantly thinking about the 1st 2 points, which is going to be the actual reason people use your application and the target audience you have.

You want your user experience and you're you I to match perfectly with why people are coming to your app.

So that way, when they get to your app, the thing they want to do the most is the easiest thing to do on that application.

So make sure you really think about that when you build out this you I Then once you have the you I figured out in your design tools, you can move on to step number six, which is going to be actually developing and building out that application for real.

And this is going to be using the technologies we talked about in the previous example.

We're gonna put that together and make a quick and dirty version of our simple version of our application so we don't want to build the entire full blown application.

We just want to build that one single small component of our application on.

We want to build it as quickly as possible, So don't worry about making the best architectural decisions.

Don't worry about making perfectly clean written code.

Just make it good enough.

As long as it works and functions, that's all that matters.

You want to get people using your project as soon as possible.

So it's really important that this N v p minimum viable product is as quick and dirty as possible to build that when you can immediately get people using it and talking about people using your project that leads us to step number seven, which is, Get this in front of people.

You want to get your project in front of other people as quickly as possible because you have bias.

You're obviously biased towards your own project.

You know how it works.

You know how to use things.

But as soon as you get other people using it, they're immediately going to know all the things that are wrong with it.

They're gonna see things that they don't like, and they will let you know.

So figuring out what these problems are as soon as possible means you can easily, quickly change them, iterated on them and make improvements.

So that is why you want to get people using your project as soon as possible.

This is why, in the previous steps we only built the smallest component of our project.

And then we got people using it because maybe you had a huge grand idea for all these additional features.

But your users never actually wanted any of those features, and they all wanted something else instead.

Now, you didn't waste weeks, months, even years building out all these extra features on Lee to find out nobody actually wanted them.

So now you're actually building the core features your user wants and also building the additional features that they want on top of debt.

And once you get that feedback from your users, essentially, you're just gonna loop back through all of these steps, you're gonna make sure that you re analyze your project, make sure it's still aligns with what your users want.

You also want to re analyze what your target audiences you want to go through, reconfigure all of your steps to make sure you're using the right technologies.

And then, instead of building out that core component, you're gonna build either improvements upon it or you're going to build new features on top of it.

And if you need to do design work, make sure you include that before you actually start building the feature, throw back out to the people using it and just constantly iterating, iterating, iterating you want to reiterate as quickly as possible.

So the shortest amount of time you can go from the first step all the way to the last step and get in front of people and then reiterated again is crucial to building a really, really successful project.

I've built multiple large projects in the past and every single time that I take too long to get a rate where I try to build too much at once.

My project almost always fails, and that's because I don't get feedback from the user, and that is the most important thing.

You can get one building a project, so I really hope this was able to motivate you to start building and planning your own project.

And I also want to hear what is the project you want to build?