What JD Learned Building the Content Assistant App: A Product Manager’s Journey

1. Why Write This Article

The author, who joined JD in May 2019 and worked on live streaming, video, topics, and other content products, shares the many challenges and pitfalls encountered while building JD’s content ecosystem, hoping the story can inspire others.

2. Why a Content Assistant

Initially the goal was a simple mobile app comparable to the Taobao Live app, offering JD creators a dedicated broadcasting tool. Research showed Taobao’s app focused only on the broadcaster side, so JD aimed to combine both B‑side (broadcaster) and C‑side (consumer) functions in one app.

Following JD’s fast‑execution culture, the team collaborated on login, order flow, notifications, and complaint systems, emphasizing a reliable version manager to avoid common pitfalls.

3. Starting with Login – Don’t Assume

The first version copied JD’s login suite (phone, WeChat, SMS, password, JD‑App joint login) assuming it was the best solution, but users complained because many broadcasters used PC‑based accounts not tied to their phone numbers, leading to incorrect logins.

After user research, the team realized the need for a traditional password field and optional one‑click methods, illustrating the importance of standing firm on user‑centered design.

4. Live Streaming – Simplify, Don’t Force Decisions

The app introduced a one‑click “copy live room” feature, allowing broadcasters to quickly duplicate settings and launch new rooms, which was well received.

However, an automatic mirror‑flip of product close‑ups caused many complaints; the team later gave broadcasters the choice to enable or disable mirroring, reinforcing that users should retain control.

5. Video – Align Audit Status Across Platforms

Discrepancies between mobile and PC audit statuses caused missing drafts; the team unified the two audit fields (public and private) and added clear prompts when only private approval was granted.

They also set a 60‑second upload limit to balance publishing efficiency with user experience.

6. Single‑Product Creation – Avoid Unnecessary Features

Adding a mobile single‑product editor without proper research led to low output and high image‑processing costs; the lesson was to conduct thorough research before extending functionality.

7. Selection Tool – Break Free from Legacy Constraints

To help creators pick products on mobile, the team ported the PC selection tool, adjusting UI to show secondary product pools and adding filters, while compromising on some backend constraints.

Different content types (live, video, single‑product) require tailored selection experiences.

8. Privacy & Compliance – A Recurrent Necessity

Regulatory notices demand updates to privacy policies, SDK inventories, permission requests, and complaint channels; the app must not collect personal data before consent, avoid frequent auto‑starts, and provide clear account‑deletion pathways.

9. Release Work – Balancing Product and Project Roles

The product lead also acted as version manager, establishing a three‑week release cycle, handling iOS/Android submissions, and navigating app‑store certification requirements, including documentation and legal assets.

Release announcements, in‑app update prompts, and coordination with operations were essential for user adoption.

Conclusion

The author reflects on the unique challenges of product work within JD’s e‑commerce ecosystem, emphasizing incremental iteration, data‑driven decisions, and confidence in one’s ideas as keys to successful product development.