On the web the page title can be set in code, it would be nice if a similar command could be added to mobile, so that one page could be used for content channel items and then the channel title could become the page title in the nav bar.

---

I was working on the Connection Opportunity Search block and the default Lava template for the Detail Page has this code:```{% if DetailPage contains '?' %}                  <a class="btn btn-default" href="{{ DetailPage }}&OpportunityId={{ opportunity.Id }}" role="button">More Info</a>         {% else %}                  <a class="btn btn-default" href="{{ DetailPage }}?OpportunityId={{ opportunity.Id }}" role="button">More Info</a> {% endif %}```I guess this block was from the earlier version of Rock. I would like to request to standardize how block behaves with Page Picker, when route is selected, then route...

---

Right now it looks like the logic to find a profile will return a profile regardless what phone type it was stored under.Ideally if we are using a mobile phone to verify a profile, it would only search for numbers with the "Mobile" type.We've found that parents will put their phone number under the "Home" type for some reason.At one point we created a "Emergency Phone" type that started creating more duplicates because it matched the parents mobile number.By searching by "Mobile" type only, we are increasing the chance of a matched profile, decreasing duplicates, and giving users a better...

---

The new LMS feature is a good start. Unfortunately, it does not support the industry standard SCORM files. This is essential for those of us who have courses built in other LMS’s. It would allow us to export those courses directly instead of having to rebuild them from scratch. Further, it allows you to design courses in other design software and import them into your LMS. Again, this is the industry standard for LMS’s, so for the Rock LMS to really reach maturity, it should have support for an industry standard.In terms of funding, I have no idea what adding...

---

Many organizations are running into limitations due to architecture and performance designs with Rock. This affects every area of the organization from:User Experiences like Event Registrations, Giving and large engagement moments ("everybody take out your phone....")Production needs being addressed by other more reliable technologiesFinances (Windows OS Dependence is expensive at scale)The ability to containerize, put at the edge for geographic diversityContext / distributed data across multi-location organizationsWould love to have a multi-faceted approach to improving/ diversifying the ability to scale Rock, including but not limited to:Expediting the .NET CORE Overhaul (a complete overhaul including all CORE pieces)Database architecture options (Postgres...

---

---

---

Adding Pushpay Payment Plans to the Native Integration.

---

Multiple Transports for SMS would allow for a diversified experience / strategy around SMS empowering complex organizations with multiple needs to administer/ manage a holistic SMS approach.

---

Event Registration integration with https://www.brushfire.com/

---