About WheelSays

Founder and Developer of WheelSays

I'm Dan Dadovic, the developer behind WheelSays. I build and operate independent web products through my UK sole-trader business, Dan Dadovic Digital. I take responsibility for what the site does, how it works and how it is looked after.

I've been building and operating independent web products since 2019. I hold a Master of Informatics in Business Systems Organization from the University of Zagreb, Faculty of Organization and Informatics. My professional background is in software services for digital publishers, working around websites, online products and their technical implementation.

That mix of web application development and digital publishing means I spend time on both the software and the experience of using it. A feature needs to make sense to the person opening the page, as well as work in the code.

You can find me on LinkedIn.

I enjoy making useful things with technology, especially a small web product with a clear job. Sometimes you have a list of options and just want to choose one. Sometimes you need everyone in a group, a running order, or a person matched to each task. I wanted a place to do those jobs without an account or unnecessary setup.

The differences between those jobs matter. Picking one name does not create a full presentation order, and dividing people into teams does not assign them individual duties. WheelSays keeps those results in separate tools so you can see what you are asking for. The tool comparison explains which result each one produces.

Website testing is part of the work. WheelSays has automated tests for list validation, random selection, team allocation and the rules behind its other tools. Checks also cover saved-list handling and failure cases. For example, an impossible assignment needs an explanation instead of a result that quietly ignores a rule.

I review changes in the browser as well, including narrow screens and keyboard navigation. Clear labels, visible keyboard focus and readable results matter when you are using a phone or moving through a page without a mouse. Those checks help me find problems; they cannot guarantee that every device or assistive setup will behave identically.

Before publication, the checks include building the site and checking its links and page information. When something changes, I rerun the relevant checks. If something still gets through, a report of the steps that caused it gives me a useful starting point.

Random teams have headcounts kept as even as possible. They are not balanced by ability, friendship or experience. Similarly, an assignment can account for the supported rules you enter, but it cannot know that one job takes longer or that someone needs a particular adjustment. You still decide whether the result fits the situation.

The tools work with your lists in your browser. Saving a source list is an explicit choice, and does not save its generated result or move it to another device. Contact messages and consent-based analytics have separate data handling. The privacy explanation describes those boundaries, including copied text and downloaded files. Take care with names on a shared screen and with anything you choose to share.