Gospel Library for iOS vision - Revision history

Sbradshaw: Redirect to Gospel Library support page

2018-04-09T21:45:31Z

Redirect to Gospel Library support page

← Older revision		Revision as of 21:45, 9 April 2018
Line 1:		Line 1:
			#REDIRECT [[Gospel Library support]]

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

Aebrown: Fix incorrect heading levels

2012-08-04T14:32:42Z

Fix incorrect heading levels

← Older revision		Revision as of 14:32, 4 August 2012
Line 54:		Line 54:
	Thus, to be easy to end users to incorporate in their lives the application should allow "contexts" which remember the location and settings.		Thus, to be easy to end users to incorporate in their lives the application should allow "contexts" which remember the location and settings.

	===== Examples =====		=== Examples ===
	Personal reading:		Personal reading:
	* Resume reading at 2 Nephi 26		* Resume reading at 2 Nephi 26
Line 77:		Line 77:
	* Display ordered set of talking points with live linked references when speaking		* Display ordered set of talking points with live linked references when speaking

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

Briancragun: Use case for preparing a talk

2012-08-04T12:27:18Z

Use case for preparing a talk

← Older revision		Revision as of 12:27, 4 August 2012
Line 69:		Line 69:
	* Language set to Spanish		* Language set to Spanish
	* Annotations set to "Show None"		* Annotations set to "Show None"

			Preparing a talk or lesson
			* Search topical material
			* List points to say
			* Link to references
			* Order talking points and references
			* Display ordered set of talking points with live linked references when speaking

	===== Context switching =====		===== Context switching =====

Benjchristensen at 04:40, 3 November 2010

2010-11-03T04:40:18Z

← Older revision		Revision as of 04:40, 3 November 2010
Line 102:		Line 102:
	* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html\| iPad 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]] ===		===Examples on iPad===
	* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]		* [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/instapaper/id288545208?mt=8 Instapaper]
Line 109:		Line 109:
	* [http://itunes.apple.com/us/app/articles-for-ipad/id364881979?mt=8 Articles 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]		* [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==		==Other Nice Features==

Jeffvand at 19:18, 1 November 2010

2010-11-01T19:18:10Z

← Older revision		Revision as of 19:18, 1 November 2010
Line 114:		Line 114:
	===Encourage Gospel Study with Schedules===		===Encourage Gospel Study with Schedules===
	* Interface with the ward calendars on LDS.org to make it easy to prepare for lessons		* 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/] and be reminded of schedules via notifications.		* Ability to set up study schedules like [http://www.readthescriptures.com/ ReadTheScriptures.com] and be reminded of schedules via notifications.

	===Share the Gospel===		===Share the Gospel===

Jeffvand at 19:17, 1 November 2010

2010-11-01T19:17:23Z

@@ Line 89: / Line 89: @@
 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 ===
@@ Line 116: / Line 109: @@
 * [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]]

Jeffvand at 19:16, 1 November 2010

2010-11-01T19:16:21Z

← Older revision		Revision as of 19:16, 1 November 2010
Line 89:		Line 89:

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

			===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/] 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.

	=== Focus on design ===		=== Focus on design ===

Benjchristensen: /* Examples */

2010-10-31T05:32:42Z

Examples

← Older revision		Revision as of 05:32, 31 October 2010
Line 102:		Line 102:
	* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html\| iPad Guidelines]		* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html\| iPad Guidelines]

	=== Examples ===		=== [[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/ibooks/id364709193?mt=8 iBooks]
	* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]		* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]

Benjchristensen: /* Examples */

2010-10-31T04:32:55Z

Examples

← Older revision		Revision as of 04:32, 31 October 2010
Line 105:		Line 105:
	* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]		* [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/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]]		[[Category:Gospel Library for iOS]]

Aebrown: Standardize capitalization and heading levels

2010-10-29T11:58:19Z

Standardize capitalization and heading levels

← Older revision		Revision as of 11:58, 29 October 2010
Line 75:		Line 75:
	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.		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 ==

	~~== Native Feel and Best in Breed Design ==~~		=== Use native UI elements ===

	=====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.		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, ~~hilighting~~, 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.		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=====		=== 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.		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.
Line 91:		Line 90:
	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.		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=====		=== 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.		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.
Line 99:		Line 98:
	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.		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==~~===		=== 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/UserExperience/Conceptual/MobileHIG/Introduction/Introduction.html\| iPhone Guidelines]
	* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html\| iPad Guidelines]		* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html\| iPad Guidelines]

	=====Examples=====		=== Examples ===
	* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]		* [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/instapaper/id288545208?mt=8 Instapaper]



	[[Category:Gospel Library for iOS]]		[[Category:Gospel Library for iOS]]