Make it Official: HTC Diamond Coming to Sprint

This is a device I have been waiting for since I heard about it many months ago, and if you weren't already convinced that it was coming to Sprint, there is more information now that all but locks it up. The touch diamond is a direct competitor to the IPhone that runs on Windows Mobile and utilizes a beautiful Touchflo 3D interface.

Rumors have been swarming for months about when it would come to the U.S., and under what carriers, and as if there wasn't already enough evidence about the device making its way to Sprint, here are some more pieces that make it really, more then official.

The following Web sites and domains have been found by various Sprint users and diamond enthusiasts pointing to the future of this device on Sprint's official Web site.

So now it's just a matter of how long Sprint will wait to launch the long awaited device. Most plausible dates seem to be that most stores will get delivery of the device on or around the 16th of August and will then begin training their employees on it for a release on September 2nd.

Price is another sticky point as no one really knows how much Sprint will offer up the device for, however it's believed that it will be under the $300 with a 2 year contract agreement to compete more directly with Apple's IPhone.

Posted on 8/11/2008 9:24:00 AM by Kyle P. Johnson

Permalink | Comments (0) | Post RSSRSS comment feed |

Categories: Mobile

Failed to enable constraints

While working with a Web application this evening I ran into this error: "Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints". 

As I  researched the origin of the error I found a lot of people having the same issue, and no real great solutions, however there was a lot of people pointing to the database properties itself, some thought it was the enable constraints set on the dataset in the code-behind.

After researching further I was pointed towards by Datasets in my .xsd file.  This file contains the duplicate copies of the field length values that were set when you created the table adapter.  I had changed a few of those values in the database after creating the table adapters in my project. 

You can reset these values by selecting your the column in your tableadapter and open it's properties where you can set the max length.

Posted on 8/10/2008 12:07:00 AM by Kyle P. Johnson

Permalink | Comments (0) | Post RSSRSS comment feed |

Categories: ASP.net

Frequently Asked Questions (FAQ) Pages

FAQs (Frequently Asked Questions) should not be a standard.  I have said it before and I will say it again.  FAQ pages are overused and outdated in an age where Web pages become increasingly easy to use and find information.

A recent client project that I am working on brought this issue back to my mind and after thinking it over in more detail I am writing a about it again just to better organize my thoughts and add some bits here and there that I have learned since my last writing in Jan '07 that further solidify my position.

Misnomer

Lets start with the fact that nine times out of ten, a FAQs are not even that.  They a list of generated questions that the company or organization perceives to be common questions that are put out there before the site has presented itself to generate questions.  When a client comes to you for a brand new Web site, one of the things that most people know and want is a FAQs page.  What FAQs does that client really have at this point?

Investing in Content

The FAQs page is often a dumping ground for pieces of content that don't seem to logically fit anywhere else, or perhaps are added later after the site it full built and deployed.  In both these cases the content was not well thought out or organized.  Nine times out of ten the content fits better into a content area rather then FAQs.

Step through the logical progression of a user for a moment.  The user is looking for something, something specific.  They surf through the content sections they thought it might be relevant in with no luck, then perhaps turn to search, then maybe the FAQs, or maybe even the sitemap.  By now you have forced the user to do a lot of looking when if you developed the content well up front they would have found what they were looking for on step one.

So why not invest in that content in the first place and find ways to integrate and fix the issues of customers having trouble finding that particular content. Create links to more developed content pages that talks about the subject in more detail then a paragraph.  Make the content (if it already exists) pop out a little more using heading tags.  You could even add that same FAQ to the sidebar of a content page that is related.

faq_inline

The point here is with a little more work and thought there are better places to put these bits that the customer will find in the first place rather then having to hunt  in the FAQs page.

SEO Considerations

When you look at FAQ pages from an SEO standpoint they really provide little or no value.  Small amounts of undeveloped text from all sorts of different topics with no content to back it up all on one page.

If these are "really" your most frequently asked questions why not (as I talked about in the above section) invest in some content to answer these questions clearly to better help your customers?  Dedicating content to these questions should  improve their search rankings and make them easier to find via search weather that be your internal site search or external like Yahoo, Google, or alike.

Not All FAQ Pages are Bad

So as with almost everything there are exceptions to the rule, and in fact there are some sites that do FAQs very well.  Linking the questions to highly developed content sections instead of using the FAQs page as the only source of that data.

Posted on 7/4/2008 7:55:09 AM by Kyle P. Johnson

Permalink | Comments (0) | Post RSSRSS comment feed |

Categories: Rant | SEO | Web General

Blog Flux Directory Blog Catalog