This screen represents the "View Property" screen of the "Estate Agent" module.

From the two attachment (one GIF and the other visio), you can see what the "View Property" screen of the "Estate Agent" module will look like.

Any comments are much appreciated, there will be other designs posted. This is your chance to participate in the development of a new Ventrian module.

Yes, but if you click on any, a slideshow will appear in a popup that would allow you to view all images.

Does this make sense?

Focusing the module on Real Estate is fine. 

What do you think about the tabbed idea of the module interface?  I e-mailed the visio file to a number of friends in the real estate business and interface design.  Here are their comments:

• Pictures are a great idea and the movie panel is brilliant.  It captures the energy of the property and entices the visitor to look at more details. 
  

   

• Agent information and contact information should not be "in their face."  You want the visitor to be taken in by the property and not feel like it is all about the sale.
  

   

• Basic summery information is okay, but more details need be provided without confusing or overwhelming the potential buyer.
  
• You have to include the ability to provide a map or driving directions.  Suggestions included passing data to services like mapquest or google.  (my thought when this was suggested to me was to consider pulling data from the DNN membership module and use that as a starting point for driving directions.  For those that will not be driving form their membership listed location they can enter the starting address). 
  
• Use icons to represent common fields but give the user the ability to switch to text for limited sighted users and browser compatibility.  Icons could be associated to certain home features (ranch could be a certain icon, duplex another, garage could be a car, etc…) people want to see pictures and icons. 
  
• RSS must be available so the data could be pushed to users.
  
• Consider being able to upload files that associate with the property.  This could include brochures, tax papers, foreclosure work, mortgage spreadsheets, maps, school information, etc…
  
• The publisher of the data should be able to tie the real-estate listing with other possible services, like Zillow, Google Earth, Gov Crime, and or Job Census data.
  
• You have to be able to describe the image if they click on it.  For example showing a picture of a hard wood floor may need further explanation as to the type of wood, age, workmanship.  The images should be clickable and provide more information if the listing agent wanted to do so.
  
• Can a user subscribe to the type of home they are looking for so that in the future if a home that matches their description is found it could e-mail them?  I was e-mailed this comment and am not sure what features are considered for the buyer.  Thought it would be interesting to include.
  
• Can the user group the listings or search by different categories.  For eample, location, size, type, cost, bedrooms, etc...and more than one particular feature?  I think what they were trying to say was, when searching on property can they look for homes in the Orange County area with 4 bedrooms and fireplace.   I am not sure what sort of ad-hoc search interface is being considered.

   

As I collect their ideas I will post them.  Understandably less than 10% of the ideas will merit possibility or consideration.  My philosophy is that the idea (like a brainstorming session) may trigger other ideas.