Some day in the future we envision having components packaged into single bundles like widgets that can be easily dropped into a web page (right now there's quite a bit of overhead for getting into the Polymer ecosystem). For example, sites that link their records of profiles to FamilySearch persons could drop in a
<fs-person-summary> bundle and display a summary of the linked person from FamilySearch without having to install bower and include Polymer and polyfills.
However, the value of these budnled components are decreased by the FamilySearch API not allowing unauthenticated read access. In other words, at the moment users would have to authenticate via OAuth 2 with FamilySearch before they'd see any data in those widgets. That's not a good user experience.
Some day in the future we envision having components packaged into single bundles like widgets that can be easily dropped into a web page (right now there's quite a bit of overhead for getting into the Polymer ecosystem). For example, sites that link their records of profiles to FamilySearch persons could drop in a
<fs-person-summary>bundle and display a summary of the linked person from FamilySearch without having to install bower and include Polymer and polyfills.However, the value of these budnled components are decreased by the FamilySearch API not allowing unauthenticated read access. In other words, at the moment users would have to authenticate via OAuth 2 with FamilySearch before they'd see any data in those widgets. That's not a good user experience.