iPhone 应用程序后端义务时间表
我正在开发一个 iPhone 应用程序，该应用程序将使用 Google App Engine 后端，并计划在 App Store 上以 1 美元的价格出售我的应用程序。
我认为我的 Google App Engine 成本存在超过应用程序收入的风险，因此不可能让应用程序后端长期运行。
问题是 - 我有义务运行后端多长时间？后端不可能永远运行，那么我必须让它可用多长时间？
I'm developing a iPhone application that will use a Google App Engine backend and planning to sell my application for $1 on the App Store.
I feel there is a risk that my Google App Engine cost exceeds my revenue from the application and therefore it is not possible to keep the app backend going in long term.
The question is - For how long am I obligated to run the backend? It is not possible to run the backend forever, so how long do I have to have it available?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您应该查看像 StackMob 这样的公司，它可以帮助您为您的移动应用程序构建完整的后端。它们为您提供您需要的后端核心服务（安全的 REST API、自定义代码、推送通知、Facebook 和 Twitter 登录等）。 StackMob 还通过清晰的开发和部署环境以及简单且有组织的版本控制在部署方面提供帮助。他们帮助解决技术问题（处理数据/流量的增长/峰值）和问题。应用程序的业务（来自服务器和客户端的分析）扩展。
You should check out a company like StackMob that helps you build a complete backend to your mobile app. They provide you with core services you'll want from your backend (secured REST API, Custom Code, Push Notifications, Facebook & Twitter log in and more). StackMob also helps on the deploy side with clear development and deployment environments along with easy and organized versioning. And they help with the technical (handle growth/spikes in data/traffic) & business (analytics from the server & client side) scaling of your app.
除了预付许可费用之外，您还有其他选择。考虑使用订阅，这样只要人们真正想要使用该服务，您就可以继续获得收入。
You have options other than just an upfront licence cost. Consider using subscriptions so that you'd continue to receive an income for as long as people actually want to use the service.
这是围绕软件即服务的普遍关注。没有正确答案。只要尽力预测成本并以可持续的方式定价您的产品即可。然后尽力保持开放状态，如果情况发生变化，向用户发送消息。
This is a universal concern surrounding software as a service. There is no correct answer. Just do your best to project costs and price your offering sustainably. Then do your best to keep it open, messaging users if the situation changes.