The Flipnote Decompilation Project studies these supplied program images: [1]
- Japanese Flipnote Studio V1
- Japanese Flipnote Studio V2
- American Flipnote Studio V2
- European Flipnote Studio V2
- Japanese Ugoku Memo-Chou Viewer, a separate NTR application rather than an editor release
Why version and region matter
The V2 releases have much of the same application structure, with different function addresses, state offsets and resources. Japanese V1 also handles several saving and online-service operations differently. Check the release inventory and regional comparison before using an offset or parsing rule from another build. [1][2]
The research package identifies its inputs by cryptographic hash and documents what was extracted. It does not distribute Nintendo's program images. This documentation likewise describes behaviour and structures without bundling ROMs. [1]
Why a single address map is misleading
Japanese V1 differs materially from V2, including network transport and PPM serialisation. The three V2 regions share broad subsystems but vary in instruction locations, resource counts and some field offsets. Use a build-specific function map; a US V2 address should never be presented as a universal Flipnote Studio address. [1][2]
The ROM is more than ARM9
A DSiWare image can contain ARM9, ARM7, extended DSi modules, an executable header, NitroFS files and embedded archives. Some UI resources are held inside executable bytes rather than NitroFS. The Japanese Viewer is a separate program with its own resource arrangement, so it is useful for comparison but cannot stand in for a Studio release. [1]
Compare behaviour, not only bytes
The same page can appear in two releases even when they read different fields or handle failures differently. Functions at different addresses can also produce identical results for the inputs tested. Record both the shared behaviour and regional differences, especially in file parsing, online requests and saving. [1][2]