Going 64-bit is like going with a multi-core CPU for mobile. Will it give you a speed increase in certain situations? Yeah. Will it be faster overall compared to its 32-bit counterpart simply because it has 32 extra bits? No, it won't.
Technically true because of the bolded part, but utterly misleading (and the next paragraph of your post is utterly incorrect).
If Apple were to release a 32-bit A7 alongside the 64-bit one, they'd both perform equally well in about 99% of all tasks normally performed on mobile platforms.
The move to 64-bit means a change to the chip's interface with the rest of the world. Instead of taking two (or more) operations to do 64-bit math, it takes one. (Many 32-bit math operations can be done two at a time, as well.) Additional registers open up. It's things like this that give the 64-bit processors a speed boost over otherwise equivalent 32-bit processors. Some of it *is* "simply because it has 32 extra bits", but most of it is because of other architectural differences between the chips (such as those extra registers).
Perhaps you recall the change from 32-bit x86 processors to 64-bit ones? You know, where the AMD processors of the day *were* available in both 32-bit and 64-bit versions, made on the same process, at the same clock speeds. Identical software compiled for both processors ran faster on the 64-bit chips due to these same sorts of architectural differences.
Of course, this all happened back when Intel was still recovering from the evolutionary dead-end that was the P4, and was betting that the incompatible Itanium & Itanium 2 processors would take over as the 64-bit chip of choice, so it's been a while (10+ years now?). Its entirely possible that you're too young to remember it, or that you weren't as involved or interested in hardware at the time.
----------
When are people going to get that no matter how optimized and improved a 64bit software is, it eats up more RAM than the 32bit counterpart, so it is very essential to add more RAM if you're going with 64 bit hardware and OS.
And no I'm not asking an iPad with 8GB of RAM. But 1GB certainly meagre.
Yep. Memory usage increases with the move to 64-bit pointers. Not as much as you seem to be implying, though.
Each *pointer* will use 64-bits instead of 32-bits. Everything else uses *exactly* as much RAM as it used to. On average, having 64-bit pointers increases RAM utilization by about 5-10% compared to the same application using 32-bit pointers.
Some apps will see pressure based on this increase. Most won't.
----------
Only for applications that are are being bottlenecked by 32-bit architecture, which are rare.
The best way to explain it is that jumping from 32 to 64-bit doesn't offer any performance gains in and of itself, but it's less likely to get bogged down, because it can handle larger amounts of data being thrown at it more gracefully. Like if you have a game that's been compiled for both architectures, the 64-bit version won't have double the framerate of it's 32-bit counterpart. But if you were to start throwing in complex physics models, and higher end AI, a 64-bit processor running the same amount of cores on the same CPU architecture as a 32-bit processor would be able to leverage all that information a little better, leading to slightly improved framerates.
It wouldn't be a massive, game changing, difference, but it'd be measurable. Thought that advantage could be matched by a slightly quicker 32-bit processor. Really, the best places to see the real advantages in 64-bit architecture would be in movie editing with large files, 3D rendering, and the like. Anything that has to do with tons of raw data being tossed around and worked on. Things you're not currently doing on iOS, in other words.
Do you think a 64-bit email app will allow you to type out words faster? Will it send your messages any quicker? What about 64-bit Angry Birds? Will it allow for...what...more birds onscreen? Will it suddenly be better because you can stuff twice the amount of data into a 64-bit register? Hell, these apps aren't even coming close to saturating a 32-bit chip. 64-bit won't do anything.
You should stop. It's pretty clear that you don't actually understand what you're talking about. There's no need to continue demonstrating it.