Why so many people are quitting Android development

• Flow

  2 2,792 0.0 Java

  Name UI states, navigate between them, remember where you've been. (by square)

  

So obviously it didn't get popular. Mortar was buggy, [Flow]((https://github.com/square/flow) was unstable, neither of them were particularly well-documented (you were expected to read the source code to know what it's about, but most people didn't know at the time how to do that), it was a mess.

• flow-sample

  1 1 10.0 Java

  Flow-Sample by Square

square/Flow however was "not API stable" (ever) and had 4 various forms over 2 years ending in inevitable deprecation, and the only documentation was a sample that people didn't really understand. Namely, this sample.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• mortar

  1 2,161 0.0 Java

  A simple library that makes it easy to pair thin views with dedicated controllers, isolated from most of the vagaries of the Activity life cycle. (by square)

  

So obviously it didn't get popular. Mortar was buggy, [Flow]((https://github.com/square/flow) was unstable, neither of them were particularly well-documented (you were expected to read the source code to know what it's about, but most people didn't know at the time how to do that), it was a mess.

• simple-stack

  40 1,353 5.8 Java

  [ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).

As someone who had been using single-activity since 2015 (a'la Flow) and eventually just rewrote the whole thing to fix all the bugs we had with it in 2017, I find it sad that the single-activity approach was questioned not because it was harder, but because people made their own lives harder. And then Google made their lives harder.

Suggest a related project