If you’re responsible for delivery of a .NET application and your users have analytics requirements, you have some decisions to make. Having your development team “roll its own” analytics functionality will almost certainly result in a costly project that’s obsolete before it launches. Meanwhile, SQL Server Reporting Services hasn’t been updated since 2010, and its browser compatibility is limited. Report Builder takes users out of your application and, worse, out of its context. Should you set users up with a standalone data discovery tool? Have them use Power BI and its myriad add-ins for Excel?
If none of these traditional options seem ideal to you, you’re not alone, and there is a better option: embedded business intelligence. While several Embedded BI solutions exist, many just place an IFRAME in your app, which isn’t secure or seamless and may not retain your branding.
This is a critical issue if you are building multi-tenant SaaS applications hosted in Microsoft Azure, AWS or other public cloud infrastructure. Embedded BI lets users go beyond static or view-only reporting, making users fluent with their data and passionate about exploring this data without leaving your application.
WHAT WILL BE DISCUSSED:
- Why embedded BI gets more user adoption
- Why Multi-Tenant Cloud Applications Now Require Embedded BI
- Creating dashboards that aren’t shelfware
- Why an integration API beats an IFRAME
- The pitfalls of desktop clients
WHO SHOULD WATCH:
- COOs and CTOs
- Product Managers
- Development Managers and Architects
- Developers building analytics or BI
- Business Analysts