Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Need GUI Advice

Status
Not open for further replies.

jfrost10

Programmer
Jun 3, 2001
2,004
CA
Hey guys,

I need your advice and input. We're re-creating an Access application on the web. What we don't want is for it to LOOK exactly like Access (we want to jazz it up a bit). Unfortunately, there's not alot of resources out there on the basics of creating "Web Applications" that are ACTUAL applications (i.e. something someone is going to key info into all day). Also, most of the "graphical" resources on the web are assuming that we want this to have rich color and fonts, etc. Which we really don't: we want this to act like a windows app, not LOOK like a windows app, but also not look like some marketing-style web page.

Yes, our requirement is one big contradiction.

I'm just curious how you guys did your page layouts for your applications, and if you came accross any really good resources for theory, examples, etc.

Thanks,

D'Arcy
 
Your recreating an existing process. Start with that. Get any small complaits the users have about the application( this doesnt give me what i need, i think it would be more useful here, etc )Take the current layout and make it exactly the same in the web app except for the changes mentioned. If there are alot of changes to be done, you may want to recreate it exactly then make the changes so you can ensure that they are all completed. You now have a working product. Make sure you get the bugs out cause users really do not like them. Nothing is as important in projects as getting the users to like and use the product.

Now that you have working application you can work on making it look nicer. be very carful on moving things around. if you do want to move something, check with the users. as you said, they will be entering things all day and have been doing so in the current access application. they likely have a well defined process and have meorized the field order. messing that up will seriously erk the users. Allways remember the end users. IF they do not like it, they will want to keep using the current access application.

If the users have serious issues with the current application, you may want to start redesigning before you start programmming it as a web app. with asp.net it is very easy to move things around for prototyping so its not to big an issue.

Most important thing to remember is that the users are used to something already, the access application. do not change it unless they want it changed. Only the medium is changing.(Access to Web) If you have any specific questions, ask away.
 
Thanks for that Corran.

I actually agree with all you said, although time constraints and the fact that Access and ASP.NET do work differently don't allow us all the flexibility of duplicating entirely.

What I'm really looking for though is examples of web application interfaces, and how people created their own: not just the typical "shopping cart" model, but a more rich user interface accessed over the web.

I'm looking more for visual ideas, theory resources, experiences, etc. I've got all the methodology of the software design part of it already though.

Still, thanks for your reply.
:)

D'Arcy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top