Just could not get pass all the FUD The guy had and a lot of complete made up stuff.
The more I know about android, the more I hate it. It is a stolen idea, a copy cat that is not done right. Some of the core functions are just ridiculously stupid and immature. Why? Because it's a copy and they don't have time to do it right. They have to get it to market quick.
E.g.
- UI: why do android UI have to be so similar to iOS? Why do android UI have to be so similar to BB UI before that? Can android do something different? You mean to tell me there're just a certain number of ways to design a UI? iOS is just one way. This is the area I have more respect for even Window phone 7. At least they made a very different UI than iOS. Come up with your own design!
- Why do I need a third party app to open a documents? Why not built into to OS itself? This is a crucial feature. e.g. I have to have Quick Office installed to open docs, pdf, etc. On iOS, I can open those document in-app.
- Virus? ---- on a mobile device? --- ewwwww!
- Sandbox? What, no sandbox on android? You mean other apps can access my app data? Ridiculous
- Different resolutions and screen size is a joke. As a developer, making games, you have a system of math to calculate where objects are on the screen, animations, etc. I have to manually do this for all the screen size I want to have my game run on? How much money I have to spend to buy all the different devices? Ridiculous. In iOS, I just know the size is 320x480 or 1024x768, and i'm good to go. I'll know my game will run just fine on all iPod touch, all iPhones, all iPads.
You know all that shows that you really have zero clue how to developed and if you are I feel sorry for your employer because that shows that are you a crappy one. You SHOULD NEVER use hard code points for UI layout. It should always be handled by reference and relative. It is not that hard to address difference size and resolutions. Big time if you do it right to first time. Now if you are using crappy designs and coding standards then this is the least of your problems. You are doing it wrong to begin with.
As pointed out before Desktop have been handling this issue with zero problem for nearly 2 decades now with no issue. It is not that hard to do if you use proper standards.
- Emulator instead of a simulator? That's another ridiculous thing. It just painfully slow to test our your app in an Emulator.
Really? REALLY that is your argument? Each ones has it plus and minuses and besides you are doing it wrong if you are relaying on either one for the major testing. Simulators have other worlds of problems like they are using different hooks and compliled for a different CPU architecture. This can lead to what works great on the simulator crashing and burning on the phone. Plus it does cause the simulator to often times be more powerful than the phone really is. You should always be testing on the phone any how.
Emulators while slow CPU end they do not have the issue of different CPU architecture issues or massively over estimating the phones hardware power.
- IDE: what's your choices? Eclipse or others --- lol. Xcode and AppCode and even Visual Studio run around the stupid and unstable Eclipse.
[/QUOTE]
again goes back to clearly you do not develope. I have worked with Eclipse, netbeans, JCreator, Visual Studio, and played with Xcode.
Of those I dislike JCreator and Xcode the most. Eclipse has a very steep learning curve and its real power comes from plug ins. The more I use Eclipse the more I like it. I also really like Visual Studio. The fact that you seem to think Visual Studio is worse than Xcode also speaks quite a bit. Apple dev tools tend to lag.
Also Dev tools are not meant to be user friendly. They are designed to be highly customizable and give you tons of options in setting things up to how you want them. The average person does not need easy access. Eclipse you have to get over the learning curve to understand why it is so great.
Yes I thought about that but that's just an excuse. Microsoft use the touch screen but their OS look completely different from both iOS and android. They have some very different concepts in navigation and display information. For better or for worse is to each his own. But for that I respect Microsoft more. There are ways to do things. Sometime it's hard but that's why it's called innovation.
And iOS touch screen UI is orginal. That is hoot and a half. Sorry but it really is not. It is a basic grid layout that as been in use for over 10 years. I owned a palm pilot running Palm OS. Guess what it had a grid of icons, with 4 primary ones on the bottom. The fact that you think that iOS lay out is orginal is funny.
Andriod OS is farther removed from that basic touch screen lay out.
Multi touch has been around in since the 80's. kdarling has been working with it for a long time. The big thing that changed in 2007 is the cost of captive multi touch screens had finally gotten cheap enough and robust enough to be put in cell phones.