

I write commonly usable software, e.g. in the areas of maps (OpenStreetMap), photo, CMS, construction defects and server control.
Except for special orders my software is available for free.
I write specific software on request: info@elbe5.de
All source code is open source; I publish it as mr-elbe5 on Github.
Michael Rönnau, Software developer more
Current
- The new map app 'OSM Maps' is ready. It is the successor of 'Maps for OSM' and is available in the app store for all three device types (phone, watch, desktop). Data from the old app can be transfered.
OpenStreetMap Maps

I value OpenStreetMap, because it is an open system with detailed information from people of the region.
I am hosting an own server (partially with own styles for hiking).
OpenStreetMap Apps

I write apps for OpenStreetMap for the Apple environment, that is for iPhones, iPads, Apple Watch and the Mac.
The current app family is 'OSM Maps', which replaces the older 'Maps for OSM'.
Content Management

The CMS "Bandika" exists since 2007 in severeal renewed versions.
It is based on Java, Tomcat and a PostgreSQL database. It features role based safety and a WYSIWYG inline editor.
Construction Defect Tracking
The construction defect tracker "Codef" is combination of server application based on the Bandika framework and a IOS-App for registering defects in place.
The IOS-App can also be used independently e.g. for maintanance people.
Developer Tools

I write developer tools for the Mac (also for MacOS) especially when I need such tools myself. An example is the Log-Viewer for watching log files, also on remote servers.
Principles
Openness
Software should be publicly visible and comprehensible. Only this will create trust and security.
Clearness
Software has to follow a clear and defined goal.
Simplicity and clear structures are preferred over assumingly all-covering frameworks.
Code has to be readable like prose.
Therefore, it is orientated at real objects in structure and naming.
Simplicity
Use has to be quick and simple, as intuitive as possible.
Usually simplicity of software means effective and thus less hardware requirements. In the end with simple software safety can be achieved much easier.
Safety
After writing banking software for many years, one thing has become important to me: No vulnerable HTML, no vulnerable databases, as many scripts as necessary, as much compiled code as possible.
