Copying Fotoura iPhone app to Android platform
- or -
Post a project like this4020
$$
- Posted:
- Proposals: 5
- Remote
- #231311
- Awarded
Description
Experience Level: Intermediate
FOTOURA IPHONE TO ANDROID CONVERSION OVERVIEW:
Fotoura are looking to provide their app on the Android platform and are looking to create a functionally identical version on Android.
There is already an Android app in place which was a pre-cursor to the iPhone version but that hasn't been updated in 18 months.
Although it may provide a quick start base to development it may also only provide some elements of code to short-cut the build. Or a developer may choose to start from scratch.
Please also refer to Fotoura Android app to see existing functionality (though there is a lot more under the thin exterior).
DEFINITION DETAILS:
Please refer to the Fotoura iPhone App. Please also take a look at the Royal Photographic Society app to see the similarity and understand how the app varies between the two (very little).
The App works by taking an xml feed of content that includes definitions of how the content must be displayed in each of the tabbed sections of the app.
For example, defines inclusion on first highlights tab, define categories and define event information.
Tours (content)
Each unit of information / content is called a . Each is a single square in the highlights page and a single details page when clicked. The two are intrinsically linked and both come from each .
The xml feed is purely made up of nothing else.
Mapping
Map functionality takes the geo-coordinates from each tour and uses them to plot a combined map of these coordinates in relation to the users position.
Brief overview of the App functionality
1. Splash screen
2. Highlights page - two rows of left / right swipeable content that clicks into content pages.
3. Seach of all content in the app.
4. Map feature that takes geo-cordinates from on-page coordinates and displays on a relatively zoomed map including client location.
5. Categories list based on tags that allows drill down into tags then links to content pages.
6. Events list split into three sections - on now, next week , in the future using data information stored in 'tour' xml
7. Bookmarking feature split into saved activities (non dated tours) and saved events (dated tours)
8. More section including links to support information.
9. Highlights page content - has a randomisation feature. Takes yes tours and displays at random 16 tours.
10. XML feed of tours. The app takes a feed of xml. The app loads existing cached content on open then checks for new xml feed based on file size and reloads accordingly. Multiple xml feeds are combined to make up the app content. There is a standard xml format which will be provided. New content must be checked for every 'x' minutes.
11. Existing app includes additional functionality that must be preserved. More information will be provided.
12. Content pages - these include the ability to use html links within pages to link to other content pages & category pages within the app. They also include links out to call phones and to external websites.
Timeline
6 weeks maximum
Ongoing development
This App is constantly evolving and developing. There is a requirement for ongoing support to re-develop this app.
Next steps (not part of this brief but FYI)
The current iPhone app has functionality beyond what you can see. This will be discussed and briefed once the right developer has been chosen.
Add multiple rows to highlights page so content can be swiped down to get additional content rows.
The current iPhone app is being developed to add localisation so the content in the highlights and events page shows the most relevant location content - more information will be provided on this.
Fotoura are looking to provide their app on the Android platform and are looking to create a functionally identical version on Android.
There is already an Android app in place which was a pre-cursor to the iPhone version but that hasn't been updated in 18 months.
Although it may provide a quick start base to development it may also only provide some elements of code to short-cut the build. Or a developer may choose to start from scratch.
Please also refer to Fotoura Android app to see existing functionality (though there is a lot more under the thin exterior).
DEFINITION DETAILS:
Please refer to the Fotoura iPhone App. Please also take a look at the Royal Photographic Society app to see the similarity and understand how the app varies between the two (very little).
The App works by taking an xml feed of content that includes definitions of how the content must be displayed in each of the tabbed sections of the app.
For example, defines inclusion on first highlights tab, define categories and define event information.
Tours (content)
Each unit of information / content is called a . Each is a single square in the highlights page and a single details page when clicked. The two are intrinsically linked and both come from each .
The xml feed is purely made up of nothing else.
Mapping
Map functionality takes the geo-coordinates from each tour and uses them to plot a combined map of these coordinates in relation to the users position.
Brief overview of the App functionality
1. Splash screen
2. Highlights page - two rows of left / right swipeable content that clicks into content pages.
3. Seach of all content in the app.
4. Map feature that takes geo-cordinates from on-page coordinates and displays on a relatively zoomed map including client location.
5. Categories list based on tags that allows drill down into tags then links to content pages.
6. Events list split into three sections - on now, next week , in the future using data information stored in 'tour' xml
7. Bookmarking feature split into saved activities (non dated tours) and saved events (dated tours)
8. More section including links to support information.
9. Highlights page content - has a randomisation feature. Takes yes tours and displays at random 16 tours.
10. XML feed of tours. The app takes a feed of xml. The app loads existing cached content on open then checks for new xml feed based on file size and reloads accordingly. Multiple xml feeds are combined to make up the app content. There is a standard xml format which will be provided. New content must be checked for every 'x' minutes.
11. Existing app includes additional functionality that must be preserved. More information will be provided.
12. Content pages - these include the ability to use html links within pages to link to other content pages & category pages within the app. They also include links out to call phones and to external websites.
Timeline
6 weeks maximum
Ongoing development
This App is constantly evolving and developing. There is a requirement for ongoing support to re-develop this app.
Next steps (not part of this brief but FYI)
The current iPhone app has functionality beyond what you can see. This will be discussed and briefed once the right developer has been chosen.
Add multiple rows to highlights page so content can be swiped down to get additional content rows.
The current iPhone app is being developed to add localisation so the content in the highlights and events page shows the most relevant location content - more information will be provided on this.
Rich G.
100% (1)Projects Completed
2
Freelancers worked with
2
Projects awarded
67%
Last project
12 Jul 2013
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies