It's supported in that it will render your IP.Content pages as they are in a web view, but it's still currently your responsibility to ensure they're rendered correctly for mobile. I'd like to at some point work on improving IP.Content's mobile capabilities. Calendar is not currently supported but it may be at some point in the future.
You've pretty much got it there. We'll still call out to the regular web pages for IP.Content data etc, but everything else will be displayed using a native view on the device.
No, you most assuredly don't have to create a new template for each product. When using IP.Content, you probably already have a page template- simply create your new pages and assign them to this template.
Unfortunately no, I don't believe you can do this in Articles, as they are merely database entries and from memory are not passed through the templating engine.
Unless I'm misunderstanding you, which is entirely possible, I don't think white label hosted forums embedded via iframe with different themes is within the spirit of the license agreement. I wouldn't really see that as a valid use case, personally.
(Disclaimer: personal opinion, not necessarily representative of IPS policy, etc)
Your idea strikes me as being considerably more flawed, unfortunately. If you provide people some anonymous way to indicate that they are not willing to pay and to "suggest a price", it's highly likely that rather than buying products, some individuals (I dare say, many individuals) will just run around "downvoting" prices in the expectation that they can get it cheaper.
If you don't like the price of something, do not buy it, and tell the author why not. Authors will value personally written, well thought out feedback considerably more than they will an anonymous click on a "too expensive" button. And frankly, if they respond to a suggestion that they rethink their pricing with public flaming or personal insults, you probably don't want to purchase off that person anyway. It's not hard to simply respond that they have considered your opinion but unfortunately will not be considering price changes at the time.
(Again, opinions do not represent IPS, so on so forth).
Regulating pricing is price fixing. And I also do not agree that there need to be more ways to influence pricing - you can choose to influence pricing by not buying the product, or you can contact the seller and let them know that you aren't happy with the price. These are the same options available to you if you were to walk into a WalMart or Target, neither of which offer an Establishment Fee or Retainer type system, or even ratings and feedback. Here at IPS, you can review a product if you buy it, peruse the support topic, contact the author directly, and rate the product. What more can be done?
(Disclaimer: views represented in this post are solely mine, and do not necessarily represent those of Invision Power Services, Inc)
It is widely considered to be very poor security practice to indicate for a failed login which aspect of the details is incorrect. As a general rule, no properly secured application will ever tell you whether it was the user name or password which is incorrect.
My personal opinion is that it is unlikely you'll ever see this.
Images aren't supported in chat, nor are text size or colour options. IP.Chat is intended to be a fast, lightweight chat solution with the bare minimum of formatting to keep chatting sleek and clean. A WYSIWYG editor would be kind of pointless if the only options supported are bold, italic and underline.
As Brandon said, not dead at all. I am currently waiting on some of the chaos from the 3.2 release to die down (every major release is somewhat chaotic, it's the nature of software development :)) and once that has flattened out then I'm looking to get through some rapidfire testing cycles, and release it at the same time as the new version of the iPhone app (which is already done, just waiting for Android to catch up).