Hopper can disassemble binaries for Intel (32 and 64bits), and ARM (ARMv6, ARMv7 and ARM64) processors.
Yes, Hopper can disassemble iOS binaries. Please note that you will not be able to disassemble an application directly taken from your iTunes library because all these applications are ciphered using the FairPlay DRM. Hopper WILL NOT be able to read this kind of application! This is up to the user to first remove the DRM (various methods exist) before analyzing the binary with Hopper.
Hopper can read Mach-O binaries (Mac and iOS), PE32/32+/64 Windows binaries and ELF binaries.
Like any decompiler, Hopper is not able to fully recover a lost source code. The main goal of Hopper is to help you understanding the code you have not written. Even if the generated pseudo code is somewhat close to C or Objective-C code, it's, most of the time, not directly compilable. If you have lost your code, you should really consider to rewrite it instead...
Yes and no ... Hopper is NOT a tool that will teach you ASM: you should already have some ASM knowledge before using a tool like Hopper. That said, it's always a good exercise to read code using an interactive disassembler!
Yes! Hopper provides many tools to allow you to modify your binaries. You can use the embedded hexadecimal editor, ask Hopper to assemble a new instruction, or even use a Python script to modify individual bytes.
No, unfortunately I cannot continue to convert MAS licenses... At the beginning, I offered this possibility in order to help the first customers of Hopper to use the new version.
You will receive all the updates of the version 4.x.x, free of charge.
Please, take a look at this page.
Technically, both products are the same. The only difference is that a personal license is tied to a person, where the computer license is tied to a computer. Usually, an independent developer will prefer the Personal License, and companies will prefer Computer Licenses. There is no restrictions on a commercial, or professional usage of Hopper.
First, please note that this decision is not definitive.
When I started to work on Hopper 3, I wanted to greatly enhance the user experience of the OS X version, my daily used operating system. This is why I decided to use the latest technologies provided by Apple.
Today, it appears that the amount of work needed to bring all these features to the Windows version, especially considering the fact that there is only one developer, is far too important compared to the revenues generated by this version...
Another reason is that I'm really not a Windows user, and the technologies used to bring Hopper on Windows are clearly not well tailored for this environment. For instance, Hopper v3 uses ARC, which greatly simplifies the memory handling, and gives a speed boost to the whole software. GNUStep has support for ARC in the Linux version, using libobjc2, but this library was not yet ported to Windows. I started to work on this port, but, although I started to make some advances, there is still far too much work to make it work perfectly on Windows...
For all these reasons, Hopper Disassembler for Windows is currently in standby...