We’re done!

Hi guys, long time no see, it’s been quite a while since our last post. Today we have an announcement to make: “We’re done”. No, we’re not done developing apps, we’re just finished with Manga Rock. It has been almost a year since we started developing for the iPhone and iPad, Manga Rock was our first application ever and it has been great. In a little less than 6 months, we have over 300 thousands people downloaded and used the app. The feedback we got was also very encouraging. People love Manga Rock.

The reason why we said that we’re finished with Manga Rock is the fact that we’re coming very close to our original goal: we wanted to provide the best manga reading experience on the iPhone and iPad.  As many of you may have known, we have been developing the iPad version of Manga Rock for quite some time. Today, we can tell you that the app is almost ready, we will be submitting it to Apple this Thursday. We can’t wait to show you what Manga Rock has become on the iPad (We rewrote everything from the ground up this time around). We’re calling it “Manga Rock Unity”.

Once “Manga Rock Unity” is available, we will be moving on to explore new ideas. Of course, that does not mean we will abandon Manga Rock at all. There will still be a team dedicated to maintaining and updating the app, you just will not see any new app under the Manga Rock’s banner, that’s all.

So yes, check back in a few days to get more info regarding Manga Rock Unity. We are super excited to show it to you guys. For now, peace!

Comments

comments

4 thoughts on “We’re done!

  1. Let me be the first to say HURRAH!!!!

    I just hope Apple doesn’t take their sweet time approving it for the app store.

    There was one annoying ‘bug?’ I noticed when I was reading stuff on the Manga Rock MF the other day. Some chapters of ‘World only God Knows’ is completely blank (nothing in it). I rechecked on MangaFox, and the chapter does indeed exists.

    I couldn’t figure out how to tell the app to try re-downloading the chapter again.

    I have encountered 2 instances of this peculiar bug.

Comments are closed.