我应该学习 Google App Inventor 作为 Android 版 Java 的补充吗
只是好奇。我已经是一名 Java android 人员，但对 android 的新应用程序发明者测试版感兴趣。 我想知道“真正的”开发人员在想什么。很多人想开发一个 Android 应用程序，但没有真正的编程技能。似乎很多应用程序都可以用应用程序发明者编写 - 不确定，因为我还没有尝试过。
Just curious. I am already a Java android guy but am interested in the new app inventor beta for android.
I was wondering what "real" developers are thinking. A lot of people want to develop an android app but don't really have programming skills. Seems like a lot of apps could be written with app inventor - not sure since I haven't tried it yet.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
希望这能为那些刚刚听说 App Inventor 的人们澄清一些事情。 （请记住，App Inventor 目前还处于测试阶段，因此所有这些都可能会发生变化。）
如果您有兴趣尝试它提供的一些功能，但没有时间或兴趣参与其中完整的 Android SDK，那么 App Inventor 可能非常适合您。
App Inventor 的界面提供了一些您在 Android SDK 中找不到的独特功能，并且非常容易掌握（请务必查看 块编辑器的快捷方式，否则可能很快就会变得乏味）。它可以对界面和支持逻辑进行实时调试和实时编辑。如果您还不太确定做某事的正确方法，那么仅此一项就可以减少时间和挫败感，并且可能是整个系统中我最喜欢的功能。新开发人员会特别发现，在手机上实际看到他们的更改得到实施，而无需等待编译和运行，这是非常有意义的。如果您尝试通过 SDK 学习知识，与传统的编译和等待过程相比，它可以节省大量时间，并且更容易适应。
如果您一直在使用 Android SDK，并且只是想尝试 App Inventor 支持的新功能，但您没有时间或不太确定如何实现，那么它也非常方便。只要您将注意力集中在 App Inventor 支持的功能上，就可以让您的手机在几分钟内完成您可以看到和使用的操作，从而为理解问题提供宝贵的见解。即使是经验丰富的开发人员也可能会欣赏这一点。
当你开始碰壁时，真正的问题就更多了。你根本无法攀爬的墙壁。您很快意识到必须了解该工具的局限性，否则您可能会花费大量时间尝试做目前不可能的事情。如果您经常使用 App Inventor，迟早您会发现自己处于这种境地。
所有编码都是图形化的。
查看一些演示或如果您不明白块编辑器的含义，请参阅该内容。在这些大的彩色块中设置值与使用 App Inventor 获得的代码一样接近，无论好坏。
如果您以前有任何开发经验，您会发现自己渴望能够进行一些简单的编码来补充您正在做的事情。或者至少能够导出项目并从 Java 中中断的地方继续。抱歉，这不是那种工具。
当你到达这一点时，你唯一的选择就是重新开始编写代码，或者忘记它，至少直到所需的功能被添加到 App Inventor 中（这可能永远不会）。这可能会激怒很多人并让他们放弃。
如果您正在考虑进入 Android 开发，我认为从 App Inventor 入手没有问题。它甚至可能会节省您数小时的精力，否则您可能会花在尝试理解一些概念上，这些概念在您执行这些概念时很容易理解，但如果您是第一次构建它们，则会有点混乱。
如果您是一位经验丰富的开发人员，或者希望赚钱或获得超越概念的 Android 体验，那么这绝对不是您的最终目的地。如果您是刚接触编程的学生，这可能是一个很好的环境，有足够的挑战和发挥的空间，以保持您对大量项目的兴趣。
尽管存在当前的限制，我仍然将 App Inventor 视为学习新概念的宝贵资源和尝试新想法的游乐场。事实证明，它是向某人介绍 Android 开发的一个很棒的工具，并且在向某人介绍一般编程时，它可能会达到您所要求的效果。
Hopefully this clears up some things for people that are still just hearing about App Inventor. (Keep in mind App Inventor is extremely beta right now, so all of this is subject to change.)
If you're interested in playing around with some of the features it offers and haven't had the time or interest to get involved with the full Android SDK, then App Inventor is probably a good fit for you.
The interface of App inventor offers some unique features you won't find in the Android SDK and is pretty easy to get the hang of (make sure to look at the shortcuts for the Blocks editor, or it might start to feel tedious real fast). It has live debugging and live edits to both the interface and the supporting logic. That alone cuts down on time and frustration if you aren't quite sure about the proper way to do something yet and is probably my favorite feature of the whole system. New developers will especially find it rewarding to actually see their changes implemented on their phone without waiting for things to compile and run. It is a huge time saver and much easier to get used to than the traditional compile and wait process you face if you are trying to learn things through the SDK.
It is also quite handy if you have been playing around with the Android SDK and simply want to try something new out that App Inventor supports that you haven't had the time or aren't quite sure how to approach yet. So long as you keep things focused on features that App Inventor supports, this can provide valuable insight into understanding a problem by getting your phone doing something you can see and use in a matter of minutes. That's something even seasoned developers are likely to appreciate.
The real problem is more when you start hitting walls. Walls that you simply can't climb. And you quickly realize that the limits of this tool must be understood or you will probably spend a lot of time trying to do something that just isn't currently possible. Sooner or later your going find yourself in this position if you use App Inventor very much.
All coding is graphical.
Look at some of the demos or screen shots of what's available through the Blocks editor if you don't understand what that means. Setting values in those big colorful blocks is as close to code as you will get with App Inventor, for better or worse.
If you have any previous development experience, you are going to find yourself longing for the ability to do some simple coding to supplement what you are doing. Or at least the ability to export your project and pick up where you left off in Java. Sorry, this isn't that kind of tool.
Your only options when you get to this point are to pick up and start all over in code or forget about it, at least until the desired feature gets added to App Inventor (which may be never). That right there likely to irk a good number of people and turn them off to it.
If you are looking at getting into Android development, I see no problem with starting out with App Inventor. It might even save you hours of effort that might otherwise be spent trying to wrap your head around some concepts that are simple to understand when you do them, but a bit confusing if you are building them for the first time.
If you are a seasoned developer, or looking to make money or gain Android experience beyond just the concepts, this isn't your end destination by a long shot. If you are a student that is new to programming, this is probably a good environment with sufficient challenges and room to play around in to keep your interest for a decent amount of projects.
Despite it's current limits, I still see App Inventor as valuable resource to learning new concepts and as a playground for trying out new ideas. It is proving to be an awesome tool for introducing someone to Android development, and would probably do as good a job as you could ask for when introducing someone to programming in general.
我已经使用它一段时间了，我的想法是它非常适合：
随着该工具的发展，它将允许更多功能丰富的应用程序（它已经允许与其他后端程序集成等）。目前的屏幕设计非常基础，但很快就会得到改进。
总的来说，我认为如果您了解 Android 的 Java，那么您将能够在一小时内学会 Google App Inventor 并开始制作一些功能性应用程序。您可能会发现它更适合构建某些应用程序，或者您可能更喜欢坚持使用当前的工具。
对于想要开始编程的人来说，我认为这是一个很好的介绍。他们可以专注于逻辑和程序设计，而不是设置 IDE、代码结构和语法。另外，他们在编码时会看到结果。
回答你的问题“我应该学习它吗”。我建议你玩一个晚上——这样你就能很好地感受到它。
I have been playing with it for a bit and my thoughts are that is is great for:
As the tool develops, it will allow more feature-rich applications (it already allows integration with other back-end programs, etc.). The screen design right now is very basic, but will be improved soon.
Overall, I think that if you know Java for Android, then you will be able to pick up Google App Inventor within an hour and start making some functional apps. You might find it more suitable for building some apps, or you might prefer to stick with your current tools.
For people looking to start programming, I think it is an excellent introduction. They can concentrate on logic and program design, instead of setting up their IDE, code structure and syntax. Plus they will see results as they code.
To answer your question 'Should I learn it'. I would suggest that you play with it for an evening - that is all it will take you to get a good feel of it.
它可能不会让你成为更好的开发人员，但所有知识都是好的，所以它不会有坏处:)
无论如何我打算尝试一下。
It probably won't make you a better developer, but all knowledge is good, so it can't hurt :)
I plan to play around with it anyway.
对于任何“我应该学习……”问题的一般答案通常是“是的，了解一些东西不会有什么坏处。”从实际的角度来看，我会跳过它。这类事情通常都是好主意，但永远不会流行起来。当然，对于非程序员来说，这可能是一种构建非常简单的应用程序的好方法，也许真正的程序员可以用它构建一个引人注目的应用程序，但看起来如果你是一名程序员，使用 App Inventor 的好处似乎并不那么引人注目。
The generic answer to any "Should I learn ..." question is usually "Yes, it can't hurt to know things." From a practical standpoint, I would skip it. These sorts of things are usually nice ideas that never catch on. Sure this might be a neat way for non-programmers to build very simple applications and perhaps a real programmer could build a compelling application with it but it looks like if you are a programmer the benefits to using App Inventor don't seem that compelling.
我还没有检查过，但我认为它可能值得一看，以帮助 UI 开发。大多数软件工程师擅长真正解决软件问题或为应用程序提出很酷的想法，但当涉及到 UI 设计时，我们发现了很多障碍。至少我自己，一直习惯和UI设计师一起工作。
老实说，我不喜欢生成代码的工具（除了 WSDL 到 java 或 java 到 WSDL），但我发现自己在出现问题时花费的时间比我花的时间更多。从头开始编写应用程序...
I haven't checked it out, but I think it might be worth a look to help in UI development. Most software engineers are good at really solving problems with software or coming up with cool ideas for apps, but when it comes to UI design we find a lot of obstacles. At least myself, I've always been used to working with UI Designers.
I honestly don't like tools that generate code, (except WSDL to java or java to WSDL) but pretty much anything else I find myself spending more time trying to trouble shoot an issue when it comes up than the time I would've spent writing the app from scratch...
Appinventor 非常容易学习，我建议同时选择这两个选项。
将大部分时间集中在主要开发环境上，并在后台学习 AppInventor，让自己休息一下。
Appinventor 的优点是您可以组合相当复杂的应用程序
在相对较短的时间内。
它也非常宽容，例如，如果您有一个数字变量，您可以将其视为字符串或数值，这意味着您可以将其放在一起
原型制作非常容易和快速。
如果您想要快速组装一个应用程序，Appinventor 可能会更好
选项，如果你需要更强大的东西，更多地控制你的用户界面等，那么
可能需要更复杂的开发环境。
Appinventor 如此易于使用和学习，您可以为自己提供更多选择。
Appinventor is so easy to learn, I would suggest go for both options.
Concentrate most of your time on your main Dev environment and learn AppInventor, in the background, to give yourself a break.
The advantage of Appinventor is you can put together reasonably complex apps
in a relatively short period of time.
It's also pretty forgiving, for example, if you have a numeric variable, you can treat it either as a string, or a numeric value, meaning you can put together
prototypes pretty easily and quickly.
If you want an app putting together, quickly, Appinventor might be the better
option, if you need something more powerful, more control over you UI etc, then
a more sophisticated Dev environment might be called for.
With Appinventor being so easy to use and learn, you're giving yourself more options.
考虑到 Eclipse 似乎引入了我无法找到且无法删除的错误——即使在使用 Project-Clean 之后，我也期待任何替代方案。
Considering Eclipse seems to introduce errors I can't find and can't remove--even after using Project-Clean, I'm looking forward to any alternative.