In the first iterations class names and their packages are constantly refactored
a really bad sounding name like "waste", "junk" or "unrelated" does a better job by forcing you to refactor such a "kitchen sink" package with its contents in a later iteration
should at least consider displaying something sensible if either/both dimensions of browser window used is too small
ideally, use responsive design approach to ux
also including my long-standing desire to keep internal things opaque to the outside world (eg. minimize exposure of directory structure, internal oids, host names, port numbers, etc)