Isn't it easier making a game on Android? especially if you lack experience... you don't have to invest as much time into it or money. A PC game can take a very long time to develop compared to a simple Android one.Why don't you start with PC and go to android once you get the hang of it? I think it's better to have a PC version first and have a mobile version later. As the previous poster has suggested, start with small projects and work your way from there. That's pretty much a basic key element whenever you're starting out in game programming, a simple pong game could help you get started. Also, keep in mind of what engine you're using, some might be harder than others while some can be really easy that you don't even need programming knowledge that much.
Not necessarily. Obviously, though, when you think of a PC game Steam immediately pops up, whereas the idea of an Android game makes us think about simple time killers, so the latter will surely be easier to program. However, the same game would be easier to develop as a PC game: testing is way quicker, you don't have to adapt your app to different screen sizes, and there are way more game engines available for PC games than Android ones (or, at least, there's higher compatibility).Isn't it easier making a game on Android? especially if you lack experience... you don't have to invest as much time into it or money. A PC game can take a very long time to develop compared to a simple Android one.
I agree with this. Start as small as possible. And then add your skills like you add bricks into the house. This way you can learn many small things in short time. I have found that some of the games are built over several years. And it should not be that hard even if you are single programmer. You just need focus and get things without bugs in game.Start small. First you need to know at least the basics of programming. There are plenty of tutorials, be it on YouTube or otherwise where you can great knowledge of it and I highly suggest having that tied up before moving on. As for your first project, I know you're anxious to get to the game you want to make, but trust me, start small. Make a tic-tac-toe. Or pac-man. Or tetris. 2048 is another super-simple project you can do in a day. When you create one of these (my advice is doing it on your own, but if you want to follow a tutorial, then that's fine too), try adding a new feature. Something that's completely original and your own. It will force your brain to think differently and work through the bugs.
Best of luck to you.
I agree with this. Start as small as possible. And then add your skills like you add bricks into the house. This way you can learn many small things in short time. I have found that some of the games are built over several years. And it should not be that hard even if you are single programmer. You just need focus and get things without bugs in game.
I agree with this. Start as small as possible. And then add your skills like you add bricks into the house. This way you can learn many small things in short time. I have found that some of the games are built over several years. And it should not be that hard even if you are single programmer. You just need focus and get things without bugs in game.
Game developer wannabe who failed to keep up here. I'm no expert, but I know a few things you should keep in mind to start:
Start with a simple idea based on the fundamentals of a genre (overworld, unit and a navigation menu for RPG, obstacles and physics for Platform, etc.) and keep in mind these things. Oh, and don't forget to stay patient. It will take years, and the bad news is that there are no shortcuts. Don't make the same mistake I did.
- Start with small projects: Don't start big. Really, don't. You don't have the knowledge to make anything big enough, and, even if you somehow managed to go on and learn things as you go, your code will get so messy you'll have to rewrite it. Start small to get familiar with your game engine of choice and the programming language you've chosen, too.
- Focus on one language at a time: If you're serious about this, then you'll have to learn how to program, no excuses. Depending on the game engine you've chosen (it's not really recommend to start by building a custom engine, considering there are absolutely viable options out there), you'll have a more or less restricted batch to choose from. For instance, the most recommended language for Unity is C#, whereas Unreal Engine favours C++, if I remember right. Anyway, focus on a single language when starting out and learn its ins and outs.
- Focus on developing single features, one at a time: The key to development is setting realistic, short-term goals you can reach. Break things down as much as you can, and then start developing each single features. You want to develop a platform game? Start from the sprites and make them work. Next, horizontal movement. Jumps and physics come next, then obstacles. It's much easier to do this than just blurt out "I want to make Super Mario".
I don't fully know myself. I guess I just lost interest as time went, and I also got progressively busier with school. I was driven by curiosity more than anything, there was no true "passion" that lead me to start, and I later found myself lacking the motivation I needed to keep going. Maybe one day I'll come back to it more seriously, but that won't happen in the near future.Great ideas. Too many aspiring developers start to work on project bigger than themselves, they try to use languages in ways they shouldn't, and start working on a lot of features at once so they lose sight of the bigger picture. The exact opposite of what you said. Why did you fail to keep up? You seem to know your stuff.