Just pushed a new update for my Calendar Checker app (. It's just 12 MB less than the median download size 🤣🤣.

Wow, I just pushed the app a few days ago and I've got my first review. It's funny that this tiny app was more fun to develop that using the so called "modern" approach. It has about 300kb and is fully NATIVE. No Google 💩, and because of this it took 1 day to develop 🤣🤣

The Tiny Calendar Checker app is up on the store for FREE ( . It now incresed in download size from 50kb to 319 kb because I added the billing library for donations.

Soon available in store . The size for new installs it's a bit larger than I anticipated :( My target size was 50 KB but I guess ~73 is not that bad either.

The tiny app looks like this. Now it only has 64.1 KiloBytes. The competition is over 9mb, the most popular calendar checker app is at 20mb. I do most of my testing on VERY low end devices! Those app blocks the device and hangs, mine is butter smooth even on my low end device.

I'm preparing a new app to demonstrate exactly what native means for Android. Many "developers" consider that 20-100mb of 💩 for a todo list or a timer app is native. In fact native means you can do the same in 100Kb, with almost zero unnecesary CPU consumption.

RT @SMuresan: Elon Musk tweets daily about Romania. Not because he knows Romania. Not because he cares about Romania. But because he w….

I'm color blind (I can't see the numbers from the first frame) and the only colorblind app for Android doesn't really help me so I made one that makes them visible for me. If other color blind people can give me feedback on the filters it would be useful 😀.

This is the 3rd year I've tried to add Compose to one of my prod apps, and for the third time, I've come to the conclusion that is 💩. Even DataBinding feels like a better choice. I'm 100% sure that Google doesn't actually use it at scale, if they did, it wouldn't be this bad.

Contrary to the popular belief that Android isn't good for indie devs, my ToDo app has been generating revenue in 2024, despite being a simple to-do list app. It seems that users appreciate nice-looking apps that don't require accounts or steal your data😅 Who would have thought?

RT @tobi: Sunday rant. For software engineering, my sense is that the phrase “premature optimization is the root of all evil” has massive….

RT @0xglitchbyte: “You dont need to learn C, I didnt”. Anyone telling you that is limiting you in favor of their ego. Most of the worlds so….

I was sceptical about choosing Flutter for my next app due to Google's reputation to abandon projects but then I checked GWT ( to see if it's still alive and surprise: it's maintained and active to this day. I guess we worry too much about these stuff.

RT @unclebobmartin: There are situations in which TDD is impractical or impossible. They are rare, narrow, and there are mitigation strateg….

I'm trying to decide what tech to use for an app: it needs to work on IOS, Destkop, Android; it should be able to create files, view PDF, Audio, Video, show maps. I'm thinking of Flutter or KMP but can't decide. I have a slight preference but I don't want to influence you.

If Compose offers fast dev speed but sacrifices control and performance, it means it's the quick solution you adopt for fast progress, that may become a hurdle when evolving requirements demand more control or performance. In essence, it embodies the concept of tech debt🤣🤣.

Technical debt is the cost incurred by choosing a quick but limited solution over a better, more time-consuming approach. New libs don't automatically make old code tech debt. High-quality code can stand the test of time without being labelled as technical debt.

As far as I remember the Google Maps on IOS took 6 months to develop including the renderer. If Compose is so superior and decreases dev time with 50% please show me a map component equivalent to the one from IPhone 1 in 3 months. From zero not using views underneath 😊.

RT @arpadietoth: @JimSproch @amrfarid140 @AthorNZ Google already acts as an arbitrary authority, capable of banning apps without a viable a….

The Torvalds-Tannenbaum debate it's a reminder that solving real problems beats theorizing about future ones. Simplicity today trumps complex architecture for tomorrow's maybes. Why choose complexity? All changes become intricate for what? Hypothetical scenarios?.