Overengineering - How to avoid it

Sometimes I find myself designing my classes for a certain project. I start with some entities, some interfaces, but after some time I think:

Are there free iPhone navigation bar icon sets available?

I want to use up/down icons like the ones used by "mail" in the upper-right corner when you're viewing a specific message. Are these icons available for free anywhere?

Where to put javascript and how to handle events

For a long time I am looking for a practical (reusable, clear, updateable,...) solution to the following:

How to limit setAccessible to only "legitimate” uses?

The more I learned about the power of java.lang.reflect.AccessibleObject.setAccessible , the more astonished I am at what it can do. This is adapted from my answer to the question ( Using reflection to change static final File.separatorChar for unit testing ).

Getters and Setters are bad OO design?

Getters and Setters are bad

Briefly reading over the above article I find that getters and setters are bad OO design and should be avoided as they go against Encapsulation and Data Hiding. As this is the case how can it be avoided when creating objects and how can one model objects to take this into account.

Effeciently storing user uploaded images on the file system

Scenario

Users can post an item and include up to 5 images with the post, each image that's uploaded needs to be resampled and resized - a total of 4 extra images are created. Meaning if the user uploads 5 images end up with 25 images total to store.

Good Tools To Develop a GUI in Android?

I would like to know if there exists a good tool to implement a design in Android like tools to make easy to implement and that can generate XML

Determining source of method call at runtime

I'm wondering if there is a "better" way to do this:

Designing animation for android application

What is the best way to design and embed an animation into an android app. (I'm not talking about transitions and activities in/out animations.)