Hippani Animator is a timeline editor for making browser animation and small interactive projects. A user places text, images, shapes, buttons, sound, or web objects in a scene, sets their state at selected frames, and lets the editor calculate the movement between those states. Hippani Animator can publish the result as a web page, animated GIF, image sequence, widget package, or video.
The project is more than a drawing. Frames can run scripts, buttons can change the timeline, and forms can collect input inside an exported page. The editor supplies the visual structure, but browser behavior still matters after export. A movie that plays inside the editor has not yet proved that every web object works online.
Frames create motion
A key frame records position, angle, opacity, and visibility at one point in time. A transitioning frame lets Hippani Animator calculate the states between two points. A non-transition frame holds its state until the next change. This makes a sliding object different from one that jumps to a new position even when both use the same two endpoints.
Layers keep related items together and can be locked or reordered. Script frames run when playback reaches them. Removing or moving one script frame can therefore change navigation or a game event without changing the artwork. Testing only the beginning of a long timeline can miss that break.
Publish to HTML
HTML export can write one page with embedded media or a page plus a media folder. It can also clean unused files from an older export. The generated test page helps with browser checking, while an iframe snippet places the finished movie inside another site.
Export frame rate affects smoothness and processor demand. A complex scene may run on a desktop and struggle on an older phone. A dynamic frame-rate option assumes larger screens have faster processors, which is only an estimate. The final page still needs a test on the slowest device it is expected to support.
HTML hides in preview
An HTML object can add a control or page element that Hippani Animator does not supply. The object appears in the exported page, but the internal player leaves it empty. That means the normal Play button cannot verify its content or browser events.
Errors inside the inserted HTML can stop the exported page. A Script ID is also required before timeline functions can read or change the object. The practical test happens after export in a browser, with the page served in the same way as the final site.
Video needs conversion
Video export creates an uncompressed AVI file and has a documented maximum size of one gigabyte. Uncompressed frames grow quickly, so a long or large movie can reach the limit before its timeline ends. Hippani Animator does not directly produce MP4, WebM, or Ogg video in that workflow.
A separate converter must compress the AVI into a delivery format. That extra pass determines final size and image quality. Keeping the project and original AVI until the converted file has been checked prevents a failed encode from becoming the only copy.
Widgets need a builder
Widget export packages HTML assets for systems that can turn web content into a phone app. It does not create a signed store submission by itself. An outside build system handles the native package, and public distribution requires a signing certificate.
Orientation lock and audio can depend on plugins in that external system. The extension also changes by target: one builder expects a ZIP package, while another can work from a folder. Instructions that name retired online builders describe the old workflow and may no longer lead to a functioning service.
Keep exports separate
HTML, GIF, and video outputs solve different delivery jobs. An animated GIF cannot preserve buttons or form input. A video keeps motion and sound but removes interaction. An HTML page keeps interaction but brings browser and hosting requirements.
Hippani Animator works best when the target format is chosen before the project grows. The author can then test the right frame rate, avoid unsupported objects, and keep each export in its own folder. Reusing one folder for several attempts can leave old media beside a new page unless the clean-export option removes it.
