LET’S CREATE TOGETHER
Tell us what you want to create or solve. We can help you work out the scope and the way forward.
Helpful details for your inquiry
Share the game concept, target devices, desired features, current Unity version or development status, and preferred timing where known. Reference games or an early concept note are enough to start a discussion.
Game concept: the play experience you want Devices: iOS / Android / web, etc. Scope: new development / feature updates, etc. Current status: Unity version and planning or development stage Timing and budget: may be undecided
Share the effect’s purpose, reference images or video, Unity and render pipeline details, target devices, effect count and preferred timing. A view of the camera and background helps us discuss how the effect should read.
Use: a skill impact, for example Count and references: URLs, video or desired style Environment: Unity, render pipeline and devices Assets and integration: what you can supply and the work needed Timing and budget: may be undecided
Share screenshots or video, reproduction steps, Unity and render pipeline versions, target devices and the improvement you need. Existing Profiler captures or investigation notes are also helpful.
Symptoms: the screen or action involved Reproduction: known steps Environment: Unity, render pipeline and devices Support needed: investigation / shaders / tools, etc. Timing: may be undecided
Tell us the task, current tools, integrations, frequency or volume, and where a person reviews or approves the result.
Task: weekly reporting, for example Tools and integrations: spreadsheets, email, etc. Frequency and volume: where known Review and approval: where a person checks the result Timing and budget: may be undecided
Where known, include the business challenge, current languages, database / AWS environment, preferred timing and stages you need. Undecided details are welcome.
Business challenge and request: an input-screen change, for example Environment: languages, database and AWS usage Stages needed: requirements / design / implementation / testing Existing materials: availability of documentation and code Timing and budget: may be undecided
Share the purpose, intended audience, questions to test, target devices and the date of a demo or event. Early proposals, sketches and reference videos are welcome, even if incomplete.
Purpose: idea validation / event / training, etc. Audience and questions to test: Required screens and interactions: where known Devices and distribution: Demo or event date: may be undecided
Include the game name, device and OS, and the actions and situation where the issue occurred.
Game name: Device and OS: Question: what happened and during which action Frequency or timing: where known
Share the purpose, current situation, support needed and preferred timing. You can contact us even if you are unsure which service fits.
Purpose: Current situation: Support needed: Timing and budget: may be undecided
Share what you know. You may mark undecided details as “Undecided”.