What is taking time is settling for the right level of complexity and the theme selection. Being too complex can discourage people just starting with word games. Too high will make it boring for hardcore word gamers. Coming out with a globally acceptable theme is not easy either. I suppose you are also facing similar challenges.
Idea looks good and useful.
Give some quick links in the first page. Is it possible to suggest ingredients based on the already selected? Give mouse over titles to the images that are being displayed on the right.
Totally agree. Once I found the gallery I pretty much immediately "got it" but up to that point I was having a hard time figuring out what it the product actually was.
Sponsored tweets are a good idea. But results are best when companies get to target the audience based on their interest. For example, a company would more likely to spend to show ads on specific search term than all the search term. So if you can find a way to categorize the people visiting your site based on retweets or fav patterns and have separate categories of favs then you can have targeted sponsored tweets.
I agree and I face this problem. Generally I circumvent this by firebugs capabilities to edit the HTML dynamically, but it has to be done too frequently end up uninstalling IE8. and installing it again at a later point. IT department thinks that IE7 does not make the security cut .. I dont know the specifics of security cut.
I feel this should be a browser feature rather than having a website. One has to search for the book mark and then provide email id, enter the captcha. Instead of these whenever there is HTTP 404, browser itself can give a icon in the address bar to keep polling the website. Firefox plugin may be?
General problem is not getting the clients to change but get all the clients to change at same time. Or else you will end up hosting multiple versions of webservice. In enterprise setup its really hard as each organization can have different processes to be followed and value proposition for switching to new version of webservice may not be same for each client.
Hash algorithms are prone to collision depending on data/content you are storing. If the data is similar then it can lead to collision in hash keys, which can deny O(1) retrieval. Retrieval depends on content stored and O(1) can not be guaranteed every time. One of the reasons for going for binary tree based traversal is guaranteed O(log n) irrespective of the kind of data that is stored.