Developing a digital product. What it is and how
summary
Claims that experience is the product and that the tech stack must be a business-modeled, open public platform that leverages network effects. Recommends a business API facade (REST/GraphQL), event streaming (RabbitMQ/Kafka/Kinesis), a NoSQL cache for fast object reads, lambda-style integrations, multi-tenancy, strong auth/authorization and continuous feedback loops. Describes applying these pieces at Creditas to expose product functionality, onboard partners, and personalize with ML — platform built and running in production.
AI-written summary · about
chapters (6)
- 0:00Start
- 16:10start with the connection between the physical and digital world
- 23:48know about your customer in its entirety from the beginning
- 33:03leverage content management systems for configuration
- 45:13embed feedback inside your experience
- 46:46collecting the feedback of the customer experience with our product
related talks
36mApplying Product Thinking to internal infrastructure
30mConsumer APIs Must be Product-Driven
44mPlatform Engineering is All About Product
47mBuilding software products distilled: customer value, engineering and delivery
33mWhy You Should Treat Your Platform as a Product
44mPlatform as a Product: A Deep Dive into the Technical Foundations
24mSignificance of Platforms in Product Development
54mDeveloper experience platforms