对于小型 iPhone 应用程序项目来说,有哪些好的规范/要求文档项目?

发布于 2024-09-14 20:09:27 字数 405 浏览 5 评论 0原文

我正在为一个小型 iPhone 应用程序原型项目编写一份简短的规格/要求文档。描述基本功能和行为对我来说不是问题。但是,由于我的移动应用程序和 iPhone 开发知识非常薄弱,我不太确定这样的文档中还应该包含哪些有关最佳实践等的内容。

示例:在我的编程世界(服务器端 Java)中,当指定外包项目时,我声明该项目必须通过 FindBugs 的静态错误分析。

示例:我了解 Apple 不希望应用程序开发人员调用某些 API 调用。这些可能是应用程序被应用程序商店拒绝的原因。但我不知道如何表达我们希望苹果的指导方针得到尊重。 (我什至不知道如何测试这一点。)

我应该在专门针对 iPhone 应用程序开发的两页需求和规范文档中包含哪些内容?

I'm whipping up a short specifications/requirements document for a small prototype iPhone app project. Describing the basic functionality and behavior is not an issue for me. But, since my mobile application and iPhone development knowledge is very weak, I'm not really sure what else should be in such a document regarding best practices and such.

Example: In my programming world (server side Java), when spec'ing a project for outsourcing, I state that the project must pass static bug analysis by FindBugs.

Example: I understand that there are API calls Apple does not want app developers invoking. These can be cause for having an app rejected from the app store. But I'm not sure how to say that we want Apple's guidelines respected. (I don't even know how to test for that.)

What should I include in a two-page requirements and specification document that is specific to iPhone app development?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

迷路的信 2024-09-21 20:09:27

这些是您可以提及的一些要点
1.应用程序应根据Apple的用户界面指南进行开发
2. 项目内部不应该有任何私有API调用,导致应用程序被苹果拒绝
3.应用程序运行状态下不应出现内存泄漏或内存分配过多的问题
4. [您的选项] 之后的所有 iOS 均应支持该应用程序。 (主要取决于应用程序使用的功能)
5. iOS 4应支持该应用
6. 该应用程序应该在 iPhone 4 上正常运行

希望这有帮助

These are some points you can mention
1. The application should be developed based on Apple's user interface guidelines
2. There should not be any private API call inside the project which makes the application rejected from apple
3. There should not be any memory leak or excess memory allocation issue during the application running state
4. The application should be supported in all iOS after [your option]. (It mainly depends on the features used in the application)
5. The application should be supported in iOS 4
6. The application should work properly on iPhone 4

Hope this helps

芯好空 2024-09-21 20:09:27

任何头文件或文档中都不会提及私有 API,因此测试这一点的一种方法是手动浏览源文件并搜索头文件和文档中使用的函数以查看它们是否存在。如果项目增长,这确实不可行,但对于一个小型应用程序来说,它可以工作:)

A private API wont be mentioned in any header file or in the documentation so one way to test for that would be to manually go through the source files and search for the functions used in the headers and documentation to see that they are there. It's really not feasable if the project grows but for a small app it could work :)

握住我的手 2024-09-21 20:09:27

除了这里已经提到的事情之外,我还想补充一些:

  • 应用程序应该快速运行,任何操作都不应该给用户这样的感觉:设备正在做某事
  • 一切需要一段时间的事情都应该在后台运行,甚至更好,可以取消
  • 确保仅在有意义但不是太少的情况下使用动画。流畅的感觉对于用户来说是最重要的。
  • 这些事情还意味着您尝试最小化应用程序启动时间。

通常有一些技巧可以解决性能问题。用户从应用程序中获得的感觉不是它有多快,而是感觉有多快。在我看来,除了没有崩溃等明显的要求之外,这是最关键的要求。

In addition to the things already mentioned here, I'd add a few more:

  • The app should work fast, no action should give the user the feeling, the device is doing something
  • Everything that takes a while should be run in background and even better, be cancelable
  • Make sure you use animation only where it makes sense but not too seldom. A smooth feeling is most important for users.
  • These things also imply that you try to minimize application startup time.

There are often tricks to work around performance issues. The feeling a users gets from your application is not how fast it is, but how fast if feels. In my opinion this is the single most critical requirement, besides obvious ones like no crashes etc..

三生池水覆流年 2024-09-21 20:09:27

使用私有API有什么问题?

此外,我想补充一点,它将在 iPhone 3G、3GS、iPod、4 上进行测试,所有设备均运行 iOS4 和 3。

What's the problem with using a private API?

Moreover, I would add that it will be tested on iPhone 3G, 3GS, iPod, 4, all with iOS4 and 3.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文