This project is read-only.

Rawr on the Droid and iPhone?

Topics: Off-Topic
Apr 7, 2010 at 7:06 PM

I love this program and would love to see a version on my Droid!!! Would this be at all possible?


Illrunyou - Lightbringer - US - Horde

Apr 7, 2010 at 7:17 PM

Short answer: No.

Apr 7, 2010 at 7:46 PM

Shorter response: FAIL!

Apr 7, 2010 at 7:52 PM

eww... I can't imagine running the optimizer on a phone, the battery would die before it finished.

Apr 7, 2010 at 8:01 PM

1) "No." is actually shorter than "FAIL!".

2) Apple doesn't even support FLASH on the iPhone.  I doubt they're even thinking about supporting Silverlight any time soon.

Apr 7, 2010 at 8:34 PM

Slightly longer answer from a Dev standpoint: Hell no. An Android port would be a waste of time, for obvious reasons, and an iPhone port would be a gigantic undertaking, which would result in a terrible app.

Slightly longer answer from a User standpoint: Think harder about it. The idea of "Rawr in my pocket" sounds great at first... until you think harder about it, and realize that it'd be a terrible idea. You wouldn't be able to optimize, the performance would be horrible, the UI interaction would be extremely restrictive, etc.

Apr 8, 2010 at 3:35 PM

Already doing this  :-D

Although I'm cheating.  I'm using my mobile to get a Remote Desktop session on my home PC.  It has some practical issues, mainly dealing with the small screen. but it works. And it works at acceptable speeds to update the screen.

Developing on the mobile (even with this) is still a no-go, mainly because of the small screen and because typing in lots of text still is annoying enough to pull out my hair.

I agree with my fellow devs above that while it sounds like a good idea, a native mobile version of Rawr would probably be a bad idea.  For one, rawr needs a connection to internet for many of it's features, and unfortunately mobile internet fees are still on the somewhat high side.  Local storage requirements would be an issue (itemcache, icons...), Memory requirements would be an issue, and of course CPU resources would be an issue, many the features in Rawr only work well because it can use multiple CPU cores off your desktop PC.  Plus your PC probably is a couple hundred to thousand times faster than the CPU of your mobile.


Apr 9, 2010 at 11:15 PM

Actually, the WoW Amory app for the iPhone is quite fast and easy to use:

And if Rawr can build in Mono, there are supposedly ports available for the iPhone and Android:

Not to say that it wouldn't be an enormous amount of work though!

Apr 9, 2010 at 11:27 PM

Armory != Rawr.

Apr 10, 2010 at 12:24 PM
Edited Apr 10, 2010 at 12:38 PM

Also Apple just updated their stuff for OS4.0:


3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).


This implies that any Mono solution is out of the picture.


TLDR; We will have to recode Rawr from scratch to make it viable for iTune Store.

Apr 10, 2010 at 3:27 PM

Devices generally lack the processing power and/or memory required to do any real gear optimizing. You'd basically be carrying around another version of the Armory app if you take the optimization stuff out. That'd be a waste of time for all the people who already put in their precious free time making the current version what it is. It's a grand idea to have the power of Rawr in your pocket, but I'm afraid the hardware isn't there yet.

Feb 8, 2011 at 11:41 PM
I think the amount of money one could make on even a simplified version of rawr for these devices is being underestimated. I'd buy it. Is there any way to have a separate machine do all the calculations and simply interface using the phones? Like a beefy server(s)? Or with one's own pc even if they had to have an app running in the background?
Feb 9, 2011 at 7:55 PM

I think you'd end up needing to do all the item caching and optimizing in the cloud, making the "app" a UI only. That's bad, because there'd have to be a cost associated with storing the content and all the processing (optimizing). So it wouldn't be something you could buy once for $0.99 and have it work forever. The $0.99 would be for the UI and then you'd have to have some kind of subscription model for actually using Rawr.

Sounds like a headache.

Feb 10, 2011 at 11:10 AM
Edited Feb 10, 2011 at 11:10 AM

If we were making rawr because it can make us more money, you'd already be seeing that in rawr now with advertisement banners both in the online and offline version and additional "usefull stuff" being combined in the rawr installer.

it's not there now.

Hence, we're not doing it for the money.

If we REALLY wanted to do what we do for the money, there are ways to generate more income per time unit spent on it than for making a mobile version of rawr. But yes, markdall hit the nail on the head. If you can't do processing on the mobile itself (too slow, too draining on the battery), then you have to do it on a server somewhere, that server needs to be payed for, so rawr wouldn't be a single payment thing. You'd have to pay for the app, and then pay fees for the usage service.

You could make it work with the CPU power of your home PC, but that would make the app considerably less useful for many and thus make less money, and even if it wasn't for the money, it'd mean less potential users meaning lots of effort for little gains.   To put it in more realistic terms however. unless one of the devs owns an iphone and rly rly wants this feature, it's just not going to happen.

That said. If you don't mind this working over your own PC, then get an RDP client (terminal server) for the iphone/android (there's several) and control your desktop from your iphone. Screen size will be a bit of an issue but it does work.

Feb 13, 2011 at 8:00 PM

Now that Nokia and Microsoft have allied, here's hoping to see some kind of Silverlight compatibility on phones --> Rawr.Mobile :)

Feb 13, 2011 at 8:15 PM
Edited Feb 13, 2011 at 8:28 PM

So, to recap:

  1. No.
  2. Phone's don't have the processing power to handle Rawr, and won't until at least 2012 when dual and quad core phones come out at decent speeds and larger memory caches.
  3. Apple's restrictions on how apps can be coded eliminate Rawr's C# back end off the bat, not to mention the Silverlight aspect. You would have to jailbreak the iPhone/iPad just to install it (if we had an iPhone/iPad version).
  4. A cloud setup where the phone serves as just a UI function talking to a Server that does the processing would be expensive, difficult to set up, and not fun to maintain.