TechWiki - User contributions [en]

User:Benjchristensen

2012-10-15T14:10:19Z

Benjchristensen: Replaced content with "Ben Christensen"

Ben Christensen

User:Benjchristensen

2011-04-26T04:11:13Z

Benjchristensen:

Ben Christensen

I'm a Project Manager for the [[Gospel_Library_for_iOS|Gospel Library for iOS]] project.

Email: [mailto:benjc.ldstech@gmail.com| benjc.ldstech@gmail.com]

Gospel Library for iOS QA

2011-01-28T05:43:41Z

Benjchristensen: /* Sample Test Case */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

You will need to be logged in to file a bug. The username/password will typically be the same as your LDS.org username/password.

If you are not able to login [[User:Benjchristensen|contact me]] and I'll help you get setup.

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

[[File:Affects-version.png]]

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

====5) Description====

Fill out a detailed description and step-by-step instructions on how to replicate the bug.

[[File:Description.png]]

====6) Finish and Save====

If you have screenshots or crash logs you would like to attach, go ahead and do so.

Click the "Create" button to save the bug.

== Sample Test Case ==

Following is an example test case and template for use on the rest of our test cases.

===Making a Selection===

====Purpose of Test====

To validate that any reading view allows selection of text, that it defaults the selection to the current verse/paragraph and that it can be modified through dragging the beginning or ending markers.

====Pre-Requisites and/or Assumptions====
- Need to be logged in? Doesn't matter.
- Internet Connection Required? Doesn't matter.
- Must be online or offline? Doesn't matter.
- Anything to perform prior to this test case?
- Navigate to any book with a reading view.

====Environment====
- iOS 3.x and later
- iPhone 2nd generation and later
- iPad
- iPod touch 2nd generation and later

====Test Data====
- There is no specific test data needed to perform this test.

====Steps to Test====
- Navigate to book of scripture and open a chapter.
- Press and hold on a verse. It should select the entire verse and display beginning/ending markers at the beginning and end of the verse.
- Drag the beginning marker up and down to change the selection.
- Drag the ending marker up and down to change the selection.
- You should be able to be word specific about what is being selected.
- Click somewhere outside of the selection, it should de-select.
- When a selection is made, it should show a black popup with options saying "Copy | Hilight | Note"
- If you drag a marker to the top or bottom of the screen, the page should scroll and keep selecting text in that direction as it scrolls.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2011-01-28T05:27:06Z

Benjchristensen:

Gospel Library for iOS QA

2011-01-28T05:26:48Z

Benjchristensen: /* How to Submit Bug to JIRA */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

You will need to be logged in to file a bug. The username/password will typically be the same as your LDS.org username/password.

If you are not able to login [[User:Benjchristensen|contact me]] and I'll help you get setup.

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

[[File:Affects-version.png]]

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

====5) Description====

Fill out a detailed description and step-by-step instructions on how to replicate the bug.

[[File:Description.png]]

====6) Finish and Save====

If you have screenshots or crash logs you would like to attach, go ahead and do so.

Click the "Create" button to save the bug.

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2011-01-28T05:26:28Z

Benjchristensen: /* 6) Fix Version */

Gospel Library for iOS QA

2011-01-28T05:23:56Z

Benjchristensen: /* 5) Fix Version */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

You will need to be logged in to file a bug. The username/password will typically be the same as your LDS.org username/password.

If you are not able to login [[User:Benjchristensen|contact me]] and I'll help you get setup.

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

[[File:Affects-version.png]]

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

====5) Description====

Fill out a detailed description and step-by-step instructions on how to replicate the bug.

[[File:Description.png]]

====6) Fix Version====

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

File:Description.png

2011-01-28T05:22:53Z

Benjchristensen:

Gospel Library for iOS QA

2011-01-28T05:22:29Z

Benjchristensen: /* How to Submit Bug to JIRA */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

You will need to be logged in to file a bug. The username/password will typically be the same as your LDS.org username/password.

If you are not able to login [[User:Benjchristensen|contact me]] and I'll help you get setup.

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

[[File:Affects-version.png]]

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

====5) Fix Version====

====6) Fix Version====

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2011-01-28T05:14:37Z

Benjchristensen: /* 1) Go to JIRA "Bug Creation" Page */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

You will need to be logged in to file a bug. The username/password will typically be the same as your LDS.org username/password.

If you are not able to login [[User:Benjchristensen|contact me]] and I'll help you get setup.

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

