Requirement details – 

1. Dashboard Screen - User will use the current location to search the service addresses by calling the REST/SOAP/XMLRPC service from website (similar to web service). User can also search choosing another location
2. Categories and Sub Categories Screen - On this screen user will select the category search the data 
3. Search Results Screen – On this screen the search results for the selected category will be displayed as LIST by default. On the same screen, user can choose MAP instead of list and all addresses will be shown on Map (either google or navtec) 
4. User can select the individual result from the list or map and get more details about the service address. There will be an additional screen to show the extra details about the service address. There are some validation rules associated with data on this screen to make decision whether to display that property or not. 
5. This application will have menu bar where user can jump from list to map or home etc. 
6. Users can send suggest new service/feature/comments by entering data into the form. 
7. The service address search will work on current location unless user changes the zip code and clicks search. 
8. REST/SOAP/XMLRPC services are out of scope. These services are ready and deployed on web address. 
9. User can post the the service details on Facebook/TWitter/Orkut or email to friend.
10. User can add the services to its favorites using web services.
11. The screen designs and other functional validations will be provided to developer upon agreement.Requirement details – 

1. Dashboard Screen - User will use the current location to search the service addresses by calling the REST/SOAP/XMLRPC service from website (similar to web service). User can also search choosing another location
2. Categories and Sub Categories Screen - On this screen user will select the category search the data 
3. Search Results Screen – On this screen the search results for the selected category will be displayed as LIST by default. On the same screen, user can choose MAP instead of list and all addresses will be shown on Map (either google or navtec) 
4. User can select the individual result from the list or map and get more details about the service address. There will be an additional screen to show the extra details about the service address. There are some validation rules associated with data on this screen to make decision whether to display that property or not. 
5. This application will have menu bar where user can jump from list to map or home etc. 
6. Users can send suggest new service/feature/comments by entering data into the form. 
7. The service address search will work on current location unless user changes the zip code and clicks search. 
8. REST/SOAP/XMLRPC services are out of scope. These services are ready and deployed on web address. 
9. User can post the the service details on Facebook/TWitter/Orkut or email to friend.
10. User can add the services to its favorites using web services.
11. The screen designs and other functional validations will be provided to developer upon agreement.