The sub-domain offers a nice touch of personalisation. No doubt it will be working no different from the domain name version, wildcard DNS.
Personally I like the subdomain route as long as they use a session cookie (or whatever) to store the creditials and don’t keep querying the subdomain (I’ve seen it happen).
If I were buildng a personalized site / web-app type deal *cough, I’d put the login on the root domain, and then have it jump to personalized sub.
I like the idea of sub-domains, it makes it feel more personal.
Subdomains do add the personal touch. However, I think it is still nice to have a login option on the main site as a backup for people who can’t remember their subdomain.
No. I don’t think I ever noticed this. I’ll pay more attention in the future. We don’t do that at work since I store all that foo with the man behind the curtain.
I would probably keep going to webapplication.com cause name.webapplication.com is longer to type.
I know. Bookmarks are our friends. It’s faster to start to type something and have Firefox finish the deal then to look through bookmarks.
What I dont fully understand is the “remember me for 2 weeks” trend. Why cant you remember me for as long as I want you to — forever even?
What’s up with that?
Amazon keeps me logged in for a LONG time. I agree with you there Mark, there’s not a lot of reason to log someone out unless it’s a banking application or something with a lot of security.
I think it depends on how important the username.domain.com page itself is in the experience. With Amazon and the like it makes no sense to do this. You are not using a specific page or subdomain location for the bulk of your interaction. Now look at an app like Backpack where all your interaction takes place at that location. That’s a great reason to use username.domain.com …it’s where you will live and interact with the product.
8 responses to “Web Apps and Login Pages”
The sub-domain offers a nice touch of personalisation. No doubt it will be working no different from the domain name version, wildcard DNS.
Personally I like the subdomain route as long as they use a session cookie (or whatever) to store the creditials and don’t keep querying the subdomain (I’ve seen it happen).
If I were buildng a personalized site / web-app type deal *cough, I’d put the login on the root domain, and then have it jump to personalized sub.
I like the idea of sub-domains, it makes it feel more personal.
Subdomains do add the personal touch. However, I think it is still nice to have a login option on the main site as a backup for people who can’t remember their subdomain.
No. I don’t think I ever noticed this. I’ll pay more attention in the future. We don’t do that at work since I store all that foo with the man behind the curtain.
I would probably keep going to webapplication.com cause name.webapplication.com is longer to type.
I know. Bookmarks are our friends. It’s faster to start to type something and have Firefox finish the deal then to look through bookmarks.
What I dont fully understand is the “remember me for 2 weeks” trend. Why cant you remember me for as long as I want you to — forever even?
What’s up with that?
Amazon keeps me logged in for a LONG time. I agree with you there Mark, there’s not a lot of reason to log someone out unless it’s a banking application or something with a lot of security.
I think it depends on how important the username.domain.com page itself is in the experience. With Amazon and the like it makes no sense to do this. You are not using a specific page or subdomain location for the bulk of your interaction. Now look at an app like Backpack where all your interaction takes place at that location. That’s a great reason to use username.domain.com …it’s where you will live and interact with the product.