Pros:
- Access app can be created within Office 2013 client and pointing to Office 365 or On-Premise site collection
- Can be use two way of authorization (app only permission , app+user permission).
- Can leverage the multi authentication including the OAuth.
- Access App can be created from data sources like SQL , Web Service, Excel and flat files (.txt & CSV)
- App can be saved as "Snapshot" including with data , in order to move the app around all the site collections and tenants.
- Supports the Form kind of operation and compatible with all devices.
- Clear navigation path and multiple app templates available for Look and Feel good.
- Support the Reporting , sorting and filter.
- Can be editable in the Grid View Format (as seen in SharePoint 2013 List)
- Can be used to run the old Access database with all Macro features that gives the business logic implementation.
- built-in search functionalities to search the huge records.
cons:
- Office WebApp must have installed in all WFEs and involved licensing model.
- No option to trigger the SharePoint Workflow or Item level permission.
- Must have SQL 2012 Enterprise edition installed as Access App uses the SQL table behind the scene.
- Access 2010 and Access 2013 app services must be up and running on the Server, Access 2010 services also required for backward compatibilities.
- SharePoint App configuration (DNS Set up) must be installed and configured on the Server as Access App model relies on the SharePoint App mechanism.
- Often crash as it requires relies on the installed Office Web App in SharePoint server.
- Must have the dedicated Site collection for Access app to manage identical app.