With regard to the operation, we definitely want to keep the paging method, i.e. not switch to continuous scrolling. Images do not have to be scaled to full screen width, which often makes the viewer feel overwhelmed. The existing ipernity layout, in which our images are presented together with title, description and other details, gives a much better feeling of sharing.

We could perhaps expand the display options for different sizes, as well as the number of columns. When viewing medium image formats, the current three columns could be retained. You could also imagine expanding to six or seven columns to use the full screen width. The existing menus, the proven pull-down menus, the Action menu, the header and footer: all this works well in terms of navigating easily and elegantly through the site. In the pull-down menu, some additional features could be added, such as a print service or a custom backup. In addition, it would be possible to add additional settings that have been desired for a long time, such as the individual choice of background color. However, we do not think it makes much sense to use cryptic symbols instead of easily understandable menus. The latter is something we are very committed to, because it guarantees exactly the efficient usability, which we appreciate so much about ipernity.

Because an inventory has to be made anyway in order to prepare the specifications, we have started to take screenshots of all pages. This is a very extensive job that will take weeks. Under each screenshot, we will enter what we think should be changed as the ima team. In this way everything will be documented in a completely transparent way. But we also invite you to make all your wishes known under these screenshots. This ensures that nothing is forgotten. However, we must also point out that not every wish can be realized. We must always consider the budget and must not lose sight of the main goal: the renewal of the technical basis. This coupled with a better provision for mobile devices is what matters most, so that the provision of separate apps is no longer necessary.

This approach is the easiest way for us to define exactly what we really want, so that the IT service provider to be commissioned understands our requirements exactly. This eliminates the need for abstract additional specifications, and a simple target/actual comparison is possible at any time as the project progresses. We don't want to make the mistake of giving an IT service provider blanket permission to design any other layout. It's not up to the programmers to tell us what they want us to get, or to prove to us how smart they are. Their task is rather to realize our requirements in the best possible way. In doing so, we want to build on what we know and to which we expressly commit ourselves. There should be no fundamental changes to the "look and feel".

In summary, we would like to express that the planned reprogramming is not intended to produce a "completely new ipernity". Our "classic car" will be technically updated and will get a new engine, so that it is more reliable, is easier to maintain and above all affordable to run. But we want it to retain its unmistakable character.