Why WebObjects / Results / Part 1-2
Why WebObjects / Results / Part 1-2
- Subject: Why WebObjects / Results / Part 1-2
- From: Lotsa Cabo <email@hidden>
- Date: Sun, 4 Jul 2004 10:31:43 -0400
THIS WAS TOO LONG TO POST BY ITSELF. I AM REPOSTING IT IN A TWO-PART
MESSAGE. THIS IS PART ONE
_________________________
Over the last few days, I have received approximately 200 replies
regarding this subject. Many of the folks on this list replied with
great feedback, but I wanted to see what non-WO developers would have
to say. So, I posted the following question to three of the M$ and
Java groups that I work with. The question was: "Assuming you were
selecting a new development platform or technology and were to find the
PERFECT website to explain why you would this new technology, what
would the site contain?"
Below is a listing of the top requests (in the order that I started
tracking them):
#1: A "Why WebObjects" Brief
Most people want a concise explanation of what the technology is and
why it is such a great tool... nothing more than 2 or 3 printed pages.
In a perfect scenario, there would be an accompanying PDF that they
could print off and give to someone to help "sell" the other person;
something they would maybe include in a proposal.
#2: Top 10 Reasons to Choose WebObjects
Somewhat inline with #1, this would provide a quick glance at the
information above. I included it here because it was mentioned ALMOST
as much as #1.
#3: Core Features
A look at the core features of the product... similar to what Apple has
on their site but without any of the marketing fluff.
#4: Comparisons to Alternative Technologies (both Open-Source and
Commercial)
Many people have mentioned the desire to relate the product to
something else that they may have heard of. Others said that it would
benefit their decision to see that there are other technologies doing
the same thing; even if it meant more technologies to accomplish the
same task. Several people also said that it would add credibility if a
site were confident enough in the product to compare itself to other
products that were of equal merit without pulling any punches
(obviously the company that created the product -- Apple, in this case
-- would never do this, but people see this site as
developer-to-developer communication).
#5: Database & Product Compatibility
Again, without any marketing fluff, many people have asked for a
developer-backed list of technologies that the product has successfully
worked with (databases, etc.)... not what it theoretically could work
with.
#6: Success Stories / Use Case Scenarios
There is power in numbers. Almost everyone asked for a listing of
other sites or companies using the technologies (preferably, sites that
are public) and how the new technology is being used. Many wanted to
see examples from major industries (like healthcare).
#7: A short "getting started" guide
Two people mentioned the idea of having a few streaming videos to demo
the technology being used. Others simply wanted a very quick guide to
show how it would be used. The one "gotcha" here is that many stressed
that the guide should be built in such a way that people can appreciate
the technology without having it in hand since, at this stage, they are
deciding if they are going to consider the technology or not.
#8: Direct "Question & Answer" area (not a forum)
(This was surprising to me however, after reading the replies, I can
understand where they are coming from.) Several people replied that
they would like an area that is maintained by senior developers to
directly answer questions about the technologies; in short, they could
post a question and get a direct answer as to whether or not the
technology could do something or how it worked. What they did not
want, however, was a forum. Most stressed that they did not want to
dig through endless commentary on a topic, but instead wanted direct
answers to their questions. Many continued that they would not mind
seeing other replies/opinions to the answer, but they should appear
AFTER the reply from a trusted individual and that the area should be
moderated to remove any possibility for online debates and arguments...
again, these people would be coming here to get answers to their
questions and not to go through a forum. The basic argument was that
there are several forums out there and that, if they wanted a forum,
they would go there.
#9: Developer Directory
A listing of developers who are using the technology and a way of
contacting them. The reasoning here is that they may like the
technology, and want to bring it in house, but may not want to train
their people on it. It would be nice to be able to see a listing of
qualified individuals that they may be able to choose from. A handful
of people mentioned having a certification exam that the listed
developers could optionally take to show they actually know their stuff
and that the test would give them some type of indicator next to their
name.
(TO BE CONTINUED ON PART TWO)
_________________________
Tired of spam? Signup for a FREE SpamJammer.Com account and say
goodbye to junk email forever!
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.