Although homebrew for the new DSi is still relatively quiet, here are a couple of resources to keep an eye on.
- DSibrew.org–Like its sister wiibrew.org, this site has the potential to be the place for homebrew developments. You’ll be able to see any DSi-specific tools for developing homebrew as well as more end-user apps.
- DSi google group–A discussion group for DSi homebrew, with some development resources made available.
- gbatemp–This has been an important site for announcements and discussions for GBA and DS homebrew, and I would expect it to remain so for the DSi. As of now, they have a dsi-specific forum, so you have to browse the existing DS forums. However, for now, this thread is worth watching, which, so far, doesn’t have much encouraging news.
- DSi Homebrew Channel–This is a forum for the development of a channel for the DSi along the lines of the Wii homebrew channel. However, this project is probably not relevant until someone discovers an exploit to allow for unsigned, or unauthorized, apps.
- wehackdsi–A blog posting news about DSi homebrew. The bloggers running the site don’t appear to do any hacking themselves but just report on what others are doing [a good service in itself].
- [updated] dsihomebrew–A new website/blog/wiki on DSi homebrew.
What might be encouraging is that, according to Bushing [of team twiizers], the DSi reuses the Wii security, which we know has already been hacked to allow homebrew. Of course, there’s more to it than that, as someone had to find a save file hack, which, more than likely, Nintendo has probably eliminated for the DSi.
Bushing in the gbatemp thread above notes that folks need to keep in perspective how long it took to get the homebrew channel working on the Wii, which was roughly 18 months. He wrote:
Yes, there are some similarities [between the DSi and Wii] — but not enough that you can just skip a year’s worth of hard work. Putting together the final artwork and coding is one of the last bits, and if history is any guide, it will just sort of fall into place once the technical side is ready. Even if you do put together a team now, you’ll probably lose half of them due to attrition before you actually have a chance to start coding.
The point is it’s going to take a while, so don’t get ahead of the first steps, and be patient. Okay, that’s two points.