Menu

I replaced 4 discontinued Flutter packages. Here's what I learned.
πŸ“°

I replaced 4 discontinued Flutter packages. Here's what I learned.

DEV Community: flutterΒ·Awais RehmanΒ·about 3 hours ago
#pllrxK7A
#devtoflutter#devto#dev#packages#discontinued
Reading 0:00
15s threshold

When the Flutter team announced they were discontinuing six first-party

packages (flutter_markdown, palette_generator, flutter_adaptive_scaffold,

flutter_image, ios_platform_images, css_colors), they left the community a

single sentence: "we encourage members of the community to coordinate on

establishing forks."

Six packages. Millions of combined downloads. And no plan.

What I did about it

I didn't set out to maintain replacements. I set out to fix my own problem β€”

I needed markdown rendering after flutter_markdown died. But once I shipped

one replacement and watched the issue threads fill up with "so what do we use

now?", the pattern became obvious: every discontinued package leaves behind

a large, orphaned user base with nowhere to go.

So I built the Prism family β€” 15 pure-Flutter packages, no platform channels,

all six platforms.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.