We all know how mobile unfriendly restaurant websites tend to be. Many of them are done in Flash, and don't work at all on most phones. Others force you to download PDF menus which take forever to load and have an annoying tendency to lock up my phone.
The irony, of course, is that I'm most likely to be looking at restaurant websites on my phone, when I'm around town looking for an interesting place to eat. There's nothing more frustrating than pulling up a restaurant website, only to see a Flash page that doesn't work, or a desktop website that you have to pinch, zoom, and scroll your way around.
I built ChompStack to make it easier for restaurants to create mobile friendly versions of their websites.
Any and all feedback would be greatly appreciated.
I feel like our biggest challenge with this service is getting in touch with restaurant owners and convincing them of the value of having a mobile website, most of them don't seem to be particularly interested in technology.
Why don't you have a very limited free version that lets them kick the tires without paying you anything?
Then, put the free version limit at 25 page views per month, or something small. Once it's all set up and running, and customers are visiting the mobile site, they'll "see the value" and be much more inclined to pay up :)
Instead of charging a flat setup or monthly fee, have you thought about pivoting your business model so that customers can order through your app, and you charge a percentage fee to the restaurant owner?
I think skeptical restaurant owners would choose that no-risk option, and you'd probably make more money. Restaurant owners who think it'll be successful in making sales would probably be willing to pay a decent sum per month.
I agree with the other commenter that you are probably not charging enough. I think this kind of service has high value if it can demonstrably increase sales.
> I feel like our biggest challenge with this service is getting in touch with restaurant owners and convincing them of the value of having a mobile website, most of them don't seem to be particularly interested in technology.
I could see that being the case. I don't think they understand how infuriating it is on the consumer side.
Maybe publish some success stories citing the amount of increased revenue.
Another idea would be to build your own index/app of restaurants with mobile friendly sites so there's double incentive for them to sign up.
> Unlimited promotions, events and discounts with scheduling
Maybe you have this already, but a local restaurant here has a promotion where you sign up via email/SMS and they raffle a free pizza every weekend. Since they're also a bar, this helps get people in the door and spend more money.
I built ChompStack to make it easier for restaurants to create mobile friendly versions of their websites.
This is the most important piece of information that is missing from your site. As a restraint owner looking at your site I'm thinking "What is this, an app, or a service or what?" and "how will my customers find my restaurant on their phone with this service?". Given that most restaurants that you are targeting are probably not even aware that people might access access the restaurant's site on their phone, you definitely need to answer these questions.
(edit: for example, your uWink demo video in the first frame already starts with the app (or site or whatever it is) on the screen. You should demonstrate how a customer would find uWink on their phone in the first place)
These things are annoying on a PC too. When I go to a restaurant website, I'm looking for some combination of location, hours, menu and specials. Cool visual design is a nice touch, but animations and sounds are just annoying.
Suggestion: expand your service to provide good desktop sites in addition to your mobile sites.
I am extremely interested in this, but I wonder why you're doing mobile only? Existing sites are crappy because they don't know any better and doing all the good stuff is HARD. I mean, add in basic mail merge capacities and a place to put a few ambiance ahots of the restaurant and you'd have EVERYTHING my Dad wants me to do with his restaurant's website.
I've read many 'Ask HN: Rate My Startup' posts and knew you guys gave great advice, but I didn't really expect to get this much feedback and encouragement.
Looks really well executed. I would definitely do some legwork on the operator front. I tackled this same problem about 2 years ago and found that operators simply aren't able to understand the need for this type of service (maybe it was the timing). Keep in mind that many don't have a website and some don't even use email, so explaining why they need a "mobile" website makes for a potentially hard sale.
Someone discussed online ordering as a possible revenue model, from my experiences with operators they weren't interested in this approach. Most orders they received over the phone would involve customization and the cost of handling order problems simply outweighed the benefit of not requiring their bartender to take an order over the phone. However, I could see this being big for chinese restaurants. Most customers order by number, and many chinese restaurants are carry out exclusively. Remove potential language barriers during order taking, increase total ordering, win-win.
I agree, the biggest challenge is with operator awareness. Most restaurant owner's priorities look something like this:
1) Food
2) Service
...
9544) Website
My hope is that with the mobile internet growing as it is, more restaurant folks will begin to understand that their customers are using their phones to look up restaurants, and showing them an empty Flash page or making them download huge menu PDFs is immensely frustrating and delivers a poor customer experience.
Great points, and we agree wholeheartedly. Most of our cold calls to restaurants have terminated in "We're just not interested" or "We have a website." Wish there was a way to take all of this feedback and channel it directly to them (or perhaps we need to work on our sales pitches? :) )
Like the Chinese restaurant idea. Wonder how receptive they'd be to changing their phone order system.
Strong idea and well executed so far. I know the pain point well.
Not so sure you're appealing to the right target market. It's hard to see this within the HN echo chamber but your site still comes across as very techie. It's clear how your service will help people like us, smartphone-wielding techies, but we don't run restaurants.
You should be targeting restaurant owners, executive chefs and general managers. These people are super busy and extremely tech-averse. They will shut off their brains instead of trying to understand anything even slightly technical about phones, Flash, web, etc. So get rid of that stuff. Instead show how they can get more customers by presenting their food and experience to people who are out in their neighborhood and hungry right now. And show how they can do this with near-zero hassle.
Messages like these might work: You're losing customers!
X% of people are already out and about when they decide to eat.
Y% of restaurant websites are broken on phones (use this instead of "Top 4 problems...").
Fancy phone = the income and connections to be prime customers.
Get rid of everything that doesn't clearly and directly support your main value proposition within the domain of your target market. For example the "Did you know?" section has only one relevant point ("14% of smartphone users look for restaurants...") and it hurts you because the number is small.
Test everything, including our comments. Good luck!
Thanks for the feedback. Our thought with the sidebars was to help educate restaurants about the growth of the mobile internet, and potential problems they might not know about on their own website that might be frustrating their customers.
I agree that framing the problem more in terms of 'you're losing customers' could work better.
Imagining myself as a restaurant owner, I'm confused as to how this would integrate with my existing website. Does it replace it? How do people get to the mobile version?
I suspect you have plans to move to the desktop web, too -- seems like it'd be great for restaurant owners to have a one-stop shop for all of their website needs.
Restaurant websites are definitely all over the place in terms of quality and accessibility -- seems like a solid market. Best of luck.
Interesting idea. I made an attempt to vet a similar idea in the spring of 2009, so maybe my experience can help you out:
In order to prove or disprove the concept without actually building out any kind of CMS or infrastructure, I set up a marketing site and some demo restaurant mobile sites (really good looking stuff built on jQTouch). Next step was to build prospect lists with every OpenTable restaurant in a handful of Ohio cities (I live in SF now, but was in Cincinnati at the time) and do a ton of cold calling.
After hundreds of pitches at different price points, I only managed to sell a few at $49/year and decided not to pursue any further. Having little prior sales experience (sold CUTCO as a high schooler) was a problem for me. Timing is crucial and being too early was another likely inhibitor. Figuring out the best sales channel is may be your biggest challenge. Along with how best to pitch the restaurants, who are not traditional early adopters.
I'll be keeping an eye on you guys. Best of luck!!
Thanks for your feedback! This sounds precisely like what we're encountering right now: restaurants are uncertain why people would want to see their site on a phone and how it increases their bottom line. We'd like to educate them and show them that customer discovery = ROI, but we're not sure how to evaluate that in our context. Some people here have suggested success stories, which we think is fantastic.
Great idea. Execution looks solid, feature set is solid. Now go sell, sell, sell.
My thought: your target market likely maintains both a nice printed menu and potentially a leaner "take-out" menu. The reason for the PDF menu is (I'm guessing) that's what they got back from their designer for the printer, and it's going onto good stock, getting laminated, etc.
One stumbling block might be that it's yet another place to have to maintain their menu/prices. If ChompStack could spit out a simplified take-out menu (or the daily special insert in the menu) they could print, that might reduce some of that effort. Or maybe a "patchfile" they can send off when they update their prices.
Interesting idea... my initial thought is that restaurants generally like to have nice customized menu designs. But then again, maybe not, maybe they'd rather just be able to input all of their data and get back a simple, usable design without much effort.
A friend has been talking about doing this for along time, as it is consistently felt that most restaurants do a horrible job with websites.
However, I wonder if focusing only on the mobile side of things is the right way to go.
I agree you've got yourself a market, but should a restaurant need to be updating two websites? If the same info is valid on both, why not provide a different css for non-mobile and be a one stop shop for restuarants.
You may also be able to provide some other related services which may provide a network effect and possibly a slight barrier to entry for competitors.
Great observation. That is definitely on our roadmap.
Of course most restaurants already do have websites, so getting them to add a simple redirect to a mobile version might be an easier task than asking them to dump their entire existing website.
But I definitely agree, for new restaurants that don't already have a website, being able to build a desktop + mobile version with the same tool is very compelling.
I'm working on a similar project, and one thing I'd like to point out is that menus are not always simple databases. There are several menus that have paragraphs of information that relates to several menu items rather than just one. How are you planning on translating that information to a mobile application, if at all? I'm trying to find a good example of this "paragraph of extraneous info" from menus in a Google Search - I'll get back to you when I can.
Interesting observation. Do you have any examples of this?
In my experience, most restaurant menus do fit into a simple database format. After all, most major point of sale systems do use relational databases to store and track menu items. The menu item databases are usually highly configurable but I've usually seen them break down into:
1) Major categories: Entrees, Appetizers
2) Menu items: Cheeseburger, Grilled Salmon
3) Modifier categories: Steak Temperature, Salad Dressing
4) Modifiers: Rare, Medium, Well-Done, etc.
Of course you usually don't display the modifiers on the menu itself, that is a back end implementation detail. :)
I know what you're talking about, but do you think mobile sites could possibly get away with not displaying that 'extra' information? Especially considering screen real estate on mobile devices is fairly limited.
If it is absolutely necessary, it seems like it would be fairly easy to have that show up when you select a section. That could get complicated if there are multiple paragraphs within a section (i.e. one for burgers and one for chicken sandwiches, but both of those are under "sandwiches"). You could just limit it to one description per category, though.
Nice idea, execution, and such. Congratulations and good luck!
Two things, though: if I were a restaurant owner, the burger in your logo would probably irritate me. After all, few restaurant owners see themselves in the fast food business, I assume.
Second, if you want to go international, ChompStack is probably a bad name. The "Globish dictionary" doesn't contain the words chomp and stack.
Great idea. Like everyone else, I am all for better restaurant websites and no more PDF menus.
I was slightly confused whether this was only mobile or if there was a possibility of building a full website + mobile version. It might help you convince restaurants to use this service if it can handle all of their restaurants website needs in one place.
We're very interested in expanding the product to include a desktop website version as well for a nominal monthly upgrade. The reason we didn't start out there is because we felt the mobile lure was a little stronger, due to the fact that many restaurants already have websites. Do you think the product would be more compelling if it offered both from the outset?
A problem with this service's model just occurred to me: The way that you get users onto your "new mobile" version of the restaurant is by re-directing them when they go to the restaurant's home page from a phone browser.
What if the users are like me, though, and just avoid going to the restaurant Web site from the phone because we are aware how bad the "usual" experience is.
I'm not expressing this clearly, but consider this analogy: If for ten years a neighborhood in town is "bad", has a high crime rate, routinely plays host to gang wars, et cetera, building a state-of-the-art gated community and community playground in that area won't attract new visitors for a LONG time until that old reputation runs its course.
One of your selling points is that there's "no marketing required." I don't know how you feel about this, but I think that's a losing strategy for a project like this.
I think the key word here is "required". Most of the restaurants we've spoken to are averse to the idea of having to promote a new piece of technology because of the time and effort that involves. This gives them the opportunity to make the decision about promoting it--restaurant websites deemed "bad neighborhoods" might choose otherwise :)
I'm not sure if there's any way around that, though. Part of the point of the service is that you don't give up your branding by making customers go through an external site. They go to your site, and if they're on a mobile phone, they get shown a mobile friendly version.
Love the idea. Instead of simply targeting restaurant owners, I would also suggest talking to urbanspoon, yelp and other restaurant aggregators. By offering a simple solution for their now shitty menus, you would bring a lot of value and would enable you to target a much broader market than one restaurant at a time.
All in all - really happy someone is going after this market. Restauranteurs have no idea where to look for a website. They just ask for the coolest possible website without wanting to pay too much so they end up with all the bells and whistles but done really quickly and badly.
You should wonder why restaurants think they should have a "fancy" website, as opposed to a Facebook business listing with a menu and some pics. A fancy restaurant will want something dark and elegant to communicate that they're not a diner or a fast food joint. Think about this.
Strangely enough my friend was pitching me on this idea about 6 months ago. It just goes to shows, ideas truly are a commodity, and execution is everything.
So many websites I goto have menus that are PDFs of their actual menus.
It seems like the biggest hurdle to face is getting all the information in initially(those menus can get pretty long) and then having the getting the restaurant owners keeping them updated in terms of pricing/selection. To me, $15 a month is nothing, as long as there is minimal effort in maintaining the mobile sites.
I like it, but I hate your logo. Who takes a bite out of just the bun? Also, by showing a hamburger, you made me think of fast food and I could see conventional restaurants balking at that.
At the risk of getting beat down I totally disagree. I think the logo is awesome. The branding hit me in the face hard. "Chomp"? Yep, that looks like a chomp. :) I wouldn't change a thing. It's colorful and communicates the food message quick and cleanly. Having just the logo text by itself would be too plain IMO. As for higher scale restaurants, I don't think that's a problem either. The site won't be seen by their customers, yet it's fun branding any restaurant owner can remember.
I created that logo and I hate it too. Any other ideas? I'm a horrendous graphic designer but I'm down to try again, and I agree with your points entirely. We were sort of pushing to get it done at the time. We could consider 99designs.com at this point I suppose.
[+] [-] stevenwei|15 years ago|reply
We all know how mobile unfriendly restaurant websites tend to be. Many of them are done in Flash, and don't work at all on most phones. Others force you to download PDF menus which take forever to load and have an annoying tendency to lock up my phone.
The irony, of course, is that I'm most likely to be looking at restaurant websites on my phone, when I'm around town looking for an interesting place to eat. There's nothing more frustrating than pulling up a restaurant website, only to see a Flash page that doesn't work, or a desktop website that you have to pinch, zoom, and scroll your way around.
I built ChompStack to make it easier for restaurants to create mobile friendly versions of their websites.
Any and all feedback would be greatly appreciated.
I feel like our biggest challenge with this service is getting in touch with restaurant owners and convincing them of the value of having a mobile website, most of them don't seem to be particularly interested in technology.
[+] [-] drusenko|15 years ago|reply
Then, put the free version limit at 25 page views per month, or something small. Once it's all set up and running, and customers are visiting the mobile site, they'll "see the value" and be much more inclined to pay up :)
[+] [-] jroes|15 years ago|reply
I think skeptical restaurant owners would choose that no-risk option, and you'd probably make more money. Restaurant owners who think it'll be successful in making sales would probably be willing to pay a decent sum per month.
I agree with the other commenter that you are probably not charging enough. I think this kind of service has high value if it can demonstrably increase sales.
[+] [-] jolan|15 years ago|reply
I could see that being the case. I don't think they understand how infuriating it is on the consumer side.
Maybe publish some success stories citing the amount of increased revenue.
Another idea would be to build your own index/app of restaurants with mobile friendly sites so there's double incentive for them to sign up.
> Unlimited promotions, events and discounts with scheduling
Maybe you have this already, but a local restaurant here has a promotion where you sign up via email/SMS and they raffle a free pizza every weekend. Since they're also a bar, this helps get people in the door and spend more money.
[+] [-] spuz|15 years ago|reply
This is the most important piece of information that is missing from your site. As a restraint owner looking at your site I'm thinking "What is this, an app, or a service or what?" and "how will my customers find my restaurant on their phone with this service?". Given that most restaurants that you are targeting are probably not even aware that people might access access the restaurant's site on their phone, you definitely need to answer these questions.
(edit: for example, your uWink demo video in the first frame already starts with the app (or site or whatever it is) on the screen. You should demonstrate how a customer would find uWink on their phone in the first place)
[+] [-] Zak|15 years ago|reply
Suggestion: expand your service to provide good desktop sites in addition to your mobile sites.
[+] [-] DannoHung|15 years ago|reply
[+] [-] stevenwei|15 years ago|reply
I just want to thank everyone for their feedback.
I've read many 'Ask HN: Rate My Startup' posts and knew you guys gave great advice, but I didn't really expect to get this much feedback and encouragement.
Thanks a lot guys!
[+] [-] josefresco|15 years ago|reply
[+] [-] stevenwei|15 years ago|reply
We'll put up a HTML5 video version too.
[+] [-] kaiserama|15 years ago|reply
Someone discussed online ordering as a possible revenue model, from my experiences with operators they weren't interested in this approach. Most orders they received over the phone would involve customization and the cost of handling order problems simply outweighed the benefit of not requiring their bartender to take an order over the phone. However, I could see this being big for chinese restaurants. Most customers order by number, and many chinese restaurants are carry out exclusively. Remove potential language barriers during order taking, increase total ordering, win-win.
Anyway, best of luck!
[+] [-] stevenwei|15 years ago|reply
I agree, the biggest challenge is with operator awareness. Most restaurant owner's priorities look something like this:
1) Food 2) Service ... 9544) Website
My hope is that with the mobile internet growing as it is, more restaurant folks will begin to understand that their customers are using their phones to look up restaurants, and showing them an empty Flash page or making them download huge menu PDFs is immensely frustrating and delivers a poor customer experience.
[+] [-] cmeranda|15 years ago|reply
Like the Chinese restaurant idea. Wonder how receptive they'd be to changing their phone order system.
[+] [-] barryaustin|15 years ago|reply
Not so sure you're appealing to the right target market. It's hard to see this within the HN echo chamber but your site still comes across as very techie. It's clear how your service will help people like us, smartphone-wielding techies, but we don't run restaurants.
You should be targeting restaurant owners, executive chefs and general managers. These people are super busy and extremely tech-averse. They will shut off their brains instead of trying to understand anything even slightly technical about phones, Flash, web, etc. So get rid of that stuff. Instead show how they can get more customers by presenting their food and experience to people who are out in their neighborhood and hungry right now. And show how they can do this with near-zero hassle.
Messages like these might work: You're losing customers! X% of people are already out and about when they decide to eat. Y% of restaurant websites are broken on phones (use this instead of "Top 4 problems..."). Fancy phone = the income and connections to be prime customers.
Get rid of everything that doesn't clearly and directly support your main value proposition within the domain of your target market. For example the "Did you know?" section has only one relevant point ("14% of smartphone users look for restaurants...") and it hurts you because the number is small.
Test everything, including our comments. Good luck!
[+] [-] stevenwei|15 years ago|reply
I agree that framing the problem more in terms of 'you're losing customers' could work better.
[+] [-] martian|15 years ago|reply
I suspect you have plans to move to the desktop web, too -- seems like it'd be great for restaurant owners to have a one-stop shop for all of their website needs.
Restaurant websites are definitely all over the place in terms of quality and accessibility -- seems like a solid market. Best of luck.
[+] [-] stevenwei|15 years ago|reply
[+] [-] RyOnLife|15 years ago|reply
In order to prove or disprove the concept without actually building out any kind of CMS or infrastructure, I set up a marketing site and some demo restaurant mobile sites (really good looking stuff built on jQTouch). Next step was to build prospect lists with every OpenTable restaurant in a handful of Ohio cities (I live in SF now, but was in Cincinnati at the time) and do a ton of cold calling.
After hundreds of pitches at different price points, I only managed to sell a few at $49/year and decided not to pursue any further. Having little prior sales experience (sold CUTCO as a high schooler) was a problem for me. Timing is crucial and being too early was another likely inhibitor. Figuring out the best sales channel is may be your biggest challenge. Along with how best to pitch the restaurants, who are not traditional early adopters.
I'll be keeping an eye on you guys. Best of luck!!
[+] [-] cmeranda|15 years ago|reply
[+] [-] tmitchell|15 years ago|reply
My thought: your target market likely maintains both a nice printed menu and potentially a leaner "take-out" menu. The reason for the PDF menu is (I'm guessing) that's what they got back from their designer for the printer, and it's going onto good stock, getting laminated, etc.
One stumbling block might be that it's yet another place to have to maintain their menu/prices. If ChompStack could spit out a simplified take-out menu (or the daily special insert in the menu) they could print, that might reduce some of that effort. Or maybe a "patchfile" they can send off when they update their prices.
[+] [-] stevenwei|15 years ago|reply
[+] [-] pedalpete|15 years ago|reply
A friend has been talking about doing this for along time, as it is consistently felt that most restaurants do a horrible job with websites.
However, I wonder if focusing only on the mobile side of things is the right way to go.
I agree you've got yourself a market, but should a restaurant need to be updating two websites? If the same info is valid on both, why not provide a different css for non-mobile and be a one stop shop for restuarants.
You may also be able to provide some other related services which may provide a network effect and possibly a slight barrier to entry for competitors.
[+] [-] stevenwei|15 years ago|reply
Of course most restaurants already do have websites, so getting them to add a simple redirect to a mobile version might be an easier task than asking them to dump their entire existing website.
But I definitely agree, for new restaurants that don't already have a website, being able to build a desktop + mobile version with the same tool is very compelling.
[+] [-] wanderboy|15 years ago|reply
I'm working on a similar project, and one thing I'd like to point out is that menus are not always simple databases. There are several menus that have paragraphs of information that relates to several menu items rather than just one. How are you planning on translating that information to a mobile application, if at all? I'm trying to find a good example of this "paragraph of extraneous info" from menus in a Google Search - I'll get back to you when I can.
[+] [-] stevenwei|15 years ago|reply
In my experience, most restaurant menus do fit into a simple database format. After all, most major point of sale systems do use relational databases to store and track menu items. The menu item databases are usually highly configurable but I've usually seen them break down into:
1) Major categories: Entrees, Appetizers 2) Menu items: Cheeseburger, Grilled Salmon 3) Modifier categories: Steak Temperature, Salad Dressing 4) Modifiers: Rare, Medium, Well-Done, etc.
Of course you usually don't display the modifiers on the menu itself, that is a back end implementation detail. :)
[+] [-] tnorthcutt|15 years ago|reply
If it is absolutely necessary, it seems like it would be fairly easy to have that show up when you select a section. That could get complicated if there are multiple paragraphs within a section (i.e. one for burgers and one for chicken sandwiches, but both of those are under "sandwiches"). You could just limit it to one description per category, though.
[+] [-] pwpwp|15 years ago|reply
Two things, though: if I were a restaurant owner, the burger in your logo would probably irritate me. After all, few restaurant owners see themselves in the fast food business, I assume.
Second, if you want to go international, ChompStack is probably a bad name. The "Globish dictionary" doesn't contain the words chomp and stack.
[+] [-] freshfey|15 years ago|reply
[+] [-] tim_church|15 years ago|reply
I was slightly confused whether this was only mobile or if there was a possibility of building a full website + mobile version. It might help you convince restaurants to use this service if it can handle all of their restaurants website needs in one place.
[+] [-] cmeranda|15 years ago|reply
[+] [-] wanderboy|15 years ago|reply
What if the users are like me, though, and just avoid going to the restaurant Web site from the phone because we are aware how bad the "usual" experience is.
I'm not expressing this clearly, but consider this analogy: If for ten years a neighborhood in town is "bad", has a high crime rate, routinely plays host to gang wars, et cetera, building a state-of-the-art gated community and community playground in that area won't attract new visitors for a LONG time until that old reputation runs its course.
One of your selling points is that there's "no marketing required." I don't know how you feel about this, but I think that's a losing strategy for a project like this.
[+] [-] cmeranda|15 years ago|reply
[+] [-] stevenwei|15 years ago|reply
[+] [-] DFreed|15 years ago|reply
[+] [-] wallflower|15 years ago|reply
http://news.ycombinator.com/item?id=1130419
[+] [-] stevenwei|15 years ago|reply
[+] [-] jeffepp|15 years ago|reply
Looks fantastic. I really like your UI -- very informative, yet clean.
I think that your prices seem pretty low, I am not sure how much feedback you have gotten from restaurants, this seems like a no-brainer for them...
Good luck!
[+] [-] stevenwei|15 years ago|reply
[+] [-] jokull|15 years ago|reply
You should wonder why restaurants think they should have a "fancy" website, as opposed to a Facebook business listing with a menu and some pics. A fancy restaurant will want something dark and elegant to communicate that they're not a diner or a fast food joint. Think about this.
[+] [-] empire29|15 years ago|reply
So many websites I goto have menus that are PDFs of their actual menus.
It seems like the biggest hurdle to face is getting all the information in initially(those menus can get pretty long) and then having the getting the restaurant owners keeping them updated in terms of pricing/selection. To me, $15 a month is nothing, as long as there is minimal effort in maintaining the mobile sites.
[+] [-] sethg|15 years ago|reply
Also, as a Nokia employee, I hope that your pages are compatible with our phones....
[+] [-] albemuth|15 years ago|reply
[+] [-] tansey|15 years ago|reply
[+] [-] jeromec|15 years ago|reply
[+] [-] cmeranda|15 years ago|reply
[+] [-] r00k|15 years ago|reply
In particular, the graphic of the two iPhones on the right side made it _immediately_ and _compellingly_ clear what you're selling. Nice work.
[+] [-] edash|15 years ago|reply
The simple shadow immediately beneath the phones is plenty.