SylviaApr 20, 2024

I really don't understand Lite apps.

Your app is slow and way too big because you never cared about usability on slower devices or saving storage. Clearly you do not have a methodology to develop thoughtfully.

So, instead of starting to clean up your app and ensure more care in the future you... write a second app? Now you have 2 codebases to maintain, effectively doubling the maintenance costs. And if you still have no methodology the Lite app will eventually meet the same fate too.

Why?

Show threadTom
@SylvieLorxu Same core but with removed unnecessary functionalities, that are build like plug-in, it's mainly the same codebase with just a different build configuration.
Apr 20, 2024 at 8:46amWeb
Show threadSylviaApr 20, 2024

@tdelmas Android build flavours would indeed be a somewhat logical way to make a Lite version (although often the "Lite" version is a PWA instead).

Still I would argue in most cases releasing a second version of your app that "removes unnecessary functionality" makes little sense (if almost nobody needs the feature, it shouldn't be there by default).

It also just confuses your users, how will most people know if they want regular or Lite? Or even that Lite exists if the app is slow?

Show threadTomApr 20, 2024
@SylvieLorxu Lite apps do help people with low end devices
Show threadTomApr 20, 2024
@SylvieLorxu The normal app is fast on high end device, but may be too slow on low ones