
Interactive Software & Platforms
Interactive software, built around real actions.
Turn a touch, a choice or a movement into a response people understand. We build the interfaces, application logic and connections behind games, public touchscreens and connected experiences.
Follow one interactionIllustrative gallery application and visitor setting.
One action. One useful response.

01 · Action
Start withone clear choice.
A gallery visitor wants to know what is on. Three clear choices make the first action obvious.
Illustrative gallery application · content and connections are selected for your brief.
01 · Action
01 · Action
Start with one clear choice.
A gallery visitor wants to know what is on. Three clear choices make the first action obvious.
A task people recognise. We define the user’s goal, the input and the response before selecting the application structure.
02 · Interface
Bring the next step forward.
Choose Exhibitions and the screen opens a useful result. Content, feedback and a way back keep the interaction easy to follow.
States that connect. We design start, selection, result and reset states as one journey, with clear touch targets and readable content.
03 · Rules
Every choice. A clear response.
Clear rules turn an exhibition choice into the right result, with a way back when content is unavailable.
Logic that supports the journey. We define progression, validation and recovery around the intended task, then check how those rules behave on the target setup.
04 · Connections
The right content. In the right place.
The selected exhibition supplies the screen with its image, title and visitor information through one agreed content connection.
Content with a clear owner. CMS and API connections are scoped around the available systems, fields, permissions and responsibilities.
05 · Response
Try it. Then start again.
Explore an exhibition, an event or a visit. Each choice reveals a different result, and Back to choices prepares the screen for the next visitor.
Ready for the next interaction. We test the agreed journeys, devices and reset behaviour, then hand over the application with its operating and support requirements.
A clear action.
A connected response.
Interactive software development in Singapore, shaped around what people need to do. We connect the visible experience to the rules, content and systems that make it work.
Make the idea usable
Translate a creative brief into clear interface states, prompts and feedback. Interactive application development makes the audience’s task concrete enough to prototype, review and build.
Make the behaviour consistent
Define what happens after an input, how a journey progresses and how it starts again. For connected experiences, each phone, kiosk or shared display has an agreed role.
Connect the right information
Bring the interface together with its content and required CMS, CRM or API connections. We review data, access, ownership and operating dependencies before implementation.
From the first input
to the working application.
Interface + behaviour
Map the user’s task, screen states, input rules and feedback. Prototypes make the interaction reviewable before the full application is built.
Application + connections
Develop the agreed logic, content structures and system interfaces. Connected experience software defines what each device sends, receives and displays.
Testing + handover
Check the critical journeys, device setup, reset and recovery states. Agree hosting, content ownership, operator guidance and the support arrangements needed for live use.
Application behaviour, integrations, device support and deployment are agreed for your brief.
Different interfaces. Connected thinking.
Format 1 of 5: Public kiosk application

Public kiosk application

Playable game system

Campaign microsite system

CMS publishing console

Connected API workflow
Public kiosk application
Turn a public-facing task into a clear touchscreen journey. We connect navigation, content, feedback and reset behaviour around the audience, venue and operating team. The gallery shown is an illustrative concept.
Playable game system
Build the rules behind a branded game: inputs, progression, timing, scoring and completion. Personal devices and shared screens can be connected where the brief calls for distinct player and audience views.
Campaign microsite system
Connect responsive campaign content to an agreed participation flow. Campaign platform development brings forms, validation, confirmations and selected system connections into one useful journey.
CMS publishing console
Give the content team a structured way to maintain the experience. We define reusable fields, editorial roles, media handling and publish behaviour around the chosen CMS and the people using it.
Connected API workflow
Connect a user action to the information it needs. We review the available endpoints, data contract, access and ownership, then implement request, response, error and recovery behaviour within the agreed integration scope.
Illustrative software directions, with connections and operating requirements selected for each project.
Software that connects
to the experience.
Documented projects linking audience actions, application behaviour and the device in front of them.

DBS Multiplayer Game Showcase
A mobile quiz application connects personal answers and multiplayer game logic to one shared large-format display.

CPF Retirement Estimator
Application UX and a guided calculation interface come together in a public touchscreen kiosk.
Before the application is built.
How does this support a game, kiosk or installation?
This is the software discipline behind the experience: interface behaviour, application logic, content and connections. We can build a focused application or coordinate several touchpoints around the same audience journey and operating requirements.
Can it connect to our CMS or CRM?
We review the available APIs, permissions, required data and operating rules first. The build can include agreed CMS, CRM, SaaS or API connections, with responsibilities and integration boundaries defined for your systems.
Can phones and a shared screen work together?
Yes, when that fits the intended experience. We define joining, input, shared progress, timing and reset behaviour, then test the agreed device and network setup. Device support and operating conditions are confirmed for the project.
What happens if someone leaves halfway?
We plan completion, return, reset and recovery states around the application and venue. A public kiosk may need an agreed inactivity reset; a connected session may need reconnection or operator controls. The behaviour is specified and tested within scope.
What is included in the handover?
We agree the application release, content responsibilities, deployment setup, operator guidance and support requirements. Hosting, third-party services, maintenance and future changes are scoped for how the experience will run.
Make the ideawork for people.
Share the user action, target devices, content and systems your application needs to connect.
Discuss your software flow

