On 4/12/06, Ashley M. firstname.lastname@example.org wrote:
Have any of your prototypes turned into live applications? If not,
what have you used to produce your applications and is there a reason
you didn’t go with Rails?
Two of the projects, were big offers in the public sector where we used
Rails to define the user interface. In these cases, the clients had
chosen technology and platform. So Rails was only used for prototyping
during the process where we wrote our offer.
One of these, which we won, we decided to modify the Rails prototype so
it will reflect all requirements for the user interface. The rationale
behind this: It’s faster to modify this in Rails and then port to the
platform that the client required. Furthermore, we want to make sure
share the understanding of the system with the client. This is where a
prototype is way better than a written document.
In this way, we use Rails to gain equal expectations of the system’s
capabilities. (Oh by the way, the contract obliges us still to document
work in word documents but I guess it’s the way the enterprise world
The third project has just passed a milestone where the client wanted us
give an estimate on how it could fit into their existing environment
(Microsoft technology). The client would choose between two options: 1.
Rails solution running on IIS and with MSSQL server. 2. A port of the
prototype to .NET (which is estimated to cost approximately 3 times as
much). I have no more details to share right now, but I’ll definately
more (on justaddwater.dk ) when I can share more details on this
I hope this responds to your questions.