Take product building very seriously. All of this learning will be of use only if you apply it right away on building some product.
Building software products today requires a clear understanding of the technology choices and development methodologies that shape product delivery. Your actual job as a product manager is to guide decisions on what to build and how to organize the work so that the product meets user needs and scales effectively.
This lesson grounds you in the practical distinctions between app development approaches — native apps, hybrid apps, and PWAs — and how Agile and Scrum practices fit into the product development lifecycle. You will also learn to envision a future-proof system architecture that supports modular growth, data-driven decision-making, and continuous improvement.
The evolution from native apps to web apps and PWAs
The mobile app landscape has evolved significantly. Native apps are built specifically for Android or iOS, using platform-specific languages and tools. Hybrid apps combine web technologies with native wrappers to run across platforms, but they often compromise on performance or user experience.
Progressive Web Apps (PWAs) are a newer approach. They are web applications that behave like native apps — responsive, fast, and capable of offline use — but run in the browser without requiring installation from an app store. PWAs can be accessed directly via a URL and can be added to the home screen, blurring the line between web and native.
Product team discussion on app strategy
You (PM): “We need to decide if we build a native app or a PWA for our next release. What are the trade-offs?”
Tech Lead: “Native apps offer better performance and access to device features, but require separate codebases for Android and iOS.”
Design Lead: “PWAs are easier to maintain and update, and users can access them instantly without installation.”
You (PM): “How do our users typically access our product? Are they on low-end devices or limited data connections?”
Product Analyst: “A significant portion are on budget smartphones and unstable networks, especially in Tier 2 and 3 cities.”
You (PM): “Then PWAs might be a better fit to reach them quickly with a good experience.”
Choosing the right app platform affects reach, performance, and development cost.
The trap many teams fall into is confusing PWAs with hybrid apps. A hybrid app uses a native wrapper to run web code inside a native shell and is distributed via app stores. PWAs are purely web-based but use modern web APIs to offer app-like experiences without installation or app store friction.
In India, where many users have limited storage and intermittent connectivity, PWAs are gaining traction. Companies like Flipkart and Ola have invested in PWAs to provide fast, reliable access without forcing app downloads.
Agile and Scrum in product development
Agile methodologies and Scrum practices are central to modern product development. As a PM, you don't write code, but you must align the team and processes to deliver value iteratively and respond to change.
Agile emphasizes collaboration, flexibility, and continuous improvement. Scrum is a framework within Agile that organizes work into sprints — fixed-length iterations, usually two weeks, with defined ceremonies:
- Sprint Planning: The team commits to a set of backlog items to complete in the sprint.
- Daily Standups: Short daily meetings to synchronize and surface blockers.
- Sprint Review: A demo of completed work to stakeholders for feedback.
- Sprint Retrospective: A meeting to reflect on the sprint and identify improvements.
Your role includes:
- Ensuring user stories are well-defined and ready for development.
- Prioritizing the product backlog based on value and dependencies.
- Collaborating closely with engineering, design, QA, and data teams.
- Tracking releases and validating work against acceptance criteria.
Agile is not just a process but a mindset. The trap is to treat it as a rigid checklist or documentation exercise. Agile demands continuous learning and adaptation.
Designing a future-proof system architecture
As your product grows, the architecture must support scalability, maintainability, and integration with other systems. A microservices architecture breaks the product into loosely coupled services, each owning a specific business capability. This modularity enables independent development, deployment, and scaling.
APIs (Application Programming Interfaces) enable interoperability between services and with external systems. Well-designed APIs allow your product to integrate with partners, extend functionality, and support new channels.
Data architecture is critical for enabling data-driven decision-making. Collecting, storing, and processing data efficiently allows you to build predictive analytics, personalization, and human-centered design features.
Outline a redesign of a platform you are familiar with, focusing on future-proofing it for the next 5 years:
- Define a microservices architecture that breaks down the system into modular components.
- Describe the necessary APIs to enable interoperability within and outside the system.
- Design a data architecture that supports data-driven decision-making and predictive analytics.
- Incorporate Agile and Scrum principles to enhance development flexibility and team collaboration.
Produce a document summarizing this architecture vision.
Test yourself: Choosing the right app approach
You are the PM at a Series A Indian startup building a consumer fintech app targeting Tier 2 and Tier 3 cities. The engineering team proposes building a native Android app first, followed by iOS. The marketing team suggests launching a PWA to reach users faster. Budget and time are constrained.
The call: Which app development approach do you prioritize and why? How do you communicate this decision to engineering and marketing?
Your reasoning:
You are the PM at a Series A Indian startup building a consumer fintech app targeting Tier 2 and Tier 3 cities. The engineering team proposes building a native Android app first, followed by iOS. The marketing team suggests launching a PWA to reach users faster. Budget and time are constrained.
Your task: Which app development approach do you prioritize and why? How do you communicate this decision to engineering and marketing?
your reasoning:
Application example: Agile and microservices in HR management tools
Consider the "Attendance Tracking Tool" project. The team designed it as a microservices-based system with integrated APIs to allow modular growth. This approach enabled seamless integration with existing HR management systems used by clients.
The product team focused on incorporating data-driven user feedback, enabling continuous improvement of the system design. Agile and Scrum methodologies were applied to facilitate collaboration between product, engineering, and QA, ensuring rapid iteration and delivery.
This example illustrates the importance of aligning architecture decisions with product goals and development practices.
The trap of ignoring technology in product management
Many PMs focus exclusively on user needs and overlook the technical implications of their decisions. The trap is thinking technology choices are solely the engineering team's responsibility.
As a PM, you must understand the trade-offs between native apps, hybrid apps, and PWAs; the impact of Agile and Scrum on delivery cadence; and how system architecture affects scalability and user experience.
Ignoring these leads to unrealistic roadmaps, technical debt, and missed market opportunities.
Where to go next
- If you want to deepen your Agile and Scrum knowledge: Agile and Scrum Essentials
- If you want to master product discovery and user research: User Research Methods
- If you want to build scalable product architectures: System Design for PMs
- If you want to improve your stakeholder communication: Stakeholder Management