CRUD2CRUD common interface for web and desktop lead toward pure data services. Programmers consume CRUD2CRUD data services without implementing concrete clients. For example in Web Services, WSDL explains SOAP client requirements, and specialized clients are implemented against each web service for program integrations, in case of CRUD2CRUD communication architecture such specialized clients are not required.
Common interface lead programmers focus on data definitions, service setups and client integrations rather writing individual API clients for each service.
CRUD2CRUD is data architecture with intent communication. Developers focus on data either working with CRUD (CRUD2) client or a CRUD (2CRUD) service. CRUD2 client is data centric and source neutral, similarly 2CRUD service is data centric and client neutral.
In such an elaborated data architecture communication APIs become standard, and data required is published for integration by both clients and services. There is no need of writing specialized clients against each service and publish their APIs.