Thanks @david_moore1. If that actually works, it sounds like it could be closer to achieving our desired end result. BUT, for us, I feel that it would be clunky to have multiple sets of identical contents pages built into our app, with the only difference being the target destination of contents items. It also has the BIG downside of giving us a lot more work! We have 100 contents menu items in the app and 7 languages. That means that for each language I would have to create 100 new contents menu items with new target destinations for every content item. We plan to add many more languages into the app, and it would just be so much nicer for the app to have that “Language & Layout” box visible at first open of the app.
It makes the most sense to me to be able to select language from the Language & Layout box rather than in the contents menu. Currently we only have the Single Pane layout enabled in the app, but we will may likely want to enable the Two Pane and/or the Verse by Verse layouts for users to reference more language translations at one glance… this is another argument to keep the language selection in the Language & Layout box and not put it in the contents menu.
I think that people who have built Bible apps with multiple languages and translations may also find it great for the Language & Layout box to appear at initial opening of the app. This helps users right away set up the app the way they want it. For example, if a Bible app for the languages in a country was produced, new users would only want the app for one or two languages and not the 10 or more others contained in the app - so that Language & Layout box at initial startup would be useful for them.
To me it seems like this feature request could be quite easy to add in. Or am I wrong about that?
Thanks @david_moore1 and @GregAshleyCooper for thinking critically through this with me. It’s good for creativity sakes and it forces me to examine more carefully what I’m after.