I frequently am asked to explain the benefits and limitations of InfoPath compared to other Microsoft forms and application techologies. I have drafted a matrix to summarize my thoughts on the matter. This is a work in progress and I'm hoping will generate a lot of comment. There are also some pieces I just don't understand enough (e.g. Excel Server) so it would be great for others to fill in the gaps.
|
Technology |
Use |
Pros |
Cons |
|
InfoPath |
Rich experience and offline for true "forms" and structured documents.
Custom data gathering applications. |
Rapid iterative design, prototyping, development. Many forms require no code and can be authored by power users. Tight SharePoint integration. Rich Text data. |
Limited UI flexibility. Integrates poorly with existing web portals (separate app launches). End-user machine config inconsistencies cause support issues. Oftentimes IP is an extra install for users and not available outside the enterprise. |
|
Word |
Rich experience and offline for freeform documents. Long documents. |
Best of breed document authoring and collaboration tool. |
Structured documents possible but very hard to build even for pro devs. |
|
Excel |
Rich experience and offline for data modeling/analysis. |
Best of breed data/numbers modeling and analysis tool. Handles large quantity of data. Built-in connectivity to back-ends. Easier to customize than Word. |
Limited layout for forms. Structured data limited to tabular format. Hard to customize. Requires pro dev for advanced customization. |
|
InfoPath Server |
Reach scenarios for government and business working with citizens/customers. |
Design-once for rich/reach use. InfoPath designer tool allows non-devs to author complex forms/structured documents. |
Many limitations right now vs. InfoPath rich-client (e.g. filters). Using this to get rich and reach requires very careful design upfront and will require design limitations. Hard to integrate with existing web portals. Complex security. Licensing confusing, expensive. |
|
ASP.NET / Web Forms |
Thin experience sufficient, offline not needed. |
Total control. Easy to integrate with web portals. |
Requires web dev / pro dev. Must build all functionality / UI from scratch. |
|
Excel Server |
I don't know the design point for this product. Reach seems to be the one but not complex apps. Input welcome! |
|
|
|
WinForm, C#, Etc. |
Custom applications. |
Ultimate control. Complex UI, More rigid security, Controlled Transactions. Custom offline handling. Performance can be optimized for the scenario. |
Advanced pro-dev only. Must build all functionality and all UI from scratch. |
|
SharePoint Forms (Lists) |
Simple List Tracking |
Fast, lean, easy. |
Very limited UI, logic. No offline. |
As I get input I will update this matrix. Comment away!