Android version of our iPhone app Lätt Mätt

Виконано Опубліковано %project.relative_time Оплачується при отриманні
Виконано Оплачується при отриманні

This app will allow Android mobile phone users to get a list of material for, and build, a veranda, deck, or landing-stage using different classes of rot-protected beams and planks from Svenska Tr?skyddsf?reningen, specifically:

1. See and compare the correct class of wood product for miscellaneous building projects.

2. Select a "deck" shape and set its measurements, select beam/plank dimensions, and see a material specification and optionally e-mail it to a friend.

3. Read tips and advice (online PDFs) and visit the company's website (WebView).

4. Read an inspiration document (online PDF).

## Deliverables

For the full functional description of the individual views, see the PDF in the zip file. The app structure consists of a main menu or tab bar with 4 main views and 6 sub-views which are simple detail views or for selecting/entering data.

The app "L?tt M?tt" design specifications

Snags:

These are the most frequent things that pop up in the test-feedback loop after the developer's final version and before approving the app. Watch out for these and build your app already from the startup to support these things, to save time for you and us. Please make sure you can develop according to these points before bidding.

1. Don't use any fixed urls anywhere in the app - except one. This url is the address of an XML file containing whatever base directory on the web where you load all other files and images from.

2. Don't use fixed strings for any text that is displayed, even if we don't specify that the app is to be localized. Our customer may request another language translation later, and then we (or you) can do the job of translation faster. It also enables us (or you) to fix simple spelling errors quickly, instead of prolonging the approval-test cycle.

3. You must use a caching method that allows you to always serve information that are as fresh as the cache times specified in the app.

4. XML is without exception in "Apple Plist 1.0" format. You must be able to parse this, and handle any character escaping necessary.

5. All text strings including those fetched from XML or HTTPResponses are UTF-8, no BOM. This includes strings in projects and sources. We are from Sweden, so here are the strange characters we use: ????? ?????. If possible, please deliver all project sources in UTF-8, no BOM when the project is delivered to us.

6. If you can, please download and use the iPhone app from App Store to get a better sense of how the information is presented and navigated.

7. Important: Text must be readable and buttons must be touchable (avoid tiny font sizes and button sizes)

8. Hilight clickable areas such as buttons when clicked, to confirm that the touch took effect.

Summary:

This app will allow Android mobile phone users to get a list of material for, and build, a veranda, deck, or landing-stage using different classes of rot-protected beams and planks from Svenska Tr?skyddsf?reningen, specifically:

1. See and compare the correct class of wood product for miscellaneous building projects.

2. Select a "deck" shape and set its measurements, select beam/plank dimensions, and see a material specification and optionally e-mail it to a friend.

3. Read tips and advice (online PDFs) and visit the company's website (WebView).

4. Read an inspiration document (online PDF).

These 4 points correspond to the 4 main menu buttons at the bottom of the iPhone screenshots. (Called View 1...4 below.)

The provided screenshots show all views and they are numbered 1..4 for the main views and 2-1, 2-2 and so on for the subviews.

All data in this app are online files, except text on buttons and titles.

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.

All data views are in portrait orientation only, so no need to accomodate auto-rotated views.

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: [url removed, login to view] - 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:

[url removed, login to view] (texts shown by pressing the 4 "NTR-x" buttons in View 1)

[url removed, login to view] (populates column "Regel" in the Dimension Selector subview of View 2)

[url removed, login to view] (populates column "Trall" in the Dimension Selector subview of View 2)

[url removed, login to view] (texts corresponding to email signature, first-use popup warning text, and email subject)

[url removed, login to view] (urls for articles in View 3)

Caching:

You may cache anything you like for performance, but if the XML data is older than 24 hours, 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.

If data is loaded, the user must be informed with the usual "loading spinner". Any text shown while loading should read "Laddar...".

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".

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.

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 full-screen loading picture is shown, 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.

Android Java Mobile App Development

ID Проекту: #2708744

Про проект

2 заявок(-ки) Дистанційний проект Остання активність Feb 16, 2012

Доручено:

itIndia2

See private message.

$850 USD за 14 дні(-в)
(77 відгуків(-и))
7.1

2 фрілансерів(-и) готові виконати цю роботу у середньому за $675

ipgvs

See private message.

$500 USD за 14 дні(-в)
(24 відгуків(и))
5.7