Obviously, if your game is interaction heavy, it helps to implement some UI function, but that doesn't mean you need to go the whole way and animate it. There's no particular need for it to be done immediately, given that functionality is the most important part. Functionally, we have all the information we want to display, but its just a matter of deciding how best to present that to the user. To an extent, we still haven't decided exactly what the HUD will look like. Add different levels of interactivity based on your projects needs and go from a simple wireframe to a prototype that feels real. Add life Communicate the functionality behind your designs and improve communication. Personally for my own project, its been in development for 4 and a half years and only recently have I started to actually lock down and improve the visuals of the UI. Proto.io comes complete with a wide selection of both Static and Animated Icons, Stock Images, and even Sound Effects. If you try and use good project organisation (such as following the Model-View-Controller model), you can neatly separate out the visual representation of something from its functionality, meaning that replacing it should be straight forward and quick. Only once you get far enough along, consider locking it down. Sure, it makes your game look polished, but if there is a chance its going to be stripped out, then perhaps best stick with placeholders that start by just displaying the information you need. With regard to UI, implementing fancy UI with animations and whatnot can be rather time consuming. Regarding games in particular, I think a simple solution is to just avoid over-engineering, or over-developing things early on. Though having said that, I may go through a few iterations of that front-end if i'm not happy with how it feels to navigate, and perhaps will spend time experimenting with visual animations before cleaning it up and unifying them into a consistent system. Given that you can pretty much develop the front-end of the app independently of the back end and then link them together later on, to me, it seems like a waste to do soft prototyping of a webpage, which is very similar just to directly developing the front end in the first place. But as for navigating pages or applying visual effects, I tend to just program those straight away. When things can resize/reshape, then yeah, it can get hard. Though I tend to only work on static content. For websites/UIs/Apps in general, I tend to just prototype with static images.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |