This thread is more about "WP8" platform in general.(wp8 as a whole not about 820)
Do you really think that a normal consumer understands these reasons ? Only thing they care about is "Works or not"
This thread is more about "WP8" platform in general.(wp8 as a whole not about 820)
Why would simple apps need 1 gb ram is the main issue discussed.
Read what "travisel " wrote above.Looks real somewhat.
Looks like people who currently have 820s 920s and 8X's , Ativ's are in situation what travisel is describing.
I read this thread and these days how interesting the thread is depends on the number of teas I drink while reading it. 3 for this one.
While there are people who have clearly moved on to other platforms and aren't happy with the way Windows Phone has evolved and they have super major contributions in this thread, I don't think most of them are valid.
Why isn't anyone looking at it from this perspective : You got a phone with low spec i.e 512 RAM right? You paid less money than the guy who paid for Lumia 920 right? You did not buy a flagship device, right? Now don't give me an example of iPhone because there is always ONE iPhone per OS iteration. For Windows Phone 8 OS, there are plenty of phones. Low ends, mid range, flagships. This is same with Androids right? If you pay for low end phone, don't expect high end performance or apps, simple. I wouldn't. I don't know why would you. If apps don't work on high end Lumia 920 e.g. Tentacles or Viber HD - I would be totally pissed and I am about those apps.
Let's compare low end WP with low end Androids and let's talk about the performances. Back in the day, Windows Phone ads (those who don't own WP anymore, you will know what I'm talking about) that showed how smooth and non-laggy the device is compared to others were everywhere. The point was - WP doesn't lag, WP is consistent. Pick up a low end WP and pick up a low end Android both with latest and greatest OS updates on them. WP will not lag, it won't **** out, it won't force close. However in Android it will. Now what use is that TuneIn radio or Temple Run or whatever you lot are on about, if it will make my phone laggy? If I wanted that, I would surely buy an Android anyway. WP came out with providing a fresher and better user experience. It's focused on user experience. It wasn't focused on apps even at the beginning. Everything was about integration (remember old days, veterans?)
I understand the point that some apps just don't need 1GB RAM e.g. TuneIn and they shouldn't demand that - but probably they've done their home work and it might be OK on Android to run in the choppy environment, by MS standards if it doesn't feel optimized with 512 MB RAM. That when 1GB RAM version is released and then after further development, optimization 512 one is released. There were few games recently that released in this fashion right?
I think most of the people on WP who have used it since 2010 or in 2011, would vote for stability, speed and fluidity of the OS anyday over the most popular app in other marketplaces. However, those switching from other OS always want those apps because to them even a laggy app doesn't feel any different than what they had on their previous phone. I don't know. My tea is finished, I need to make a brew now.
Because its developers are too lazy to optimize it? OR they just want to release it ASAP then optimize it later? For god's sake. Why you guys keep blaming Microsoft for other developers' laziness? Cause that's the most nonsense thing I've ever read :| Not to mention the post that compare windows phone store with appstore...
You wonder why a simple app needs 1GB of RAM? Why don't you just go ahead and put your question to its developer? Don't they know it best?
Oh, and yes! Did you ever try to install and play some games like angry birds on a low end Android phone (even some mid-end ones)? Cause I did, and the game is just unplayable. YES, it can be installed, it can run to menu, it can process to game, but after then is laggy, freezing and buggy... So what's the point?
Here one for you....do you believe Windows "Blue" WP9 update for WP8 memory base will be?
- 512MB
or
- 1GB
I believe "Blue" update for WP8 will need 1GB RAM! Would this **** off people with 512MB Ram WP8? So the only update's 512MB WP8 users get is GDR1/GDR2/GDR3 and no Blue?
Sounds like WP7 256MB Ram all over again? WP8 512MB Ram users in the same boat as last generation.
New WP9 "Blue" using new next generation Snapdragon 800 series MSM8974 with Adreno 330 and 2GB Ram will make my 1GB ATIV S WP8 Low end user!! I know this and you know this? Life span of Smartphone hardware now days is 6 months! Every year it's doubling!
Software is so far behind new hardware people are starting to see no support for older hardware.
Good news is WP9 hardware Snapdragon 800 series will be faster than Galaxy S4 Snapdragon 600 series used in north America.
If your a developer now days with choice of RAM of your APPS what would you use?
- 256MB WP7
- 512MB WP7.5/WP7.8/WP8
- 1GB WP8/WP9
- 2GB WP9
?
iOS devs for iOS original apps go out of there way to optimize, bug fix and add features. The same as for WP original apps as well. Take Amazing Weather, look how far it's come.
I don't understand why you are so angry at MS. Did MS developed and published those games? No they did not. The developers choose to support only 1gb devices. Blame them. Contact those developers and complain that you want to buy their game and so they should make a 512mb ram version. Then they will spend the time and make it for 512mb devices. Blame MS for the apps they make not for apps made by others.
As for the platform moving fast. What does that means? I'm a company I'm making a game. I choose to support wp8. I then hire some wp8 programmers or retrain my programmers to work on wp8 devices. This takes between 1 month to 2 month. This process of course starts in November when they have the sdk and phones the phones at their disposal. There comes December with winter holidays. Actual work begins in January. It takes 2-3 month to make a good game so what do you expect? How fast is fast in your dictionary? Software products as other products need time to be made and tested. Seams so few now remember the android launch and it's problems and lack of apps in the begging and it's slow speed.
it's easier and more cost productive, to be lazy and not make your app shine but be there fast and with as much effort as possible. When a streaming app will need 300 mb to play some music then something is totally wrong in this world.
I work as a software developer (not for mobile devices however) and I can say that you have the wisdom of the falcon. It basically boils down to this.
But to be honest, I have no clue where you got those absolute numbers from.
On 512 MB devices Apps can use up to 150 MB of Memory. If they exceed that threshold the App will be killed by the OS. On 1 GB devices it's up to 350 MB. This does not mean that the OS is taking up all the rest but there is reserved space for Background Tasks like a Navigation App running in the Background or Skype waiting for incoming calls.
Certain Apps can't run with only 150 MB of usable Memory - especially games, so developers set a flag in the App so it can't be installed on low Memory devices.
The Memory is reserved. The reason is that the System should work predictably - both for users and for Apps. If I have a Navigation Software running in the Background it Needs a guarantee that it will have enough Memory available. I can't just stop Navigation because the Facebook App is loading a big Image. Or if I receive a Skype call I want to talk to someone but perhaps would not want my currently active App to just be closed down because it takes too much Memory. So: no, the Memory is not unused. If Apps don't use their allotted share it is also used to Keep several Apps available for fast switching (e.g. Twitter is still in Memory but asleep).
That actually is an improvement over WP7 where an App was regularly only allowed to use 90 MB of Memory. This was not enforced by the OS so you could go above it if there was enough space available. The Problem was that at some Point it would run out of Memory and then would be killed. That would sometimes happen at 90 MB, sometimes at 150 MB. So a developer could test his App on his device without background Music, etc. and see it crashing all the time on people's devices. This Situation can no longer occur.
The Basic Problem is that Smartphone OS's don't use virtual Memory like on a PC. There if you run out of physical Memory Little used data is swapped out to the hard drive (which slows the System considerably). This normally isn't done on Smartphones because it is taxing on the Flash Memory. 256 MB WP7 devices still implemented it to allow them to even run 90 MB big Apps and Background process were completely deactivated on those devices. WP8 also Needs more Memory for the OS itself than WP7 did.
Why isn't anyone looking at it from this perspective : You got a phone with low spec i.e 512 RAM right? You paid less money than the guy who paid for Lumia 920 right? You did not buy a flagship device, right? Now don't give me an example of iPhone because there is always ONE iPhone per OS iteration. For Windows Phone 8 OS, there are plenty of phones. Low ends, mid range, flagships. This is same with Androids right? If you pay for low end phone, don't expect high end performance or apps, simple. I wouldn't. I don't know why would you. If apps don't work on high end Lumia 920 e.g. Tentacles or Viber HD - I would be totally pissed and I am about those apps.