[[File:Affects-version.png]]

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2011-01-28T05:08:56Z

Benjchristensen: /* 3) Affects Version and Environment */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

[[File:Affects-version.png]]

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

File:Affects-version.png

2011-01-28T05:08:37Z

Benjchristensen:

Gospel Library for iOS QA

2011-01-28T05:06:55Z

Benjchristensen: /* 2) Descriptive Summary */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

File:Descriptive-summary.png

2011-01-28T05:06:10Z

Benjchristensen:

Gospel Library for iOS QA

2011-01-28T04:57:12Z

Benjchristensen: /* How to Submit Bug to JIRA */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2011-01-28T04:45:15Z

Benjchristensen:

Gospel Library for iOS QA

2011-01-28T04:43:04Z

Benjchristensen:

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

===[[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]===

===[[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]===

===[[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]===

===[[Gospel_Library_for_iOS_QA_tagging|Tagging]]===

===[[Gospel_Library_for_iOS_QA_search|Search]]===

===[[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]===

===[[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]===

===[[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]===

===[[Gospel_Library_for_iOS_QA_settings|Settings]]===

===[[Gospel_Library_for_iOS_QA_localization|Localization]]===

===[[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]===

== How to Submit Bug to JIRA ==

instructions here for JIRA

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2011-01-28T04:27:13Z

Benjchristensen:

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

== Test Cases by Application Section ==

== How to Submit Bug to JIRA ==

instructions here for JIRA

== Sample Test Case ==

A sample test case.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2010-11-03T04:53:19Z

Benjchristensen:

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{{Under construction}}

===Quality Assurance===

Need to work with QA members of team to fill this in.

The concept is to have a QA process through which a release is tested for production release.

Already there are over 100k potential users of the application based on downloads and this number is expected to grow thus we need to ensure high quality releases.

[[Gospel_Library_for_iOS_QA_Use_Cases|Use Cases]]

Use Cases for iOS Gospel Library.

[[Gospel_Library_for_iOS_QA_Test_Cases|Test Cases]]

Test Cases for iOS Gospel Library.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2010-11-03T04:45:20Z

Benjchristensen:

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

{| style="position:relative; margin-left: 10px; background: #F2F3E5; border: 1px solid #aaa; border-left: 10px solid #ff8000; width: 50%;"
|-
| style="padding: 0.25em 0.5em; width: 100%; vertical-align:top;" | [[Image:Construction.png|60px|right]]This article is <b>under construction</b> for a brief time. {{{1|If the article has not been changed in a few days, you may remove this template.}}}
|}

===Quality Assurance===

Need to work with QA members of team to fill this in.

The concept is to have a QA process through which a release is tested for production release.

Already there are over 100k potential users of the application based on downloads and this number is expected to grow thus we need to ensure high quality releases.

[[Gospel_Library_for_iOS_QA_Use_Cases|Use Cases]]

Use Cases for iOS Gospel Library.

[[Gospel_Library_for_iOS_QA_Test_Cases|Test Cases]]

Test Cases for iOS Gospel Library.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS vision

2010-11-03T04:40:18Z

Benjchristensen:

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

== Usability of paper with features of digital ==
None of the benefits of paper should be lost when someone moves to digital.

For example:

* Anybody regardless of skill or education should be able to use the Gospel Library app to browse, read and study.
* Marking up, annotating, bookmarking must be as easy as grabbing a pen, not the result of navigating menus and options.
* Flipping between sections (such as D&C and OT both being used in a Sunday School class) must be as simple as "keeping a thumb" in one while looking at the other and flipping back and forth.

== Synchronized everywhere ==
* All data settings, markings, annotations, notes, bookmarks etc must follow a user wherever they go.
* A user should not ever have to think about "which device" their content is on.
* A user should never have to worry about backing up or losing data.
* A user should be able to read and mark something on an iPhone and pick up their iPad and resume at the same place reading with the same markings.
* The LDS.org website, iOS, Android, WebOS and all other devices should all be synchronized with each other via the same services - data created on one is available on all others without any thought of "syncing" - it just happens.

Examples:
* [http://itunes.apple.com/us/app/kindle/id302584613?mt=8 Kindle Apps] for iOS, Mac, PC, Kindle devices, Blackberry, etc.
* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]
* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]

== Globally distributed and accessible ==
* The app should be available in all countries that the iTunes App Store is available.
* The application and content should be localized to every language the standard works are available in.
* A user should be able to quickly switch content to any language - not just the language of their device - so that (for example) an English speaking user could flip to Spanish to teach someone with.
* Blind users should be able to use iOS VoiceOver to navigate the entire application as well as access audio versions of all content possible (scriptures, talks, videos, etc).

== Support all user contexts ==

The app should be capable of "following" a user to their different use cases in various contexts, such as:

* personal reading
* Sunday School
* Priesthood/RS
* seminary
* family reading
* lesson prep
* teaching/instructor

In a paper-based setting there may be different books, copies of books, bookmarks, etc., used in different settings. This won't generally exist in a digital world.

A person won't have different $300 devices with different LDS.org accounts for different contexts - instead the application must adapt and be flexible to them.

Why?

As a user moves from personal reading to Sunday School to Elder's Quorum to teaching with the missionaries, each setting requires being at different places in the Standard Works, wanting or not wanting markings and annotations and other such preferences.

Also, remembering where to be in each setting is left to the user rather than the device. This is unlike most "dead tree" technologies which will have bookmarks to hold reading places.

A book left on the nightstand at home versus one in the bag for church "remember" where they are and are contextual to an activity.

Thus, to be easy to end users to incorporate in their lives the application should allow "contexts" which remember the location and settings.

===== Examples =====
Personal reading:
* Resume reading at 2 Nephi 26
* dark mode on
* Annotations set to "Personal Reading 2010"

Elder's Quorum:
* Resume reading at General Conference April 2010
* dark mode off
* Annotations set to "Show All"

Teaching with missionaries:
* Resume reading at 3 Nephi 11
* Language set to Spanish
* Annotations set to "Show None"

===== Context switching =====
Switching between contexts should be as simple as putting down one physical book and picking up another.

The state of these "contexts" must sync between devices to follow a user. Personal reading on an iPad should be able to be resumed on an iPhone.

== Native feel and best in breed design ==

=== Use native UI elements ===
The user interface design and user experience should "feel at home" on the iOS devices - using native user interface elements and following Apple Human Interface Guidelines.

For example, text selection, copy/paste, highlighting, navigation etc should use native UI widgets - custom widgets should not be re-invented. Users are most comfortable using UI elements they are accustomed to and trained with through the use of the other apps and the operating system itself.

=== Design for screen size ===

The iPad is very different from the iPhone/iPod and needs to be designed for accordingly. Taking the iPhone UI and just "blowing it up" to iPad size is not sufficient. Not only does it poorly leverage all that the iPad can offer, but it often results in poor user experience.

For example, the iPhone screen width is perfect for reading and scrolling verses of scriptures. The iPad on the other hand is very wide and may be better suited to columns of text or a thin column of text with contextual footnotes and references in the page gutter.

Another example is that on the iPhone most button nav bars make sense to be at the bottom but on an iPad the top is generally better suited to how an iPad is used and held.

=== Focus on design ===

Functionality and engineering are not enough to make a product great - design means the look and feel down to the last pixel, worrying about things like animates and page transitions, simplifying navigation and feature discovery and polishing every aspect of the user experience.

All of these things drive engineering - not the other way around.

The user experience and design of the application should be thought of first to accomplish the best possible experience for the user and then engineering and development applied to that accomplishment.

=== Apple interface design guidelines ===
* [http://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/MobileHIG/Introduction/Introduction.html| iPhone Guidelines]
* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html| iPad Guidelines]

===Examples on iPad===
* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]
* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]
* [http://itunes.apple.com/us/app/reeder-for-ipad/id375661689?mt=8 Reeder for iPad]
* [http://itunes.apple.com/us/app/wikipanion-for-ipad/id364195592?mt=8 Wikipanion for iPad]
* [http://itunes.apple.com/us/app/articles-for-ipad/id364881979?mt=8 Articles for iPad]
* [http://itunes.apple.com/us/app/simplenote/id289429962?mt=8 Simplenote]

* [[Gospel_Library_for_iOS_UI_examples_iPad| Annotated examples of applications on iPad]]

==Other Nice Features==

===Encourage Gospel Study with Schedules===
* Interface with the ward calendars on LDS.org to make it easy to prepare for lessons
* Ability to set up study schedules like [http://www.readthescriptures.com/ ReadTheScriptures.com] and be reminded of schedules via notifications.

===Share the Gospel===
* Easily share passages, talks, scriptures and other media via email, facebook, and other build in applications.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS QA

2010-10-31T05:36:18Z

Benjchristensen:

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

===Quality Assurance===

Need to work with QA members of team to fill this in.

The concept is to have a QA process through which a release is tested for production release.

Already there are over 100k potential users of the application based on downloads and this number is expected to grow thus we need to ensure high quality releases.

[[Gospel_Library_for_iOS_QA_Use_Cases|Use Cases]]

Use Cases for iOS Gospel Library.

[[Gospel_Library_for_iOS_QA_Test_Cases|Test Cases]]

Test Cases for iOS Gospel Library.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS vision

2010-10-31T05:32:42Z

Benjchristensen: /* Examples */

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

== Usability of paper with features of digital ==
None of the benefits of paper should be lost when someone moves to digital.

For example:

* Anybody regardless of skill or education should be able to use the Gospel Library app to browse, read and study.
* Marking up, annotating, bookmarking must be as easy as grabbing a pen, not the result of navigating menus and options.
* Flipping between sections (such as D&C and OT both being used in a Sunday School class) must be as simple as "keeping a thumb" in one while looking at the other and flipping back and forth.

== Synchronized everywhere ==
* All data settings, markings, annotations, notes, bookmarks etc must follow a user wherever they go.
* A user should not ever have to think about "which device" their content is on.
* A user should never have to worry about backing up or losing data.
* A user should be able to read and mark something on an iPhone and pick up their iPad and resume at the same place reading with the same markings.
* The LDS.org website, iOS, Android, WebOS and all other devices should all be synchronized with each other via the same services - data created on one is available on all others without any thought of "syncing" - it just happens.

Examples:
* [http://itunes.apple.com/us/app/kindle/id302584613?mt=8 Kindle Apps] for iOS, Mac, PC, Kindle devices, Blackberry, etc.
* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]
* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]

== Globally distributed and accessible ==
* The app should be available in all countries that the iTunes App Store is available.
* The application and content should be localized to every language the standard works are available in.
* A user should be able to quickly switch content to any language - not just the language of their device - so that (for example) an English speaking user could flip to Spanish to teach someone with.
* Blind users should be able to use iOS VoiceOver to navigate the entire application as well as access audio versions of all content possible (scriptures, talks, videos, etc).

== Support all user contexts ==

The app should be capable of "following" a user to their different use cases in various contexts, such as:

* personal reading
* Sunday School
* Priesthood/RS
* seminary
* family reading
* lesson prep
* teaching/instructor

In a paper-based setting there may be different books, copies of books, bookmarks, etc., used in different settings. This won't generally exist in a digital world.

A person won't have different $300 devices with different LDS.org accounts for different contexts - instead the application must adapt and be flexible to them.

Why?

As a user moves from personal reading to Sunday School to Elder's Quorum to teaching with the missionaries, each setting requires being at different places in the Standard Works, wanting or not wanting markings and annotations and other such preferences.

Also, remembering where to be in each setting is left to the user rather than the device. This is unlike most "dead tree" technologies which will have bookmarks to hold reading places.

A book left on the nightstand at home versus one in the bag for church "remember" where they are and are contextual to an activity.

Thus, to be easy to end users to incorporate in their lives the application should allow "contexts" which remember the location and settings.

===== Examples =====
Personal reading:
* Resume reading at 2 Nephi 26
* dark mode on
* Annotations set to "Personal Reading 2010"

Elder's Quorum:
* Resume reading at General Conference April 2010
* dark mode off
* Annotations set to "Show All"

Teaching with missionaries:
* Resume reading at 3 Nephi 11
* Language set to Spanish
* Annotations set to "Show None"

===== Context switching =====
Switching between contexts should be as simple as putting down one physical book and picking up another.

The state of these "contexts" must sync between devices to follow a user. Personal reading on an iPad should be able to be resumed on an iPhone.

== Native feel and best in breed design ==

=== Use native UI elements ===
The user interface design and user experience should "feel at home" on the iOS devices - using native user interface elements and following Apple Human Interface Guidelines.

For example, text selection, copy/paste, highlighting, navigation etc should use native UI widgets - custom widgets should not be re-invented. Users are most comfortable using UI elements they are accustomed to and trained with through the use of the other apps and the operating system itself.

=== Design for screen size ===

The iPad is very different from the iPhone/iPod and needs to be designed for accordingly. Taking the iPhone UI and just "blowing it up" to iPad size is not sufficient. Not only does it poorly leverage all that the iPad can offer, but it often results in poor user experience.

For example, the iPhone screen width is perfect for reading and scrolling verses of scriptures. The iPad on the other hand is very wide and may be better suited to columns of text or a thin column of text with contextual footnotes and references in the page gutter.

Another example is that on the iPhone most button nav bars make sense to be at the bottom but on an iPad the top is generally better suited to how an iPad is used and held.

=== Focus on design ===

Functionality and engineering are not enough to make a product great - design means the look and feel down to the last pixel, worrying about things like animates and page transitions, simplifying navigation and feature discovery and polishing every aspect of the user experience.

All of these things drive engineering - not the other way around.

The user experience and design of the application should be thought of first to accomplish the best possible experience for the user and then engineering and development applied to that accomplishment.

=== Apple interface design guidelines ===
* [http://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/MobileHIG/Introduction/Introduction.html| iPhone Guidelines]
* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html| iPad Guidelines]

=== [[Gospel_Library_for_iOS_UI_examples_iPad| Examples on iPad]] ===
* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]
* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]
* [http://itunes.apple.com/us/app/reeder-for-ipad/id375661689?mt=8 Reeder for iPad]
* [http://itunes.apple.com/us/app/wikipanion-for-ipad/id364195592?mt=8 Wikipanion for iPad]
* [http://itunes.apple.com/us/app/articles-for-ipad/id364881979?mt=8 Articles for iPad]
* [http://itunes.apple.com/us/app/simplenote/id289429962?mt=8 Simplenote]

[[Category:Gospel Library for iOS]]

Gospel Library for iOS UI examples iPad

2010-10-31T05:31:12Z

Benjchristensen: moved Gospel Library for iOS UI examples iPad to Gospel Library for iOS user interface examples on iPad: To make the page header look better while conforming to the "don't capitalize titles" rule.

#REDIRECT [[Gospel Library for iOS user interface examples on iPad]]

Gospel Library for iOS user interface examples on iPad

2010-10-31T05:31:12Z

Return to [[Gospel_Library_for_iOS_design|iOS Design]] page.

==Examples of reader application UIs on iPad==

===[http://itunes.apple.com/us/app/ibooks/id364709193?mt=8| iBooks]===

* Multi-colored hi-lighting
* Standard text-selection controls
* Hi-lighting, color selection and text management built into OS-standard text popup controls
* Navigation bar at top
* Navigation hides/shows with single touch anywhere on screen
* Notes display inline in page gutter, created through same text selection popup controls
* Popover search
* Popover dictionary definitions (compare with what can be done on cross-references, footnotes, etc)
* Pagination information at the bottom is a nice touch that converts the "digital" into a "physical" feel
** Potentially very valuable to display physical page numbers in Gospel Library to correlate location between digital and physical world for settings such as Sunday School where an instructor says "now turn to page xxx" or "let's read the first paragraph of page yy"
* Overall a clean design though the "book" feel of the pages in the background is obviously unnecessary
* Synchronizes annotations (hi-lights, bookmarks, notes) and reading location automatically between devices (iPhone and iPad for example)

[[File:IBooks-1.png|400px]]
[[File:IBooks-2.png|400px]]
[[File:IBooks-3.png|400px]]
[[File:IBooks-4.png|400px]]
[[File:IBooks-5.png|400px]]
[[File:IBooks-6.png|400px]]
[[File:IBooks-7.png|400px]]
[[File:IBooks-8.png|400px]]
[[File:IBooks-9.png|400px]]

===[http://itunes.apple.com/us/app/articles-for-ipad/id364881979?mt=8| Articles for iPad]===

* Beautiful layout and design including typography
* Images are styled nicely to fit the design
* Every article has a 'globe' at the top allowing access to languages the article is in
** This could be very powerful in the Gospel Library so that on any scripture, talk, video or other document it can immediately be accessed in any language.
* Popovers are effectively used for quick navigation within an article or for changing settings
* Navigation bar at top

[[File:Articles-1.png|400px]]
[[File:Articles-2.png|400px]]
[[File:Articles-3.png|400px]]
[[File:Articles-4.png|400px]]

===[http://itunes.apple.com/us/app/inkling/id379351586?mt=8| Inkling]===

* Excellent navigation system for dealing with very large textbooks
** Uses both the top and side bar for navigation
** Sidebar works very well on an iPad with the extra screen real-estate and typical two-handed use of the device
* Sidebar shows context of the current chapter for location in the document and sections
** The sidebar could be potentially useful in the Gospel Library for similar reasons
* Popovers provide rapid access to settings and navigation
* Graphical representation of books and chapters instead of just text
** Could be very powerful in Gospel Library to use iconography instead of just text lists to provide richer visual differentiation of the many types of content
* Annotations (hi-lights and notes) are easy to use and discoverable without documentation since they use OS-standard text selection controls

[[File:Inkling-1.png|400px]]
[[File:Inkling-2.png|400px]]
[[File:Inkling-3.png|400px]]
[[File:Inkling-4.png|400px]]

===[http://itunes.apple.com/us/app/instapaper/id288545208?mt=8| Instapaper]===

* Minimal and highly functional UI
* Navigation bar at top
** Originally had bar at bottom when it migrated from iPhone but moved to top after some user experience demonstrated that on an iPad the top bar is better suited to where hands are held.
* Fast and easy to switch between Light and Dark modes for day/night use.
* The entire UI including navigation lists use the Light/Dark modes, not just the reading view
* OS-standard text selection controls are used to integrate application specific sharing features
* Synchronizes automatically
** Content between devices and web
** Reading location within articles

[[File:Instapaper-1.png|400px]]
[[File:Instapaper-2.png|400px]]
[[File:Instapaper-3.png|400px]]

===[http://itunes.apple.com/us/app/reeder-for-ipad/id375661689?mt=8| Reeder]===

* Uses sidebar navigation effectively so that holding the iPad with two-hands allow effective controls with the thumb.
* Popovers and top navigation are also used similar to the other apps.

[[File:Reeder-1.png|400px]]
[[File:Reeder-2.png|400px]]

===[http://itunes.apple.com/us/app/simplenote/id289429962?mt=8| Simplenote]===

* Top navigation bar and popovers
* Tags are effectively used for allowing articles in multiple "categories" for searching, filtering and navigating
** Could be very effective with Gospel Library for tagging hi-lights, notes etc

[[File:Simplenote-1.png|400px]]
[[File:Simplenote-2.png|400px]]

===[http://itunes.apple.com/us/app/wikipanion-for-ipad/id364195592?mt=8| Wikipanion]===

* Top navigation bar and popovers

[[File:Wikipanion-1.png|400px]]

Gospel Library for iOS user interface examples on iPad

2010-10-31T05:29:58Z

Benjchristensen:

Gospel Library for iOS user interface examples on iPad

2010-10-31T05:10:45Z

Benjchristensen:

File:Wikipanion-1.png

2010-10-31T05:04:21Z

Benjchristensen:

File:Simplenote-2.png

2010-10-31T05:04:10Z

Benjchristensen:

File:Simplenote-1.png

2010-10-31T05:04:00Z

Benjchristensen:

File:Reeder-2.png

2010-10-31T05:03:43Z

Benjchristensen:

File:Reeder-1.png

2010-10-31T05:03:25Z

Benjchristensen:

File:Instapaper-3.png

2010-10-31T05:03:09Z

Benjchristensen:

File:Instapaper-2.png

2010-10-31T05:02:58Z

Benjchristensen:

File:Instapaper-1.png

2010-10-31T05:02:47Z

Benjchristensen:

File:Inkling-4.png

2010-10-31T05:00:24Z

Benjchristensen:

File:Inkling-3.png

2010-10-31T05:00:08Z

Benjchristensen:

File:Inkling-2.png

2010-10-31T04:59:56Z

Benjchristensen:

File:Inkling-1.png

2010-10-31T04:59:42Z

Benjchristensen:

File:IBooks-9.png

2010-10-31T04:59:26Z

Benjchristensen:

File:IBooks-8.png

2010-10-31T04:59:14Z

Benjchristensen:

File:IBooks-7.png

2010-10-31T04:59:00Z

Benjchristensen:

File:IBooks-6.png

2010-10-31T04:58:50Z

Benjchristensen:

File:IBooks-5.png

2010-10-31T04:58:38Z

Benjchristensen:

File:IBooks-4.png

2010-10-31T04:58:24Z

Benjchristensen:

File:IBooks-3.png

2010-10-31T04:58:10Z

Benjchristensen:

File:IBooks-2.png

2010-10-31T04:57:57Z

Benjchristensen:

File:Articles-4.png

2010-10-31T04:57:43Z

Benjchristensen:

File:Articles-3.png

2010-10-31T04:56:48Z

Benjchristensen:

File:Articles-2.png

2010-10-31T04:56:35Z

Benjchristensen: