SERVICE / SVC-06 / UNCONVENTIONAL APPLICATIONSDEFINED SERVICE SCOPE

Software for ideas outside the usual template.

Some ideas need their own interaction model. We build applications for exploring scenarios, shaping stories, experimenting with rules and creating experiences that a conventional product template cannot express.

SVC / 06UNCONVENTIONAL APPLICATIONS
Illustrative laptop opening into an interactive world of floating terraces linked by an amber path.
STARTCONCEPT / AUDIENCE
TESTINTERACTION / DEVICE
OUTPUTBESPOKE APPLICATION
SMALLEST CREDIBLE ENTRY POINT

Begin with the decision that must become possible—not with the largest possible scope.

WHEN THE EXPERIENCE DEFINES THE SOFTWARE

AN UNUSUAL IDEA NEEDS A WORKING INTERACTION, NOT JUST A STRIKING DEMO.

A branching story, explorable scenario or playful creative tool can lose its purpose when forced into familiar forms and dashboards. Its value may depend on what a person discovers, changes or creates through the interaction itself.

We turn that experience into explicit rules, content structures and a testable application. The first prototype answers whether people understand the interaction and whether the technical approach can support it.

UNCONVENTIONAL APPLICATIONS

EXPERIENCES WE CAN DEFINE AND ENGINEER

  • 01

    Interactive simulations for exploring choices and their modelled consequences.

  • 02

    Branching narratives, digital exhibits and story-driven applications.

  • 03

    Playful mini applications with original rules and feedback.

  • 04

    Generative creative tools with user-directed inputs and editable outputs.

  • 05

    Spatial or visual interfaces for ideas that are difficult to express in a conventional screen flow.

  • 06

    Custom content editors and publishing workflows for maintaining the experience.

BUSINESS OUTCOME

A DISTINCTIVE EXPERIENCE WITH A CLEAR DELIVERY PATH

  • 01

    An experience specification covering the audience, interaction and intended result.

  • 02

    A working prototype that tests the central mechanic.

  • 03

    A defined technical approach with device and performance constraints.

  • 04

    A scoped application build with documented content and interaction rules.

  • 05

    An agreed source, licensing, maintenance and handover package.

WHAT YOU BRING
  • 01

    The concept and what someone should experience, learn or create.

  • 02

    Audience, context of use and target devices.

  • 03

    Creative references, available content and permission to use it.

  • 04

    Rules, constraints, budget and a decision owner.

WHAT RELESONA PRODUCES
  • 01

    Experience map and interaction specification.

  • 02

    Interactive prototype with recorded user feedback.

  • 03

    Application architecture and content model.

  • 04

    Implementation, acceptance checks and handover within the agreed scope.

ILLUSTRATIVE PROJECT DIRECTION

AN INTERACTIVE SCENARIO EXPLORER.

Imagine an application in which people adjust the rules of a small digital world, explore alternative paths and compare the resulting scenarios. It could support a fictional narrative, an exhibition or an educational exercise. This describes a possible commissioned application, not an existing released RELESONA product.

01

Define the world

Set the content, states, rules and boundaries the participant can explore.

02

Make choices legible

Show what changed and allow participants to compare, undo or restart.

03

Keep it maintainable

Separate content from application logic so the experience can evolve.

FROM EXPERIMENT TO APPLICATION

TEST THE CENTRAL MECHANIC FIRST.

Before expanding the world, adding content or commissioning a full build, test whether the central interaction makes sense to its intended audience. Device performance, accessibility and the ability to maintain the content are part of that decision.

CONTROL BOUNDARIES

THE CAPABILITY IS DESIGNED WITH THE LIMITS THAT KEEP IT CREDIBLE.

  • 01

    Novel interactions remain understandable and support keyboard access and reduced motion where applicable.

  • 02

    Simulation rules, assumptions and limitations are visible; a scenario is not presented as a validated prediction.

  • 03

    Content rights, data use and generated output ownership are defined before publication.

  • 04

    Prototype, pilot and released application are labelled according to their actual maturity.

  • 05

    Payments, public accounts and third-party actions require their own explicit scope and acceptance.

WHO THIS WORK IS FOR

Unconventional Applications suits creators, organisations, educators and teams with a distinctive experience to build and a willingness to test its central interaction before expanding the scope.

FREQUENTLY ASKED QUESTIONS

QUESTIONS TO RESOLVE BEFORE UNCONVENTIONAL APPLICATIONS BEGINS.

01Does the idea have to fit an existing software category?

No. Start with the experience and its audience. We can define a suitable interaction and delivery format during qualification.

02Can this include games or interactive storytelling?

Yes, as a scoped bespoke application. Mechanics, content, licensing, device support and any online features are defined for the engagement.

03Must the application use AI?

No. Deterministic rules and conventional software may be the better fit. AI is considered only when its role and limitations support the intended experience.

04Is the illustrated scenario explorer available to use?

No. It is an example of a possible project direction. This page describes a commissioning service, not a product catalogue or public demo.

MAKE THE EXPERIENCE CONCRETE

BRING THE IDEA THAT DOES NOT FIT THE TEMPLATE.

Describe what people should be able to explore, change or create. We will define the first interaction worth testing and the practical route to building it.