Frequently asked questions

An immersive site is one the visitor moves through rather than reads. It can be a three-dimensional scene that opens in the browser, a story that unfolds as you scroll, or a space you walk through with a camera. The industry also calls these "3D websites", "interactive sites" or "WebGL experiences". What they have in common is this: the content does not sit still on a fixed page, it opens up as the visitor moves.

No. Following the link is enough. No plugin, no app, no install; the site opens like any normal web address. The same link works on a phone and on a computer.

It will be if it is built badly. That is why mobile is not a stage we adapt to afterwards but a constraint we plan for from the start: scene complexity, texture sizes and pixel ratio are tuned to the device, and on a browser without WebGL the site falls back to a plain HTML version — no blank screen.

3d.cbh.org.tr is our hardest example: a multiplayer 3D world running in the browser, optimised to open on low-end phones as well.

Not by themselves — and this is the part most often skipped. When the text lives inside the WebGL scene, a search engine cannot see it; in practice the site looks like an empty page.

The solution is to produce real HTML on the server independently of the scene, add structured data (schema.org) and get the technical SEO setup right. iltay.org.tr ranks first for its target searches despite having almost no inbound links.

No. If what you have to describe is a place, a product or a process, three dimensions help. But if what the visitor actually needs is to find something quickly and leave, a 3D scene is a burden rather than a benefit.

When that is the case we say so in the first conversation and propose a conventional corporate site instead. Taking on work that should not be done ends badly for both sides.

It depends on the scope; a single-page 3D presentation and an archive site with two thousand files are not the same job. We give a timeline once the scope is clear, after the first conversation. We do not give a schedule without knowing the scope — a date that does not hold is of no use to anyone.

We do not publish a fixed price list. Not to avoid transparency, but because the work is not comparable: the same figure is too much for one project and not enough for another. We discuss the budget in the first conversation, once it is clear what will be built.

If you already have a budget, say so at the start — we can either shape the scope around it or tell you plainly that it does not fit.

Yes. Who manages the content, and how, is part of the design; we build an administration panel where text and images can be changed. We go through it together at handover.

The three-dimensional scene itself (camera movement, lighting, geometry) lives in the code and is not editable from the panel; if something needs to change there, you write to us.

We prefer to do both, because that is where the difference shows: when the person designing and the person coding are different, the motion and fluency promised in the design get lost in the build.

That said, if you already have a finished design, or you need help only on the technical side, we can talk.

We are based in Ankara and work remotely across Türkiye and abroad. Meetings run online and the whole project can be followed over a link. Distance is not an obstacle.

One sentence is enough. Leave a note in the box on the contact page telling us how you would like to be reached, or write directly to info@intak.tr. In the first conversation we work out what you want — at that stage there is neither a design nor a fee.