Reply With Quote
Well, if you're a developer, you would know that it takes more than "homework". And that's why you don't see tablet-specific versions of many Android apps. Again, not sure how this applies to ICS yet.
Actually, Android has done very well on the phone department. But you can't untie that with the market share they have in that area.
Well, if you're a developer, you would know that it takes more than "homework". And that's why you don't see tablet-specific versions of many Android apps. Again, not sure how this applies to ICS yet.
Was going by the article it said it was $150 for the new keyboard for the prime.
Lol ya im sure Apple is quaking in their boots. Remeber the Ipod killer Zune?
If you jailbreak all apps are free...
Yeah, but that is bull . (yes I know plenty of Android users who do this too and I get in their case about it too).
Okay i exaggerated there. Even though I have plenty of apps that I havent paid for I have spent probably around $1000 on legit apps. I won't bother trying to justify pirating apps.
Durr with that amount of money, you could've bought a decent laptop.
no it doesn't. If you wanna do a straight port from mobile app to tablet, all logic is separated from GUI. All you have to do is change the GUI and you are good to go
now, again I said if you wanna do a straight port. But tablet is a different physical media from mobile. So if you wanna build a real true tablet app, you would have to rething the entire application. So again, your point is not valid cause you anyway have to redo the application in this case. Ipad or Android. same thingAnd that's why you don't see tablet-specific versions of many Android apps. Again, not sure how this applies to ICS yet.
I already have a nice I7 laptop (Vaio)
Nope. The tablet API only showed up in Honeycomb, and Honeycomb didn't officially make it to a lot of phones. That's why ICS is important, because it merges the API on a single OS targeted both at phone and tablet. Now, if you target ICS, you can code towards both the tablet and phone.
Nope again. What Apple did right in iOS is to use resolution-independent UI from the get go, because they wanted to support rotation-aware apps. That actually ended up being the right call, because now the same concept expands to different screen resolutions.
Took us just a single day to have an universal version of our app that works natively both on iPad and iPhone. As long as you define how things are laid-out, your app just works, regardless of the screen size or whether it's retina or not.
that is exactly what I said. You have 2 choices let your Froyo app run in Honeycomb, or redo the GUI part to use Honeycomb optimized tablet APIs. Either way it is not a major problem. It's not like you are redoing your entire app
which is the case in Android. Again, a Froyo app will run in Honeycomb as is.Nope again. What Apple did right in iOS is to use resolution-independent UI from the get go, because they wanted to support rotation-aware apps. That actually ended up being the right call, because now the same concept expands to different screen resolutions.
Took us just a single day to have an universal version of our app that works natively both on iPad and iPhone. As long as you define how things are laid-out, your app just works, regardless of the screen size or whether it's retina or not.
I'm wondering if other places affected by this shortage (e.g. Bust Buy). I'm getting closer and closer to splurging on one for the holidays. Of course, this might not even be an issue up here.
waiting a week just to have it canceled blows.
I can't stand that kind of stuff. You know you have a popular product on hand. Bust that OUT.
Asus
Which is exactly what I was pointing out. You don't have to "redo" pretty much anything in iOS. As long as you wrote the app to be resolution-agnostic, and you mark the app iPad compatible, the OS will handle the UI to be tablet-native on a tablet, and phone-native on a phone. You write against the exact same API.
But it won't use tablet APIs... it's like non-universal iPhone apps running on the iPad.
Okay, not a developer, but I will say this. When iOS 4 came out, you could tell which apps were developed with iOS 4 and the Retina screen in mind and which ones weren't. I saw a lot of fuzzy icons and not so sharp displays for a few months while everyone caught up. Some apps improved vastly in terms of display when they added the little "updated for iOS 4 and Retina display" to the description.
Now that has to do with just the visual, but I'm sure it is a little part of developing on iOS vs Android that ElNono is trying to get at.
I have to say if the TP is as successful as the original, I could see Asus leading the android charge. They are coming out with a Tegra 3 phone next year and they are (at least IMHO) synonymous with quality. When I built computers, I used Asus components wherever possible. My current and previous laptops were asus and run great. If that quality and innovation continues to carry over to the mobile side, they could be a force to be reckoned with.
Same exact thing on Android
I don't agree that you can call an iOS phone app, a tablet app too. It's either a phone app that also runs on tablet, or a tablet app that also runs on phone. IMO those are 2 different platforms. A true tablet app is designed for the tablet from the groudn up.But it won't use tablet APIs... it's like non-universal iPhone apps running on the iPad.
Nope. You couldn't possibly have a tablet-UI when the API isn't there. That's exactly what ICS brings to the table.
It doesn't have to be like that. And certainly, that's the big plus you're getting for free here. The users get two different experiences, but the developer only had to write towards one API. And it's a big reason why there's so many native iPad apps out there.
That's why it's called universal, as opposed to a phone app. It doesn't just works on both, but they actually behave distinctly on both, but it's handled entirely by the system.
For example, when you display a popup menu, the API is exactly the same, but on the tablet it will display on a popup, where on the phone it will be a menu that slides from the bottom. Or when printing, you'll get the print options in a popup on the tablet, where it takes you to another screen in the phone. It's all handed by the system, and it's a time saver, because it does what's natural for that device, and I don't have to sit down and re-invent the wheel. Now, if you want to customize per device, you can do that too.
The convergence of APIs on ICS will hopefully prompt to the same kind of "smarts" on Android.
I am no expert on the subject, but the way I understand it this is what ICS' "Fragments" API brings to the table.
Actually, the introduction of the retina display is a good example. Everything still worked natively, no scaling on fonts, system controls, etc. The only thing that required a change was that if you used a custom image/icon/bitmap, you needed to include one with twice the resolution and name it <image>@2x.png.
That's it. You didn't even need to change the filenames on the program. The API automatically appends and uses the @2x if it's on a retina display and the file is there, otherwise it falls back to whatever was there and scales it.
And now we come full circle
Yes, that's what I read too, which is what's pointed out here:
http://buildmobile.com/whats-coming-...ream-sandwich/
Still not sure how much of a timer saver it is though.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions