wondering why I wouldn't just build this in Views. Indeed, this might look a bit masochistic if you're used to Views. However, there are a few things to consider:
EntityFieldQuery is core. If you are interested in keeping your installation as lean as possible, this is something to consider. Views is a contributed module, and so it automatically adds size and overhead to your Drupal install.
EntityFieldQuery is small. The amount of code required to generate an equivalent listing in Views, compared to what we built above, is much, much greater.
By my rough count, there are 150 contrib projects for Drupal 7 that declare new field types as part of their central module. I've listed the projects here by their usage statistics.
Taxonomy View mode allows for each Term page to use a Taxonomy view mode instead of the default hard code view.
This allows the term page display to be a list of the fields on the term (much like is done to nodes).
Multistep adds multiple-step functionality to content type editing forms. It does so by assigning a step number to each fieldgroup within the content type and hiding all the groups that do not belong to the current step. The user can then use different submitting buttons that will redirect to the previous, next, or current step.
The module also provides a block for each content type with a menu of the different groups within that form and a progress bar.
The main difference between this and the "Allowed values" or the "Maximum/Minimum" is that even if the value is outside the accepted limits, it will still pass validation. Also, Accepted Limit allows you to set custom warnings for each field.
The Adaptive image module provides device-appropriate versions of images from your fields.
You can activate adaptive images by adding an adaptive effect to any of your image styles.
The used technique is derived from http://adaptive-images.com/ by Matt Wilcox.
The hard work is done by Drupal core no need for any additional rewrites.
If image styles work on your website, this module will too.
The vCard module adds a vCard download link to every users profile. This link makes it easy to add users on your Drupal site to your local address book. Since we love microformats, there is also a theme function (theme_vcard) for displaying user data in the hCard format.
Hooks into the admin/content/node list
* Uses AHAH to show node previews and node edit forms within the existing page.
* Uses AJAX to perform searches, apply filters, and retrieve the results without reloading the entire page.
* Adds filters by author and text content (using Drupal's built-in search).
* Shows how many nodes exist within a given set of filters, and allows direct navigation to any page of results.
Timeline is a DHTML-based AJAXy widget for visualizing temporal information.
This Drupal module is an integration for a JavaScript timeline widget developed by the SIMILE project.
It works in a similar way as Google Maps but for time-based events.