Start an older Kamigami project by checking the exact robot, its condition and the device that will control it. A usable kit needs compatible software as well as intact mechanical parts. Verify that combination before buying an old robot or promising a powered classroom activity.
This is a legacy owner's guide. The worked document example is the 2017 Bokken, product FRD00; other insect shells and Jurassic World models require their own records. It helps you choose a feasible activity, including an unpowered option when app access or hardware condition remains unresolved.
Check support before spending money
Support check, September 7, 2026: Mattel's Bokken support page still provides chassis and shell instruction PDFs and says replacement parts are unavailable. Its promotional description retains an old promise of continuing app updates. That wording is not a dated confirmation of current phone compatibility.
For this review, searches of Apple's US app catalog and the US Google Play web store did not produce a verified Kamigami control-app listing. The legacy FAQ linked by Mattel also could not be reached. These findings do not establish availability for every country, account or previously installed device. They do mean that a fresh installation and a supported operating-system combination have not been verified here.
| Your situation | Check | Useful next step |
|---|---|---|
| Considering a used kit | Exact model, condition and demonstrated app/device operation | Verify on the intended device before committing money |
| App already installed | App version, OS version, connection and a short controlled response | Document a working combination before relying on it for an activity |
| Fresh installation needed | Official listing, publisher and device compatibility | Ask Mattel if the appropriate official app cannot be identified |
| Robot will not power or charge | Model-specific instructions and visible condition | Seek product support; avoid improvised battery repair |
| Powered use remains unresolved | Intact, safe-to-handle mechanical parts and diagrams | Use an unpowered structure or planning exercise |
A seller's video on a different phone is evidence for that seller's setup. Record the exact app, publisher, device, OS and date, then determine whether the same path is available to you. Similarly named products such as KamiBot use their own control software. An app name that sounds similar is insufficient evidence of compatibility.
Use official app stores and manufacturer support. Avoid treating an APK mirror, an old promotional download button or a requirement to weaken device security as a supported installation path. Preserve a working installation carefully; deleting it does not guarantee you can download it again.
Identify the kit and inspect the mechanics
Find the product number on the packaging or product markings and match it to Mattel's support record. For FRD00, open both the official chassis diagrams and the Bokken shell diagrams. The chassis PDF is 22 pages and the shell PDF 13 pages, including their cover illustrations. They show sequential folds, orientation and fastener placement.
Lay the parts beside the appropriate diagram and compare left and right structures. Check fold direction, seated fasteners, shell placement and freedom from binding. Photograph the current state before correcting an uncertain assembly step. Follow the illustrated sequence rather than forcing a piece to fit a remembered shape.
Mattel's FRD00 product record lists an age recommendation of eight years and up and a non-replaceable 3.7 V lithium-polymer battery. An adult should review an old unit's condition and the original charging instructions. Stop using a unit with swelling, leakage, unusual heat or damaged charging parts. Do not open or improvise a replacement for the sealed battery assembly.
The available assembly PDFs explain the structure; they do not establish a supported current charging or app-recovery procedure for every old unit. If the original charging instructions or a required component are missing, resolve that with Mattel consumer support before powered use. Supply the product number, photographs, device details and the exact symptom.
Establish a simple working baseline
If the correct official app is already installed or can be obtained for your device, follow its model-specific connection instructions. Keep other nearby robot sessions closed while identifying the intended unit. Record permissions or connection messages exactly, since a silent assumption about the device's state makes troubleshooting harder.
Begin in a clear, level floor area under supervision, away from stairs, pets and loose objects. Establish how the app stops motion and where the robot's power control is before issuing a short movement request. Keep hands and hair clear of moving legs. The first goal is a predictable start and stop, not speed or a complicated game.
Separate outcomes: the app opening, the robot connecting, a light responding and the mechanism moving are different checks. If light control works but movement does not, inspect the mechanical assembly and recorded power condition before repeatedly issuing commands. If connection fails, preserve the error and software versions for support.
Yenra has not physically tested a Kamigami/device combination for this guide. Use the checks as a record of what your own unit demonstrates. For a time-limited lesson, prepare the unpowered activity below so an unresolved dependency does not consume the whole session.
Turn a working robot into a measurement exercise
Once short, controlled motion works, choose one question: how consistently does the robot travel during the same brief command? Mark the start position and orientation on the floor, use the same surface and command, and record five trials. A phone video can help estimate duration without handling the robot while it moves.
Invented example: repeatability of a short run
Suppose five two-second runs cover 38, 42, 40, 39 and 41 cm. Their mean is 200 ÷ 5 = 40 cm, with an observed range of 38–42 cm. Mean travel speed over those runs is 40 ÷ 2 = 20 cm/s. These values are example arithmetic, not measured Kamigami performance.
Change one factor, such as the floor surface, and repeat with the same starting method. Record battery condition and any failed run; explain an exclusion from the average. A difference suggests a question about traction, gait or measurement rather than immediately proving a cause.
For a coding exercise, first write a finite sequence in plain language: signal a start, move briefly, stop, signal completion. Translate it only into controls actually available in your app. Check each step independently before combining them. Timed movement has variable distance; a drawn square is an experiment to measure, not a guarantee of returning to the starting point.
Keep the learning useful without the app
An intact unpowered kit can still illustrate how a flat sheet becomes a three-dimensional mechanism. Use the official diagrams to identify folds that create stiffness, points where fasteners hold shape and mirrored parts that must agree. Compare a diagram with the assembled chassis and explain what would bind if a fold faced the wrong way.
Sketch a paper model of a folded beam and predict which shape resists bending better, then compare it gently by hand. Keep this as a separate paper exercise; avoid repeatedly folding an aging robot part to demonstrate fatigue. Another useful task is writing a test plan with a prediction, one changed variable and a way to record the result.
Download the editable Kamigami owner and experiment record. It keeps support evidence, assembly checks and measurements together. If the goal is a new programmable robot project, the first wheeled-robot guide provides a separately documented platform and bounded starting program.