I need your opinion.

First of all: Good luck with your App!. Secondly, I would like to ask if you know of any App out there that takes 200MB? Seems to much for an App, but I'm not really that much into the apps world. Whats it is your App about, can you share some words on it? :D

*I said a stupid thing

Well I guess it depends on what that app will do. But honestly, I think that with todays tech progress, with all data packs, wifi and smartphones being small computers with big discs I would say go with 200mb and good quality.

I know nothing about making apps, but maybe, if this isn't hard, make two versions? One main (200mb) and one 'lite' (50mb) for people with older phones.

50 mb app with not so good quality?
How not good is uncompressed than compressed version?

@edit: If the difference will not be too large (or very small), it suits me 50 mb

why do you use gifs instead of video files?
is it a limitation by the app or just for compatibility with devices?

for an app, smaller is better IMHO
and dont forget that the app usability/info comes first rather than nice looking gif

Im in the 50 mb crowd the smaller the better especially if they are able to do the same/similar things
200 mb is reaching to the I would not even bother looking at number
Comparing the two pictures it is not worth the 4x size for a not so huge difference

It seems like the people here are fairly split on their views

bro, app is all about funcionality.
I myself have some shitty look apps that totally do the work that most pretty ones doesn't...
why don't you add both versions? isn't the same script (outsider here)?
maybe you want to make a "addon" that you choose to install separately. (this is getting more and more common but to new funcionalities, not looking quality)

btw, I will analise which one runs better and do the job. my choice is based on these two criteria only.

I believe you could get it to work both ways, by having the higher quality gifs as an optional download, and the lower quality as default. However, I don't know the environment you're working with, so it might be more difficult to implement than I think.

A possible suggestion is you could just use a cycle system of images, for instance, you could use 5 different pictures that represent a hero (e.g. Doom) that automatically cycles. This keeps it somewhat less repetitive whilst keeping space low. Do take this comment with a pinch of salt, since I'm not really answering the question x)

GIF is inefficient, use something better such as webm.

It depends on the platform. For my PCs I wouldn't hesitate about the size. For the phones or tablet, it would need to be one awesome app to justify the size. Please clarify which platform this app is for...

SuperDuperApp 50MB
SuperDuperApp HD 200MB

OR

SuperDuperApp 50MB with option to download higher res graphics in-app

My 2c :)