3rd Party API - More Ways to tap Into Talent/Skills of interested parties

toddhopkinson
New Member
Posts: 2
Joined: Sun Dec 04, 2016 5:03 pm

3rd Party API - More Ways to tap Into Talent/Skills of interested parties

Postby toddhopkinson » Sun Dec 04, 2016 5:26 pm

Hi,

Why is there no third-party API for scripture and other gospel library content made available to allow the community of software engineers / app developers / innovators within the church (or even without) but not necessarily employed by the church so that we can have the ability to access and push forward on 3rd party projects and products utilizing these resources? I can't think of a better way to promote innovations, ideas, practices, and advances around the great treasures we have here than to open up the services and resources to all of us.

There are many of us who are eager to make use of the official versions of church resources/material, and who currently cannot, because they are restricted to internal projects.

If control is needed, this is easily resolved the same way every other 3rd party API out there uses, such as through app secrets/app keys controlled by the API's authority. Whatever the means, control can easily be guaranteed the church to insure no 3rd party is able to use the API in a way that is questionable or undesirable.

Thanks,

Todd Hopkinson
Lava Monster Labs
www.Lavamonster.io
480-236-3651

User avatar
sbradshaw
Senior Member
Posts: 3207
Joined: Mon Sep 26, 2011 8:42 pm
Location: Provo, UT
Contact:

Re: 3rd Party API - More Ways to tap Into Talent/Skills of interested parties

Postby sbradshaw » Tue Dec 06, 2016 6:42 pm

See this thread:
https://tech.lds.org/forum/viewtopic.php?t=25463

Also, it's important to keep in mind that not all content published by the Church is owned by the Church – some of it is governed by contracts the Church has with other parties. For example, several of the hymns; also, photos in manuals and sound/video clips from Church-produced videos may not always be owned by the Church. In fact, not too long ago the Church was implicated in a lawsuit because a third party was using the Alexander Scourby Bible recordings from LDS.org in their third-party scriptures app. The Church had permission to use it, but not to provide it for others to use.
Samuel Bradshaw • If you desire to serve God, you are called to the work.

toddhopkinson
New Member
Posts: 2
Joined: Sun Dec 04, 2016 5:03 pm

Re: 3rd Party API - More Ways to tap Into Talent/Skills of interested parties

Postby toddhopkinson » Sat Dec 10, 2016 11:30 pm

Thanks for responding Samuel.

Let's simplify and narrow the API to the standard works then, for sake of discussion.

I have yet to hear any valid reason an API should not be provided to allow 3rd parties to develop prototypes, proof of concepts, and actual projects and products (adhering any/all conditions desired by the church) under a church-controlled access-permitted condition.

Such an API would allow additional talent and capable individuals to participate and contribute in the arena of ideas and innovations on mobile applications, services, tools, and platforms dedicated to the standard works -- thus exposing one another (including the internal church dev teams) to numerous concepts, approaches, insights, & ideas - challenging one another to pull the best elements from wherever they may be into the tools and platforms waiting to be created for the Scriptures.

The fact of the matter is that while the solutions and products we have right now for the digital consumption of the standard works are good, they are only the starting point of what is possible and intended, I'm confident.

Let's open the doors to allow additional talent on-board to support and contribute to the pool of dedicated individuals already engaged thus far, but in a way that best makes use of what we each have to offer. A 3rd-party API (subject to church-approval or rejection of any applicant/use at any time for any reason) could really catalyze some amazing things for the ways we access and use the scriptures digitally.

russellhltn
Community Administrator
Posts: 22163
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Re: 3rd Party API - More Ways to tap Into Talent/Skills of interested parties

Postby russellhltn » Sun Dec 11, 2016 1:16 am

The church is unlike any "business" you'll ever run across. Everything answers to the Brethren, not to "the consumer".

Secondly, the church has a very small pool of developers and their priority list is set by the Priesthood Department. An API would require finding time on that priority list.

Third, while a community forum is a good place to get feedback, it's an ineffective place for advocacy since none of the decision makers visit here.

If you have a specific project in mind, then I suggest you contact the IP Office at permissions.lds.org. That's what someone did for a Amazon Echo project and it seems to be proceeding.
Have you searched the Wiki?
Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.


Return to “Mobile Applications”

Who is online

Users browsing this forum: No registered users and 1 guest