|
|
Posted by kday33@gmail.com on 12/01/06 00:31
IMO, it all depends on the app. Gmail doesn't need sexy urls because
you're never going to use any of the links. Google maps doesn't
automatically give you a link, but you can generate one easily (not
very sexy though).
I think you can probably get away with non-sexy urls most of the time.
The only time I've been irritated is when I search for a product on a
website and the web page for the product has a url that is dependent on
the parameters of the previous search. Then I can't bookmark the page.
On Nov 30, 9:42 am, "f3l" <auditor...@gmail.com> wrote:
> this is all about web apps, desktop apps are another matter]
> ok, so here is my definition of an administrative app:
>
> CRUD + some logic
> all the data is private, all the access is restricted, everything lives
>
> behind the login screen.
>
> so, if I have a url like
>
> server/app/table/action/parameters
>
> I have various advantages, for instance,
>
> I can bookmark stuff, so that I can comeback later and continue to work
>
> on it (a record, or a view state* perhaps),
>
> I can also send links to my cop-workers, so they see the same
> information that I do, also,
>
> I can save all kinds of checks (are there any registers of the X table,
>
> that have Y condition available?), I can save various links, a list of
> links, that imply a proccess, etc.
>
> * table name, search criteria, sort order, page number, etc.
>
> so, in this context, do you think that users would benefit from sexy
> urls, that store a session's state, so it can b retrieved later, or do
> you think that "users won't even use it, they'll retype serach
> criteria, etc"
Navigation:
[Reply to this message]
|