Android version of our Gilla Bilen Iphone app

This app will allow Android mobile phone users to 1. Find the nearest car dealer or car service facility, and filter by car make and model, tap to read details about that company, and tap to see its place on a map and get driving directions from Google Maps. 2. Read news updated hourly. 3. Read hints and tips about car-owning. The basic structure is the 3 main views above, with detail views containing plain text, a map view and a few views for making settings. The app is in Swedish, with only a few localized strings we will supply and the rest of the Swedish text supplied in Apple Plist XML files, or data in same format as HTTPResponse based on lat and long parameters passed to an ASP url. Android OS differs from iOS, so your job is to deliver this app as a compilable-in-Eclipse project (for OS 2.2+) that can be directly compiled and submitted to Android Market, which has the same design and UI usability as the iOS app for screensize varying between 320x480 up to about 640x960, while adapting it to the UI interface of Android apps that Android users find intuitive. You will find a thorough design spec, with full data disclosure, and Photoshop files and screenshots in the Detailed Specification. ## Deliverables **The app "Gilla Bilen" design specifications** **Summary:** This app will allow Android mobile phone users to 1. Find the nearest car dealer or car service facility, and filter by car make and model, tap to read details about that company, and tap to see its place on a map and get driving directions from Google Maps. 2. Read news updated hourly. 3. Read hints and tips about car-owning. All data is online XML files, except a list of Swedish cities and their GPS coordinates, which is offline (included in the app), and the filtered out list of car dealers which is retrieved from an ASP script. All text is in UTF-8, and this app is intended only for Sweden. In the final app, all text in the app must be in Swedish. **Indata:** For graphical and other file resources, see the attached .zip file. **All** .xml and .plist files are one(1) array of dictionarys in a standard Apple Plist 1.0 XML wrapper. Characters <, >, and & are HTML-escaped in these files and must be converted back. There is only **1** fixed url: [login to view URL] Your app cannot have any other fixed urls in it, or links may become broken in the future. First entry is **xmldir**, which is the base folder of the online XML files: [login to view URL] (for the car model selector list) [login to view URL] (Tips & Hints categories) [login to view URL] (News articles) [login to view URL] (Tips & Hints articles) Second and last entry is **aspurl**, which is the URL for the HTTPGet for the XML HTTPResponse giving a list of the nearest dealers. To this, you must append the following parameters, in this order: lat - latitude from the phone's position or a selected town in the town list lng - longitude for same. rld - 0 for 20 results, 1 for 40 results, 2 for 60 results, and so on. m - Selected car model, or empty string if "Alla" (all models) is chosen. Only m can be empty string, and you must specify all 4 parameters in the call. This Objective-C code is provided as example: NSString *str=[NSString stringWithFormat:**@"%@?lat=%f&lng=%f&rld=%d&m=%@"**,aspurl,homelat,homelon,n,filter]; **Caching:** You may cache anything you like for performance, but if the XML data is older than 30 minutes, you must make sure it's re-downloaded. It's checked whenever you switch to the view showing the data (this includes the app coming back from being in the background). The XML files are individual and caching time can be checked individually in the view that relies on the data. Avoid reloading all files every time one file needs to be refreshed, except on app startup of course. The GPS position must be refreshed and the new position verified and supplied to the HTTPGet url, before fetching data for the dealer list! The GPS position should update in real time only in the map view, to save battery. **General design:** You should follow the UI design as closely as possible, but where it conflicts with normal Android app use you can suggest a better solution. We want an app that is completely intuitive to an Android phone user. It should however be clear to a novice user that has used a few similar apps before, how he should navigate the app, at all times. Opening URLs, routes, calling a number, or e-mailing must bring up a modal Yes/No dialog with the text "Detta g?r att du l?mnar appen tillf?lligt. ?r du s?ker?" (Yes and No in Swedish is Ja and Nej.) "Back buttons" should have the titles of their parent view, but if the title is not fixed, it should read "Tillbaka". For example, the Back button in the city list should read Hitta ?F, while the Back button in the map view should read Tillbaka, as the Details view title could vary. All lists should normally be presented sorted as they are in the files. If a list deviates from the screenshots, however, then sort it like the screenshot. All text boxes in detail views are plain text. The app should adapt to different screen sizes within reason - if it's a modern smartphone (Android OS 2.2 or higher) and the resolution is 320(w) by 480(h) or higher, it should be supported. It should be clear that the other two views (Nyheter, Tips & R?d) are present, so that they don't think the first view, the dealer list, is the only one. **Functionality:** If you want, you can familiarize with the Iphone version on App Store after reading the below, to make sure you get how navigating the UI is intended. When the app starts, the picture with the yellow car is displayed full-screen, with only a small loading indicator in the center. Not until the dealer list is fully ready behind it, does it fade away in 1.2 seconds, never to be shown again unless you force quit the app and start it again. **1. Hitta ?F** (dealer list) The dealer list uses Helvetica and Helvetica-bold, and the distances are shown in Trebuchet MS. Distances are shown in kilometers as they come in the XML data, but if the distance is < 1 km you must multiply by 1000, round and display f.ex. "950 m". Compare data in the current XML files with the screenshots for how the subtitle data should be presented in each cell. Tapping a table cell displays the Details page. You must look at the data and our Details screenshot to see how the data is presented. Tapping Back goes back to the dealer list, and tapping Karta (map) goes to a standard Google Maps map with a placemark. Tapping V?gbeskrivning in this view opens the placemark externally in the default browser. We use this Obj-C code: [mapsurl appendString:**@"[login to view URL]"**]; [mapsurl appendFormat:**@"%f,"**,mylat]; //phone position or selected city [mapsurl appendFormat:**@"%f"**,mylon]; [mapsurl appendString:**@"&daddr="**]; [mapsurl appendFormat:**@"%f,"**,[login to view URL]]; [mapsurl appendFormat:**@"%f"**,[login to view URL]]; Back in the dealer list view, there are 2 buttons to 2 more views: Bilm?rke (lets the user select All car models, or a specific one from the list [login to view URL]), and Ort (city), where the user selects Min Plats (the phone's position) or a specific one from [login to view URL]). **2. Nyheter** (news) It works like the dealer list, tapping a cell opens a simple detail view with the article. **[login to view URL] & R?d** (tips & hints) It works like Nyheter, except there is a view one level above where you select one of the categories in [login to view URL] before seeing the list of tips. You must split [login to view URL] by these categories in the app. **Keys and values in the HTTPResponse** Name - Name of dealer (title) Distance - distance in km, with decimal places. Postort - city Service - car models that they service Saljer - car models that they sell Tjanster - other services Latitude - GPS position Longitude - GPS position You must handle empty strings: If Latitude or Longitude is empty, hide the Karta button. Zero, one or both of Service and Saljer may be empty. Handle this so it displays like in screenshot [login to view URL] for the 4 combos ("Servar" means "Performs service on"). The general rule is that a line is omitted if the value is empty. The .xml files in the .zip file are provided as example only, only use them for reference, not in the app! They should be self-explanatory. But if you need further information, contact AVIA via [login to view URL] chat or private message. Normal working hours in Sweden are 8.00-17.00 CET. **NOTE:** The final app must be delivered to AVIA in a form where it can be compiled with Eclipse and directly uploaded to Android market. The "reverse domain identifier" for the app should be **[login to view URL]**.