Hi.
Answering the technical part of your questions.
With the Supernet Wallet and Iguana how will the internals of HEAT compare?
The HEAT client framework is a very large project it was written from scratch and uses the latest tech from front-end land.
I am not too familiar of the Supernet Wallet but from what I've seen it's internals are very similar to the generation 1 NXT client.
We did MofoWallet after that which has a more modern approach and uses newer frameworks such as Angular 1.
The current iteration can be considered third generation client, it's built up of web components, Angular 2 (styled code) and written in higher level TypeScript instead of plain Javascript.
As far as i understand your HEAT LEDGER wallet will hold the ability to hold multiple tokens and also then to exchange at market value between them.
Can you elaborate. A multiple coin wallet with internal exchange system?
Through the Services Architecture feature with which anyone can start offering services in a transparent and highly secured manner. It becomes possible for users to write services that for instance offer a Shapeshift type of service. To get things started we will be creating those services ourselves and publish the source code so others can take that and build on that.
It's through these external yet still communicating over the blockchain services that power this exchange system.
I also was super impressed by the instant message system inside FIMK which i assume will port into HEAT.
Will this be easy to use over smart phones. A secure instant messaging system will be how i get my friends to sign up and then pass them some HEAT.
That is exactly what the replication layer is all about. This layer replicates the unconfirmed transactions in real-time to a powerful MySQL database or other type of large data store.
Thats the only way to ever allow any serious amount of user numbers to communicate over the HEAT ledger network.
If we did not have such an external system (replication comes with an external API app which is a highly available Scala/Play! app that in turn is powered by the MySQL data) it would mean every phone in the world needs to connect to one or another HEAT server somewhere out there. And that would not scale at all. In HEAT the p2p/server app does nothing but that, it is all about the consensus mechanism, need to see inside the data? or listen in? then you go through the external replication layer which is meant to run on a powerful server(s).
The client framework has been put together with use on mobile phones in a browser and embedding into a native phone app container in mind.
