Skip to content
AppDues
Log in
Contact salesSign up

droidcon Berlin 2023: Booth, Meetings, and the BillingClient 5 Paywall Talk

This page looks back at a mid-2023 conference announcement from a subscription tooling company: a week in Berlin combining two co-located events, droidcon Berlin and Fluttercon, with a small number of in-person developer meetings. It covers what was scheduled, the argument made in the BillingClient 5 paywall talk, and the migration takeaway for Android teams still running older Google Play Billing Library versions. Treat everything here as a record of announced plans at the time, not as an offer of meetings, booths, or giveaways today.

What the Berlin visit involved

The announced window was July 3–7, 2023, spanning both the Fluttercon and droidcon Berlin conferences along with as many developer meetings as the team could fit around them. Monday July 3 and Tuesday July 4 were reserved for one-to-one sessions with developers in the city; the plan was to bring technical and app-growth specialists who could give on-the-spot feedback and hear likes, dislikes, and feature requests. Across the conference days the team intended to staff a booth in the main sponsor area, aimed at Android and Flutter developers, including subscription-growth topics. The giveaways described in the announcement were Android-themed socks and cat-droid pins.

The BillingClient 5 paywall talk

The headline session was titled “The joys and challenges of building a paywall with BillingClient 5,” scheduled for July 5 at 15:20 in the Lamarr Room. Its argument: the flexibility BillingClient 5 offers enables new paywall configurations and functionality, illustrated with working examples attendees could implement themselves. The speaker also planned to cover the challenges encountered while upgrading the company's own library to support those changes — relevant to Android apps still on PBL4 or PBL3. The stated context was that migration away from Google Play Billing Library 4 was approaching, with PBL5 or PBL6 as the destination, and that migrating sooner carried advantages.

A migration decision checklist

Use this to decide how urgently to act on the talk's premise:

  • Confirm which Google Play Billing Library version your app currently ships. If it is PBL3 or PBL4, you are in the group the talk addressed.
  • Check the current Google Play deprecation timeline for your version before scheduling work — the July 2023 framing predates any later changes.
  • Identify which paywall configurations you want that your current library version cannot express; that gap is the concrete case for moving to BillingClient 5.
  • Budget for library-upgrade friction, not just paywall design. The talk explicitly paired the flexibility gains with upgrade challenges.
  • Prototype against the working examples from the session before committing to a full migration.

This checklist restates the talk's stated reasoning; it is not a substitute for the current official Google Play policy.

Two different problems, often confused

Readers sometimes treat “BillingClient 5 gives you more paywall options” and “upgrading to BillingClient 5 is hard” as contradictory. They are not. The first is a capability statement about what the library exposes; the second is an engineering-cost statement about what it takes to adopt those capabilities inside an existing codebase and SDK wrapper. A team can gain the flexibility and still spend real effort on the upgrade. Planning should account for both.

If you were not in Berlin

Berlin was one stop on a wider announced travel schedule that also named New York, Logroño, San Francisco, and London. For teams that could not attend in person, the practical follow-up is the Billing Library 5 overview and the Android subscription-testing guide referenced alongside the talk.

Frequently asked questions

When was the Berlin visit scheduled?

July 3–7, 2023, spanning the Fluttercon and droidcon Berlin conferences, with July 3 and 4 set aside for developer meetings.

What was the BillingClient 5 talk about?

It covered how BillingClient 5's flexibility enables new paywall configurations, with working examples, plus the challenges of upgrading the company's library to support those changes — aimed at apps still on PBL4 or PBL3.

Where was the booth?

In the main sponsor area of the conference.