Is this a problem for you? - Designing apps.

Discussion in 'Mac Programming' started by slooksterPSV, Aug 2, 2006.

  1. macrumors 68030


    Ok, now I just may be weird or that, but I have problems make apps because I can't design the interface to a liking, where with Windoze, I'd just toss it together, but I worry about the design on Mac OS X. This worrying doesn't help me out cause then I can't figure out what I want to code, and I don't want to make my apps repetitive.

    Who else has this problem or knows what I'm talking about?
  2. macrumors 68040


    I do think interface design is more important for Mac apps than for Windows apps, but I wouldn't stress about it too much. Just follow the HIG the best you can then get to writing code. I know what you mean though. I've been spending a lot of time just tweaking the UI for the app I'm working on.
  3. macrumors 601


    I think it's a very positive thing that you are worrying about the UI instead of just "throwing it together". The more concern you have about making it great, the better.
  4. macrumors 6502a


    As far as I am concerned at the moment, just getting the application to run without crashing or leaking memory is the most important aspect. As long as I know what controls are going to be required in the GUI (and I should note that I am presently just developing tools to help me) then the GUI is something that I will address more seriously once the basic application is working.
  5. macrumors 603


    Yeah, I know the feeling, but I also agree with HiRez that thinking the user interface through and worrying about it is usually a good thing. However, sometimes tinkering with the small details can get too time consuming. If you get completely consumed by it you must just have the will power to get coding instead of creating the 37th version of the icon for that button you're not happy with. :p
  6. macrumors 68030


    Generally I purposefully make test apps look really nasty (I mean *really* nasty, so no one can mistake it for the real thing). Then once the basic functionality works, I lay everything out properly.
  7. macrumors 601


    You guys are making me think maybe there is something to be said for "throwing it together" initially, coding, and then refining the interface towards the end. As long as you actually do remember to spend time on the UI. Leaving it til the end gets dangerous, especially if you are under a deadline. Guess what's going to get short shrift if it comes down to it?

    It's also sometimes good to not make it look too nice initially, as then you have lots to improve in the next versions. Well maybe that's cheating but users like to download a new version and be able to see big changes, and the UI is an obvious way to do that.
  8. macrumors 6502a

    There is a significant drawback to just throwing the UI together rather than thinking through the use cases and right grouping/layout of the UI. Often the UI structure guides the structure of the underlying code. The result is that the structure of your code will closely mirror the UI you just threw together rather than mirroring the final UI. This mismatch can cause all kinds of maintenance grief or at least will make the code harder to extend and maintain over time.
  9. macrumors 68000


    Agreed. There are some apps out there that have really impressive, forward-looking interfaces (Acquisition, Cinema, e.g.). Don't let it stop you from making your app -- just follow the guidelines and make it clean and sparse and you can't go too wrong. If your app is good enough maybe you can then find an artist hear to make it look slick.

Share This Page