我不确定对于 Android 课程来说，让每个学生都有一个设备......并且让他们都是相同设备是否有意义。以相同的成本，您可以获得一系列具有不同特性的设备，并使用它们来帮助演示处理多种屏幕尺寸、多个 Android API 版本、具有 Google 地图的设备与不具有 Google 地图的设备等的技术。设备的此类变化是 Android 生态系统核心结构的一部分，因此，如果可能的话，将不同的设备纳入课程似乎是谨慎的做法。
I am not certain it makes sense, for an Android course, to have each student have a device...and have them all be the same device. For the same cost, you could get an array of devices of different characteristics, and use that to help demonstrate techniques for dealing with multiple screen sizes, multiple Android API versions, devices that have Google Maps versus devices that do not, etc. Given that such variations in devices are part of the core fabric of the Android ecosystem, it would seem prudent to make varying devices be part of the curriculum, if possible.
If you are stuck having to buy all of the same handset, I agree with nportelli -- all else being equal, I would try to stick to plain "Google Experience" devices instead of those with heavy customizations (HTC Sense, MOTOBLUR). Two likely candidates would be the HTC Magic and the Motorola Milestone, assuming the latter is presently available (not quite certain about that).
BTW, I am tentatively scheduled to be in Wroclaw the week of 7 December, to teach Android application development for a local firm. What's the best place in Wroclaw for pierogi? :-)
Handsets get updated every 4-6 months so whatever you buy now you will regret it later in the next year.
When you really need it then go and get one. No need to do it a year in advance.
Regarding Hero: the reviews I read didn't look impressive. It gives impression of a prototype before HTC releases something final. Lack of videocall cam is one disadvantage I see right now.
The official dev phone is the HTC Magic supposedly. I would not go with the Hero since it has a custom firmware and Sense. Should stick with a vanilla version of Android. Or just use the emulator.
If I were going to be debugging things on it, I'd think I'd prefer a phone with a physical keyboard, like the Samsung Moment.
Then again, probably the smartest thing to do would be to find out what the instructor is using and get the same phone. That way you can be fairly sure you won't get any compatability issues that nobody running the course has ever seen.
Would not recommend the HTC Hero. I develop on an HTC as well (Dream), and the problem is that it has a 320x480 resolution. By itself its not bad, but the users have (among others) Motorola Droids. The resolution there is up to (480 x 854).
So your programs will look nice on the HTC, and horrible on the high-res phones. I suggest going with a high res phone, where you have the benefit of switching resolutions. Knowing how to develop UI for different resolutions (and/or pixel density) is very important.
By the way: The Android simulator that comes with the SDK does not truly represent the font sizes of the real devices when dealing with high density. It has to be tested on a real device or it's a mess.
发布评论
评论（5）
我不确定对于 Android 课程来说，让每个学生都有一个设备......并且让他们都是相同设备是否有意义。以相同的成本，您可以获得一系列具有不同特性的设备，并使用它们来帮助演示处理多种屏幕尺寸、多个 Android API 版本、具有 Google 地图的设备与不具有 Google 地图的设备等的技术。设备的此类变化是 Android 生态系统核心结构的一部分，因此，如果可能的话，将不同的设备纳入课程似乎是谨慎的做法。
如果你不得不购买所有相同的手机，我同意 nportelli 的观点——在其他条件相同的情况下，我会尝试坚持使用普通的“Google 体验”设备，而不是那些经过大量定制的设备（HTC Sense、MOTOBLUR）。两个可能的候选者是 HTC Magic 和摩托罗拉 Milestone，假设后者目前可用（对此不太确定）。
顺便说一句，我暂定 12 月 7 日这一周在弗罗茨瓦夫，为当地一家公司教授 Android 应用程序开发。弗罗茨瓦夫哪里是吃饺子的最佳地点？ :-)
I am not certain it makes sense, for an Android course, to have each student have a device...and have them all be the same device. For the same cost, you could get an array of devices of different characteristics, and use that to help demonstrate techniques for dealing with multiple screen sizes, multiple Android API versions, devices that have Google Maps versus devices that do not, etc. Given that such variations in devices are part of the core fabric of the Android ecosystem, it would seem prudent to make varying devices be part of the curriculum, if possible.
If you are stuck having to buy all of the same handset, I agree with nportelli -- all else being equal, I would try to stick to plain "Google Experience" devices instead of those with heavy customizations (HTC Sense, MOTOBLUR). Two likely candidates would be the HTC Magic and the Motorola Milestone, assuming the latter is presently available (not quite certain about that).
BTW, I am tentatively scheduled to be in Wroclaw the week of 7 December, to teach Android application development for a local firm. What's the best place in Wroclaw for pierogi? :-)
手机每 4-6 个月更新一次，因此无论您现在购买什么，明年晚些时候您都会后悔。
当你真的需要它时，就去买一个。不需要提前一年做。
关于英雄：我读到的评论看起来并不令人印象深刻。在 HTC 发布最终产品之前，它给人留下了原型的印象。缺乏视频通话摄像头是我现在看到的一个缺点。
Handsets get updated every 4-6 months so whatever you buy now you will regret it later in the next year.
When you really need it then go and get one. No need to do it a year in advance.
Regarding Hero: the reviews I read didn't look impressive. It gives impression of a prototype before HTC releases something final. Lack of videocall cam is one disadvantage I see right now.
官方开发手机是 HTC Magic据说。我不会选择 Hero，因为它有自定义固件和 Sense。应该坚持使用 Android 的普通版本。或者直接使用模拟器。
The official dev phone is the HTC Magic supposedly. I would not go with the Hero since it has a custom firmware and Sense. Should stick with a vanilla version of Android. Or just use the emulator.
如果我要在上面调试一些东西，我想我会更喜欢带有物理键盘的手机，比如三星 Moment。
话又说回来，最明智的做法可能是找出教练正在使用的手机并购买同一部手机。这样您就可以相当确定您不会遇到任何运行该课程的人从未见过的兼容性问题。
If I were going to be debugging things on it, I'd think I'd prefer a phone with a physical keyboard, like the Samsung Moment.
Then again, probably the smartest thing to do would be to find out what the instructor is using and get the same phone. That way you can be fairly sure you won't get any compatability issues that nobody running the course has ever seen.
不推荐 HTC Hero。我也在 HTC (Dream) 上进行开发，问题是它的分辨率为 320x480。就其本身而言，它还不错，但用户拥有（除其他外）摩托罗拉 Droid。分辨率高达（480 x 854）。
所以你的程序在 HTC 上看起来不错，但在高分辨率手机上却很糟糕。我建议使用高分辨率手机，这样您就可以切换分辨率。了解如何开发不同分辨率（和/或像素密度）的 UI 非常重要。
顺便说一句：SDK 附带的 Android 模拟器在处理高密度时并不能真正代表真实设备的字体大小。它必须在真实设备上进行测试，否则会很混乱。
Would not recommend the HTC Hero. I develop on an HTC as well (Dream), and the problem is that it has a 320x480 resolution. By itself its not bad, but the users have (among others) Motorola Droids. The resolution there is up to (480 x 854).
So your programs will look nice on the HTC, and horrible on the high-res phones. I suggest going with a high res phone, where you have the benefit of switching resolutions. Knowing how to develop UI for different resolutions (and/or pixel density) is very important.
By the way: The Android simulator that comes with the SDK does not truly represent the font sizes of the real devices when dealing with high density. It has to be tested on a real device or it's a mess.