I decided to keep the design simple and mobile-friendly, favoring speed over too much bling. It does one thing: tells you if you should take WA-520 or I-90. That's all.
Fun weekend project. Took me about three hours total, using BeautifulSoup and Django (although Django is probably actually overkill here, since there's no database, no auth/auth, and only one view).
Well, I wouldn't use anything but Django, because that's what I'm comfortable with. :) But, there are some "microframeworks" for Python that might actually be more appropriate. Something like itty, perhaps: http://github.com/toastdriven/itty/
I'm not sure what would make PHP any "safer" than Rails or Django or any other framework. As for easier? Maybe, if you know and like PHP. I loathe PHP and am not very proficient with it, but am quite comfortable with Python. My feeling is: use the language you like and know best. That's always going to be the path of least resistance, and the performance/security implications when choosing between Ruby, Python, and PHP are pretty negligible.
Nice work, Crofty. Simple, clean, and to the point. Digging the "no fluff" approach to this little project. And I can't believe you actually got whichbridge.com on top of it.
Jeff, sorry, I didn't mean "safer" as in security, but more as in "I know I am not going to run into any deployment issues" safer. But, I guess what you know the best is what you will have the least issue with. I need to give Django a go... my buddy Wess will be happy if I do :)
Makes sense, Doug! Django deployment is super-easy and reliable for me, because I have a dedicated could server that's all configured for it and I've deployed several sites on it over the past year. It's been ages since I've deployed a PHP site. I'm sure I could still make it work, but I don't currently have a server with PHP installed, and there's just something comforting about what you're...well, comfortable with. :)
Jeff, Id submit that it might be important to show the alternate bridge's time in the page as well. For instance let's say you're in Kirkland and want to get over to Seattle. You go to that site and it tells you that 90 is faster, but what it doesn't tell you is tbat maybe 90 is only faster by 10 minutes in which case it would be faster to take 520.
I know this would primarily be used in times when the difference is more than 10 minutes, but I'm just using one of many examples where I could see having all the information at hand would be advantageous.
Oh and also, why not use GPS information if It's available to default to whichever tab the user most likely needs at that time.
Sorry to shit all over your preview with annoying feature requests, but just thought I would feedback :)
I like it, but maybe it's too simple? It doesn't say "what it is, what it does, for who and where" Those were things I was asking as I was clicking. :-)
UPDATE: just saw you posted this above: It does one thing: tells you if you should take WA-520 or I-90. That's all.
So, the user needs to know to go to dribbble.com and read that. Why not just put that in a sentence on the site?
I see your point, but I think the URL pretty much does that -- for Seattleites. If you're not from here, you won't understand, but it's also not for you. A little background:
There are two floating bridges over Lake Washington, which divides the city of Seattle from it's Eastside suburbs, which include Bellevue, Kirkland, and Redmond. The bridges are the primary traffic issue in the Seattle area, as they as the main thoroughfares for those that work at several of Seattle's biggest companies (Microsoft, Nintendo, T-Mobile, Amazon, Starbucks). Colloquially, Seattleites refer to them as "the bridges," and everyone here knows what you're talking about if you were to say, "It's on the other side of the bridges," or "Which bridge should we take?"
So, while it probably lacks context for people who don't know this area, so far, it seems like Seattliles pretty much "get it" instantly.
BTW, I heard from the Washington State Department of Transportation today. They said: "Very cool app! [...] We get so inundated with information here that we often forget about the brilliance of simplicity."
Well, then that clears it up. I was thinking because I didn't get it, you must've built it only for yourself, but then why make it pretty if that's the case? :-)
By the way, this simple little app gave me some inspiration to build a little app of my own that I've been thinking about for a year now. I'll post a rebound once I have something worth showing...
18 Responses
I decided to keep the design simple and mobile-friendly, favoring speed over too much bling. It does one thing: tells you if you should take WA-520 or I-90. That's all.
Fun weekend project. Took me about three hours total, using BeautifulSoup and Django (although Django is probably actually overkill here, since there's no database, no auth/auth, and only one view).
about 2 years ago
What would you use for something like this if not Django?
about 2 years ago
Well, I wouldn't use anything but Django, because that's what I'm comfortable with. :) But, there are some "microframeworks" for Python that might actually be more appropriate. Something like itty, perhaps: http://github.com/toastdriven/itty/
about 2 years ago
Ok, I love frameworks (particularly Rails), but wouldn't PHP be the safest/easiest choice?
On the design note, the app looks awesome. Its perfect for what you are doing... very cool!
about 2 years ago
Hey Doug-
I'm not sure what would make PHP any "safer" than Rails or Django or any other framework. As for easier? Maybe, if you know and like PHP. I loathe PHP and am not very proficient with it, but am quite comfortable with Python. My feeling is: use the language you like and know best. That's always going to be the path of least resistance, and the performance/security implications when choosing between Ruby, Python, and PHP are pretty negligible.
Thanks for the kind words!
about 2 years ago
Pro
Patrick Haney
Nice work, Crofty. Simple, clean, and to the point. Digging the "no fluff" approach to this little project. And I can't believe you actually got whichbridge.com on top of it.
about 2 years ago
Thanks, Haney! Yeah, I was pretty shocked "whichbridge.com" was still available, too.
about 2 years ago
Jeff, sorry, I didn't mean "safer" as in security, but more as in "I know I am not going to run into any deployment issues" safer. But, I guess what you know the best is what you will have the least issue with. I need to give Django a go... my buddy Wess will be happy if I do :)
about 2 years ago
Makes sense, Doug! Django deployment is super-easy and reliable for me, because I have a dedicated could server that's all configured for it and I've deployed several sites on it over the past year. It's been ages since I've deployed a PHP site. I'm sure I could still make it work, but I don't currently have a server with PHP installed, and there's just something comforting about what you're...well, comfortable with. :)
about 2 years ago
Pro
Ryan Rumsey
Can you build one for Austin too? :)
about 2 years ago
Pro
Josh Bryant
Jeff, Id submit that it might be important to show the alternate bridge's time in the page as well. For instance let's say you're in Kirkland and want to get over to Seattle. You go to that site and it tells you that 90 is faster, but what it doesn't tell you is tbat maybe 90 is only faster by 10 minutes in which case it would be faster to take 520.
I know this would primarily be used in times when the difference is more than 10 minutes, but I'm just using one of many examples where I could see having all the information at hand would be advantageous.
Oh and also, why not use GPS information if It's available to default to whichever tab the user most likely needs at that time.
Sorry to shit all over your preview with annoying feature requests, but just thought I would feedback :)
about 2 years ago
Great suggestions, Josh! Thanks!
about 2 years ago
Pro
Alan Houser
I like it, but maybe it's too simple? It doesn't say "what it is, what it does, for who and where" Those were things I was asking as I was clicking. :-)
UPDATE: just saw you posted this above: It does one thing: tells you if you should take WA-520 or I-90. That's all.
So, the user needs to know to go to dribbble.com and read that. Why not just put that in a sentence on the site?
about 2 years ago
Alan-
I see your point, but I think the URL pretty much does that -- for Seattleites. If you're not from here, you won't understand, but it's also not for you. A little background:
There are two floating bridges over Lake Washington, which divides the city of Seattle from it's Eastside suburbs, which include Bellevue, Kirkland, and Redmond. The bridges are the primary traffic issue in the Seattle area, as they as the main thoroughfares for those that work at several of Seattle's biggest companies (Microsoft, Nintendo, T-Mobile, Amazon, Starbucks). Colloquially, Seattleites refer to them as "the bridges," and everyone here knows what you're talking about if you were to say, "It's on the other side of the bridges," or "Which bridge should we take?"
So, while it probably lacks context for people who don't know this area, so far, it seems like Seattliles pretty much "get it" instantly.
BTW, I heard from the Washington State Department of Transportation today. They said: "Very cool app! [...] We get so inundated with information here that we often forget about the brilliance of simplicity."
Thought that was pretty cool. :)
about 2 years ago
Pro
Alan Houser
Well, then that clears it up. I was thinking because I didn't get it, you must've built it only for yourself, but then why make it pretty if that's the case? :-)
about 2 years ago
Ah, Seattle and gnarly traffic: they go together like peas and carrots. Didn't they try to solve the traffic problem in "Singles" like 18 years ago?
Awesome concept, Jeff. I love mini-apps like this.
about 2 years ago
Pro
Patrick Haney
By the way, this simple little app gave me some inspiration to build a little app of my own that I've been thinking about for a year now. I'll post a rebound once I have something worth showing...
about 2 years ago
Sweet!
about 2 years ago