Partager via

Why hasn't anyone heard of InfoPath?

  • Article

I recently wrote a book on InfoPath 2007. What I find most amazing about the book is that it's evangelizing InfoPath. I've shown a number of developers the book, and when they read the description, their reaction is "wow, InfoPath sounds cool - I should check it out."

How is it possible that a member of MS Office that's four years old has almost no mindshare?

I don't know the answer - I'd be interested to hear suggestions on how to get the word out to more users and developers.

Comments

  • Anonymous
    February 25, 2007
    The end-users that make forms make them in Acrobat.  The developers that make forms make them in Visual Studio.  Is InfoPath a product searching for a niche?  I've yet to see a series of strong articles on MSDN et al on why it is better than all the other ways of doing things that people are more familiar with.  It needs to overcome 'critical mass' in order for momentum to build.  I've had InfoPath installed since the first version but I'm not even sure if I've ever run it.

  • Anonymous
    February 25, 2007
    I've heard of InfoPath, but have never used it and am unlikely to ever use it. There is way too much stuff to know about in the software arena today, so if I don't NEED to know about it, I don't learn about it. Ask yourself what you know about ... pick any topic that you've heard of but don't know about. Then ask yourself how likely it is that you'll ever NEED to know about it. Cranial CPU cycles are a limited resource.

  • Anonymous
    February 25, 2007
    I've looked at infopath a few times over the years, but every single time it boils down to the simple fact that I don't need a new technology to help me get my job done, I need the technology I use and know today to do what I want. There simply isn't time to relearn the "infopath" way of doing x unless x is pivotal to my success and of course it simply hasn't been and is highly unlikely to be.

  • Anonymous
    February 25, 2007
    The comment has been removed

  • Anonymous
    February 25, 2007
    InfoPath has really only been an option if you were part of a company that installed it as part of their Office install. And most company IT departments aren't going to install anything that they don't absolutely need to because then they would have to support it. For a few forms, they would probably use ASP.NET for the forms. And by the time they got enough forms to make it worthwhile to consider using a new technology like InfoPath, they have this "installed base" of forms using another technology that would have to be converted. Now with InfoPath Forms Server there might be a chance of making more headway. However, since businesses now need to pony up the extra cash for an Enterprise SharePoint license to use the Forms server, that probably won't happen too often. If the Forms Server was free, or if there was a free InfoPath client, then there might be a chance to use it. But it will always remain a niche product until the licensing is changed - if ever.

  • Anonymous
    February 25, 2007
    Because Microsoft does not provide free InfoPath reader to work with InfoPath forms! This is so stupid! How am I supposed to publish InfoPath forms for my clients on the Internet? I am not going to buy MOSS2007 for this.

  • Anonymous
    February 25, 2007
    I agree with your sentiments, Bruce. Just 'cause it's out there made by some GIANT company DOES NOT mean we need to know things they make which we'll NEVER use.

  • Anonymous
    February 25, 2007
    The comment has been removed

  • Anonymous
    February 25, 2007
    The comment has been removed

  • Anonymous
    February 26, 2007
    The problem is that InfoPath, being a separate app from the ones people use daily, is not "discoverable."  In other words, there is no real way for an Office user to learn about the benefits of InfoPath in their day-to-day work.  Most people don't have extra time to play around with and learn "those other apps" that come with Office.  The only way to overcome this is through marketing and teaching.

  • Anonymous
    February 26, 2007
    The comment has been removed

  • Anonymous
    February 26, 2007
    InfoPath is a very cool technology but it has a fair share of problems. One of its biggest attractions for me is publishing forms online for people to use - however, I don't want to use MOSS. If Microsoft started distributing an ASP.NET control which made InfoPath forms available on ASP.NET sites, I'd consider using InfoPath anywhere I use a form today.

  • Anonymous
    February 26, 2007
    It would help alot if MS were to release a free Infopath reader or/and form filler.

  • Anonymous
    February 27, 2007
    To be a successful product, somebody should evangelize InfoPath. Typically, it is either the Developers who promote the technology or the Business Users. InfoPath is for Business Users. Unfortunately it is not easy for Business Users to learn InfoPath by themselves without the help of Devlopers, unlike  other Office products like Word and Excel. However Developers find no need to use InfoPath. So, know your target market tailor your product features to their needs.

  • Anonymous
    March 15, 2007
    Personally speaking, I had heard of infopath (2003) but was disappointed to hear that was required to host the forms that you created. That pretty much put me off it for good. I only recently learned that 2007 can generate stand alone forms in (d)html, so perhaps it's due another look.