Skip to main content

A Killer Smartphone App

One of the big problems I have using Consumer Reports is that the listings, even if available online, require some pretty significant planning and research before using them.  Specifically, vendors often don't have the exact models that are reviewed, so you have to interpolate other reviews on similar models from that manufacturer.  Also, vendors often have varying stock, so the research you've already done may become obsolete quickly.  Finally, most of the reviews on CR are best used in large-format displays.

What I would love to have is a smartphone app where you could enter a make and model of an appliance (or better yet scan something using the camera) right in the store and get quick, easy-to-read summary of the ratings for that product or similar ones, along with recommended prices.  It would make shopping in a store a much more informed process.

I would think something like this could make someone a lot of money.

Comments

Post a Comment

Popular posts from this blog

Java command line app with Spring and Gradle

Many Java developers have had to build a command line app for one reason or another over the years, and there are many(!) ways to do it.  There are a bevy of command line libraries, some people roll their own when they get to this point (which is one reason why there are so many command line libraries!), and others just pull in the arguments simply and directly, eschewing a library. However, writing a tool, a developer should just focus on the meat of the problem rather than having to worry about the enabling functionality that allows it to work.  The Spring Framework very much supports this approach to development with its inversion of control (IoC) container and a myriad of other features. To support that approach for command line applications, the spring-cmdline library provides a bridge between the Spring framework and the JOpt Simple command line library. This tutorial will show how to leverage the spring-cmdline library to stand up a very simple command line ap...
Post a Comment
Read more

manifest classpath + taglib jars + Tomcat = FAIL

I found an interesting side-effect of using manifest classpaths in our application jar files as it applies to taglib jar dependencies and embedded Tomcat 6. ·          Manifest classpaths do not appear to be expanded in the URLClassLoaders that load the jars with the manifests, so only the jar file referenced directly on the classpath are included in its URLs. The taglib search mechanism in Tomcat 6 (haven't checked Tomcat 7 to see if there's a difference) only walks the classpath looking for URLClassLoaders, looking at the underlying JAR URLs. Thus, if the taglib jar is referenced only as a dependency in the manifest of the main jar file and is not specifically on the classpath, it will not be spotted and use of that taglib by the JSP engine will throw an exception. This problem won’t actually show up in tests as IDE environments and builds generally include all the jar files in the classpath, so this one will bite you at runtime. ...
Post a Comment
Read more