We are getting there as well - 100% of our user pages are Skuid (detail pages and tabs) and we have partial on Home pages. Nothing on reports or dashboards, although most skuid object tabs have an Analytics tab we created so they can dynamically create reports / charts to see what they want. We haven’t had good user adoption of Salesforce reports and dashboards anyways. There are just too many limitations, and the users get confused by seeing all the fields on the object and don’t understand which field (which price field??) is the one they want in their report. So they don’t even attempt to build their own, and they call us. And we build them a Skuid report (most of the time.)
We have not replaced the SF header / search in our org.
We do have a full SF community (customer plus and partner, custom domain - no SF or Skuid url references) completely built in Skuid. We are a manufacturer (we make fiber optic cable and components sold to customers like Electric companies, Telecom providers, guys like Amazon/google/facebook) and our customers use our community to look up their order status and shipment info, invoices (like an amazon account). We’ve just released a fully Skuidified Content area in our community which meant getting into the sausage making of the Salesforce CRM content area. It was tricky but do-able once you understand the library - version - document relationships, and we build a cool search screen to replicate the sorta-ok one that Salesforce has on their native content tab. Our internal view of Content is still native SF. It just hasn’t floated up as super important to build a Skuid version right now. Our community is fully skinned - Skuid header and search, incorporates the Logout function (just a url) and the user has no idea they are in Salesforce.
We have also replaced emailing using Skuid actions, (still using either Apex templates or standard SF templates.)
For us, we are completely bought in and won’t build a single new feature without using Skuid.
