Newbie alert. Need advice :D

Hi… I’m a newbie here in this forum. And also new to unity. I hope we can help each others :wink:
So me and my team are making a puzzle game for android. This game has no story, yet we’re planning to enhance the design so that it looks more interesting.
The game consists of 2 stages, and each stage has 20 levels. In each level there are gonna be several bulb lamps that are connected to the switches. The bulb lamp has its own colour. And the switch controls several bulbs with its colour control. Our goal is to turn on all the bulbs. I don’t know if you guys get what I mean by this explanation without showing you the user interface, but hopefully you’ll get the point.
If you guys have any advice to make this project goes well, please leave a comment. Thanks in advance :smile:

(1) Preproduction: Write ideas out. Draw pictures. Simulate the play experience with your fingers on a drawing. What modes are there, what screens are there, what basic meshes and scripts will you need to be able to play the minimum core of the game? Ignore the textures and sounds for now.

(2) Production: Create the basic meshes and scripts. Use cubes or spheres as stand-ins for the objects while you’re getting the logic working on those game items. Start working on textures and sounds in parallel, or if it’s a very small team, after the basic game elements work. It is too easy to waste a ton of time changing your mind on all the textures and fiddly details, and never work on the play mechanics.

(3) Testing: Get used to testing all the implemented features over and over and over. Some teams prefer to develop a bunch of new stuff, then test it all at once. Some developers prefer a zero-defect methodology: constantly test each feature as you develop it, and don’t move on to something else until all known problems have been solved. It’s easier to fix a problem while it’s simple and isolated, before it gets lost in the inter-connections and architectural mistakes.

(4) Feedback: Get other people to try the thing, early and often. Tell them to talk out loud as they explore what you have. “Okay, the turning controls are sensitive. I want to change how sensitive the turns are. Let me see. Oh, menu, um, settings, uh, here. I’ll turn down the sensitivity… OK, close that, let’s try… yeah, that’s better.” Listen for feedback that someone could not find something they were looking for. Confusion. Misunderstanding. Don’t explain how it works to these people verbally-- watch how they discover how it works (or doesn’t).

(5) Ship it and get the word out.

Thanks a lot halley. it means a lot :smile: