All Mangas Reader

Yep, I thought of creating such a class earlier but it's a lot of work...
This one seems to lack a lot of functionnalities...

As AMR's chrome version seems to be more and more stable... I am actually thinking of porting it to firefox.... in a few month....

Opera would be more easy but there is less people asking for it...

haha but i rarely use ff, i use opera relatively often. (Not as often as chrome, but I'd still perfer a opera ext over an ff one).

Well, I admit that if polo decides to do a browser port, I'd personally prefer an Opera port. On the other hand, the firefox well-managed extensions gallery and far-reaching userbase will allow for a huge influx of users. The user count, and therefore the donation count, will be far greater than what you could get from an opera extension. I'd understand if it were a simple matter of changing a few lines of code, but this is a pretty huge piece of software.

Actually, browser porting is a huge project and though it'll lead to some influx in users and donations, the more prudent market to compete in is the mobile one. If polo can create a nice app to keep track of manga from a phone, more than just a few people would be all too willing to put in a few dollars for it. On top of that, after looking through the android market (haven't checked the iphone appstore yet), I found that there are only three applications that are similar, and they don't work as well as advertised (they load only one page at a time, while they could be loading the next page in the background). And I'm sure there's more ideas that polo could come up with considering he made this kickass extension.

The truth is, eventually AMR is gonna reach the point where there'll be a lot fewer new feature requests. Furthermore, as polo mentioned before, chrome is becoming more and more stable, so there are far fewer bugs (i know there'll always be new bugs) but eventually, he'll have enough time on his hands to do a separate project. And I think the best project would be a mobile port rather than a browser port.

Of course, while i can say all this, I've *never* developed an android app (though i did try my hand at one or two and a few more on other OSes), it's probably much much harder than a browser port. So it's all up to polo and it's his decision.

Android OS porting isn't 'harder' than doing a browser port, it's more 'different'. Although I prefer the IOS API to the Android API...
The bigger issue is that there are a lot more challenges on the UI and design side for such a port, Screen size being the first issue.
So it would be less an issue of coding difficulty than design difficulty at least at first. Getting a really streamlined design that can gracefully handle the much more erratic bandwidth of cell phones is hard.

v/r,
Ike

aahh... I give up porting, very clueless

But on other hand, I spent 2 hours migrating my AMR reading list to Google Reader.

Still hoping AMR dev porting it to Opera though

aww, that's unfortunate, it's alright though, no worries! Better luck next time!