I AM TMOTI✧Back to the experience ↗

RAMAN / CREATIVE DIRECTION / 16 OCTOBER 2026

A remarkable site.
A clear next step.

The research, implementation decisions and film-production brief behind this first version. Design choices are hypotheses to test, not promises of revenue or virality.

Connected previews

Pet Finder, PartAtlas and Wardrobe Mirror now open from their project details. Their hosted URLs and owner-only access were confirmed through Sites. Actual device behaviour still needs testing. Other catalogue entries remain project previews.

What is built

Research → decisions

The research spans homepage usability, product explanation, web performance, accessibility, search discovery, experimentation and video-reference workflows. The sources below are primary guidance or first-party case studies.

FindingApplied to IAMTMOTI
Visitors need to understand a homepage and identify its main tasks. NN/gA short brand promise, a prominent app-finder route and direct navigation to the collection and creative channel. The quiz is optional.
Product visuals and descriptions should answer practical questions. NN/gEach project explains its intended use and readiness. Concept graphics are labelled; screenshots and demos should come from tested release builds.
Clear, differentiating descriptions help comparison. NN/gPlain-language benefits and short feature notes. No invented reviews, download totals, awards or guaranteed outcomes.
Loading, responsiveness and visual stability are measurable. Google Web VitalsCompressed local WebP imagery, no font downloads, no heavy framework, reserved image dimensions and a small script footprint.
Performance can affect business outcomes; effects vary. Vodafone case studyProtect the mobile experience before adding video. Vodafone reported 8% higher sales alongside a 31% LCP improvement in its experiment; that is not a forecast for this site.
Long automatic motion needs user control. W3CPause control, finite reveal and a static experience when reduced motion is requested. Future video gets the same controls.
System motion preferences should be respected. web.devCSS switches off animation and smooth scrolling for reduced-motion users.
Useful content and understandable structure support search discovery. Google Search CentralSemantic sections and descriptive text. Before public launch: add individual verified app pages, canonical URLs and a sitemap for the final domain. No ranking promises.
Small qualitative usability rounds reveal obstacles; they do not estimate population conversion rates. NN/gStart by observing about five representative visitors. Fix confusing labels, then test again. Run adequately powered experiments only after meaningful traffic exists.

What success should mean

For this site, success is a visitor reaching a relevant, usable app or engaging with a real creative work. Attractive animation supports that journey. It cannot substitute for a useful product, distribution or a trustworthy offer.

A focused visitor journey
  1. Understand: “This is Raman’s home for apps and creative work.”
  2. Choose: browse directly or answer the finder.
  3. Evaluate: see the real app, compatibility, purpose, price and release status.
  4. Act: open the verified store listing or watch a performance.
  5. Return: find useful updates and new work.

Keep the finder to three questions initially. Only add questions that demonstrably change the recommendation. Never require an email just to see results.

Measurement plan — not yet instrumented

Before marketing, choose a privacy-appropriate analytics approach and update the privacy notice. Track aggregate events such as finder start, finder completion, app-detail view, verified store click and video play. Do not transmit free-text answers or personal details by default.

Establish a baseline first. Test one meaningful change at a time, define the outcome in advance and do not declare victory from a handful of clicks.

A practical first usability round

Ask visitors to find something for a specific need, explain why it fits, locate its availability and then find Raman’s creative channel. Observe without coaching. Note where they hesitate, misread the state or cannot find the next action. Include mobile users and keyboard navigation. Fix the most consequential obstacles and repeat.

Your ten-second brand film

ByteDance’s official Seedance page confirms support for image, audio and video references, with control over camera and lighting. Use the official “Try now” route to a currently available interface; exact controls, access, cost and restrictions depend on the service and account. No Seedance generation or purchase has been made here.

  1. Choose your final approved brand portrait. The homepage currently uses the recovered version with glasses. Use the full-resolution original, not a screenshot of the chat.
  2. In a supported Seedance image-to-video or reference workflow, upload that image. Ask for a ten-second shot if the chosen interface supports that duration. If only a shorter duration is available, generate that and create a gentle edited loop.
  3. Generate a 16:9 desktop composition with the portrait on the right and quiet space on the left. Also make a 9:16 mobile version or a carefully checked portrait crop. Do not stretch the source.
  4. Use the prompt below. Keep motion restrained around the face and glasses; the environment can provide the spectacle.
  5. Inspect the entire result for facial drift, hands, spectacle frames, warped lettering, flashes and strange cuts. Regenerate or edit any defects.
  6. Add the exact “I AM TMOTI” lettering as a separate overlay in the website or editor. This preserves spelling and keeps text crisp.
  7. Export a silent web MP4 (H.264) and optionally WebM, with a still poster. A proposed starting budget is about 2–4 MB for the hero clip; judge visual quality and actual mobile loading before accepting it.
  8. Send the approved film here. It can replace the animated still while retaining the pause control, static poster and reduced-motion treatment.

COPYABLE CREATIVE PROMPT / PROPOSED DIRECTION

Use the attached IAMTMOTI brand portrait as the visual reference. Create a 10-second premium cinematic hero shot. Preserve the subject’s facial identity, bald head, beard, exact glasses shape, clothing and seated pose. No speaking, no lip movement and no change of expression. A slow, elegant camera push-in reveals immense golden portals, drifting clouds and distant floating architecture. Warm gold light moves subtly across the scene; faint particles drift through the air. Keep the face stable and the atmosphere photorealistic. Maintain a dark, quiet left third for website text, with the subject on the right. No new lettering, logos or watermarks; no extra limbs, morphing, fast cuts or strobing. Finish with a gentle hold. The mood is possibility, creative courage and quiet command.

For a loop, ask for compatible opening and closing composition and then inspect the seam; a prompt cannot guarantee a seamless loop. On phones, size the hero responsively in pixels and viewport units. A physical size such as 5–10 centimetres will vary by screen.

Hosting and domain

This build is prepared for a private hosted review. That does not connect IAMTMOTI.com or make the site public. No additional hosting purchase has been made. If you already own the domain, its registration can remain with your current registrar. Domain ownership and registrar have not been confirmed in this update.

When the site is ready for public launch, attach IAMTMOTI.com through the hosting service, use the exact DNS verification and routing records it provides, and wait for domain and HTTPS validation. Preserve any existing mail records. Do not guess IP addresses or change nameservers without checking what other services use them.

Portable static HTML, CSS, JavaScript and assets are retained as the source. A different static host is possible later; pricing and limits should be checked at that point. For example, Cloudflare Pages’ own custom-domain instructions distinguish apex-domain and subdomain setup. Those instructions are specific to Pages and are not the DNS settings for this hosted review.

Before a public launch

Verification record

JavaScript syntax checks and all 64 questionnaire combinations passed, including preference-ranking checks. Local asset and internal-link checks are included in the source. Browser rendering, real-device interaction, Core Web Vitals and screen-reader behaviour have not been verified in this environment. No claims about those results are implied by a successful deployment.

Return to IAMTMOTI ↗