SAAS 的网页设计与传统网站有何不同？
寻找有关多租户应用程序的 UI 设计有何不同的指南。 非常感谢白皮书和博客条目的指针。
Looking for guidance on how UI design differs for multitenant applications. Pointers to whitepapers and blog entries greatly appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不明白为什么（图形）设计应该有所不同。 最终用户不应该能够确定谁在托管该应用程序。
当然，软件设计必须注意区分不同的实例/客户端，并确保客户端的各种需求不会以负面方式相互影响。
还应考虑维护。 如果您的应用程序仅由一个客户端使用，通常可以商定一些停机时间以进行更新、重新配置等。 对于许多客户来说，情况会变得不同。 因此，您可能应该计划让您的应用程序重新读取配置而不重新启动。 您还应该计划一种无需停机即可升级应用程序的方法。
I can't see why the (graphical) design should be any different. end user shouldn't be able to determine who is hosting the application.
The software design of course has to take care to separate the different instances/clients and to ensure various demands of clients don't affect each other in a negative way.
Also maintenance should be considered. If your app is only used by one client, it is often possible to agree on some downtime for updates, reconfiguration and the like. With many clients this will become different. So you should probably plan for your application to reread configuration without restart. You also should plan for a way to upgrade your application without downtime.
取决于您真正提供的服务类型，不是吗？
如果您允许您的应用程序被各种客户端（例如 Outlook Webmail）设置皮肤，那么您需要适当考虑这种情况。
但实际上，SAAS 在这里毫无意义。 您只需设计您的……设计，因为它应该是，并且需要是。 简单的。
Depends on what type of service you're offering really, doesn't it.
If you're allowing your app to be skinned by various clients (say, like Outlook Webmail) then you need to consider the situation appropriately.
But really, SAAS means nothing here. You just design your ... design, as it should be, and as it needs to be. Simple.