Community Projects > Mobile Apps

Common feature set?

(1/7) > >>

omängum fra'uti:
So far, for the Android application, all I have had to go on was a set of screenshots from the iPhone application, and inferred functionality based on that.  I honestly have no idea how the user experience compares to the iPhone app.

So to actually document it, here is what I currently have, and what I plan to do.

- Displays version, build number (Revision number) and DB number *REMOVE FOR RELEASE
- On initial start, checks for updated database & prompts for download
- Button to go to DICTIONARY
- Button to go to RESOURCES
- Back button exits app
* TODO: App settings (Auto check dictionary version, prompt for update, force update now, Dictionary provider URL?)

- Button to go to ABOUT
- Button to go to DISCLAIMER
- Button to open web browser on
- Back button also RETURN to MAIN SCREEN

- Display about message
- Display app and DB version (To stay after release)
- Back button also RETURN to RESOURCES

- Legal mumbo jumbo
- Back button also RETURN to RESOURCES

- Button to toggle English -> Na'vi and Na'vi -> English
- No back button *Phone supplied back button standard on Android
- List of word and definition (I think this might want part of speech abbreviation too)
- Clicking on word opens DICTIONARY ENTRY
- Back button RETURN to MAIN SCREEN
- Search function (Triggered by menu option, phone search button, or typing on phone keyboard where applicable - no persistently visible search entry, per standard Android interface design)
* TODO: Buttons to filter by part of speech
* TODO: Jump to letter (Assume that's what the letters down the right side in iPhone are?)

- On Android, a pop up in front of the word list rather than a full screen that is used on iPhone
- Word
- IPA (When available)
- Part of speech
- Definition
- Button to dismiss entry screen and return to word list
- Back button also dismiss entry screen and return to word list
* TODO: Picture, when available
* TODO: Play button, when spoken form available

Other stuff
- Requires dictionary for different languages
- Need translation for all strings (Right now Android app set up for localization, just lacking translations)
- For graphical screens, alternate version where desired - Perhaps change the text to an overlay graphic and just localize that?  (Again easy to do in Android app, just need the translation into different languages as graphics.)

Thats actually pretty close to how the iPhone App works.  In the dictionary, the letters on the side is the index.  It does the jump to section that you mentioned.  Also, there are separators in the dictionary for each section.  Its nothing more than a really short height cell with the Letter in it.  This is pretty standard stuff on the iPhone, wouldn't be surprised if its available on Android as well.  The only other big difference I see is that you do the popup thing for the dictionary entry instead of a separate page.  Any specific reason for this?  Not sure how well images would fit in a popup.

omängum fra'uti:
It just seemed to work better at the time, but that can certainly be easily changed.  If the images are small enough it could work, I'm thinking to the side on landscape screens and below on portrait screens...  It's just one line saying what sort of screen to open up so when images go in if it doesn't work, it can be changed.

The spacer thing between sections is not something I have seen on any Android application, but I'm sure I could figure out some way to do it.  Is it collapsing, where you touch it and everything in that category collapses under the label?  Also, does the index work like the iPhone keyboard where it zooms the letter under your finger, then goes to it when you release?

There is no collapsing.  They are just section headers.  The index on the side is really basic, when you press on it, the whole column highlights, and as you drag your finger on it, it moves the table to the start of the section that your finger is on.  Same thing if you just tap it, it will go to the top of the section you tapped.

This might be useful, Separating lists with headers in android.


[0] Message Index

[#] Next page

Go to full version