Connected systems
Ascer Lighting and Visuals coordinates music, lighting and video; Karaoke Queue connects audience requests to a host’s own library.
About the studio
Ideas with a human
behind them.
Ascer Development Studio brings practical applications, games and specialist tools under one umbrella, led by Christopher Bunce.
The whole system matters.
My background crosses security, cloud and service desk work, alongside independent software and game development. That means I look beyond whether a screen works: how does the data reach it, what can go wrong, how will a user recover, and how will someone support it later?
I started exploring game development through RPG Maker and went on to Unity projects, including Tower Climb’s earlier iOS release and the Battle Royal multiplayer foundation. More recent work connects my interests in live performance, music and practical operational tools.
From a personal portfolio to a studio.
Ascer Lighting and Visuals was the birthplace of the Ascer identity. Ascer Development Studio brings that specialist software together with mobile apps, games and integrations. The studio is founder-led today, with room for future collaborators and different kinds of projects.
AI helps with the work. I lead the decisions.
I use AI to accelerate implementation, explore interfaces and iterate on ideas. I still understand and review the code, decide how the product should behave, challenge assumptions and check the result. Clients deal with a person who takes responsibility for the work.
Skills in practice
The portfolio shows how the thinking becomes software.
Native experiences
SwiftUI supports the Apple applications, while C# and Avalonia support the specialist desktop workspace.
Data & workflow design
Drive Flow combines user-owned records, version-checked saves and ordered handovers with a driver-centred interface.
Game systems
Deepforge uses seeded generation, capability checks and save migrations to make a complex set of mechanics easier to develop and change.
Working together
Clear decisions, visible progress.
We begin with the problem and the people using the product. A small working version gives us something concrete to test and improve, while the technical decisions account for storage, integrations, permissions and future changes.
For someone commissioning a product—or considering Chris for development work—the project pages explain the technologies and design choices behind the result. The studio’s shared visual language provides consistency while leaving room for your users and your own identity.
Your next project
What could we build for you?
Describe your users, the workflow and the systems it needs to connect. We’ll discuss a useful first version.