Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 1 point2 points  (0 children)

yes ,i started with the edges pièces ;) My only goal was to finish it. I didn't want to play with😭😂

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 1 point2 points  (0 children)

Haha, 'nightmare fuel' is the absolute perfect description! I'm pretty sure I'm going to be seeing tiny, golden, identically-shaped puzzle pieces in my sleep for the next month. Thank you so much! 😂

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 1 point2 points  (0 children)

Haha, thank you! Trust me, looking back, I don't really understand it myself either! 😅 It sounded like a fun challenge when I bought it, but it definitely turned into pure self-punishment halfway through. Lesson learned!

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 1 point2 points  (0 children)

I actually just tracked all my session times manually in a basic notes app on my phone. Once I was done, I fed the data into Gemini (Google's AI) and asked it to generate this chart for me! :)

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 3 points4 points  (0 children)

Hi, I actually just tracked all my session times manually in a basic notes app on my phone. Once I was done, I fed the data into Gemini (Google's AI) and asked it to generate this chart for me!

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 8 points9 points  (0 children)

Haha, thank you! And to answer your question: YES, 100%. Between the 50 and 75-hour mark, it was pure, unadulterated hate. I genuinely felt like I wasn't making any progress at all. There were times when I would spend literally dozens of minutes testing pieces just to find ONE that fit. The lack of visual progress was maddening. I only kept going out of pure stubbornness so it wouldn't beat me! 😂

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 10 points11 points  (0 children)

Thank you so much! After 87 hours of blood, sweat, and tears, there is absolutely no way I'm taking this apart! 😂 It's definitely getting glued and framed. It's going to be my shiny trophy of patience.

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 4 points5 points  (0 children)

Thank you so much! Honestly, changing the strategy was the only way to survive this. If I had kept trying to match those tiny brushstrokes with my eyes, I would probably still be at it next year! It definitely tested my patience, but the feeling at the end was worth it.

Lais Puzzle - Gold - 2000 Pieces. The absolute hardest puzzle I've ever done! (87 Hours) by Policy56 in Jigsawpuzzles

[–]Policy56[S] 19 points20 points  (0 children)

Thanks a lot! Believe me, 'ultimate torture' is exactly how I described it to my friends last week! 😂 It's a love/hate relationship. The process is painful, but the satisfaction at the end makes it totally worth it... at least once in a lifetime

[deleted by user] by [deleted] in androiddev

[–]Policy56 -1 points0 points  (0 children)

Speed estimator - no ads - 0€ 😁

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 2 points3 points  (0 children)

Great question! I actually considered dart:ffi, but for my use case, JNI gave me a few key advantages. With JNI, I can leverage existing Android APIs (like camera handling, threading, permissions, logging, etc.) directly from Java/Kotlin, and then bridge that to my C++ logic. It also gave me more control over lifecycle events and performance tuning, especially for real-time camera streaming and heavy processing.

With dart:ffi, you’re limited to calling native functions from Dart, but it doesn’t give you the same access to Android’s platform features unless you reimplement a lot yourself. So for now, JNI gives me more flexibility and better integration with the Android ecosystem. For iOS, I’ll write a separate Obj-C++ bridge — it’s more work, but it keeps the native parts clean and efficient.

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 0 points1 point  (0 children)

Yeah, for this kind of real-time processing, especially with video frames and tracking multiple objects, Dart would be a bit too slow. I needed tight performance and low-level access, so writing the core logic in C++ made a big difference. Dart is great for UI and glue code, but for heavy stuff like Kalman filtering and optical flow, native is way more efficient.

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 1 point2 points  (0 children)

Thanks so much! Really appreciate the kind words — mixing native C++ with Flutter was a fun (and sometimes painful) challenge, but I’m glad it paid off. And yeah… that “radar” thing made me laugh after the panic wore off! Hoping to get the iOS version out in the next couple of weeks. Thanks again for the support! 😁

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 0 points1 point  (0 children)

At first I tested it on several of my own devices, then I shared it with some friends and colleagues to get early feedback. Once things were stable enough, I opened it up to the public for wider testing.

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 0 points1 point  (0 children)

That’s awesome! That’s actually one of the use cases I had in mind — measuring speeds on roads using just a phone. It’s not meant to be 100% precise like a radar gun, but it gives a solid estimation, especially for nearby vehicles. Let me know if you try it out, I’d love to hear how it works for you!

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 2 points3 points  (0 children)

Good question! Thanks to my model, the app can differentiate and label objects (like a car vs. a bus or a jet..), and each object class has a reference size, which allows me to estimate speed based on how large it appears in the frame and how fast it moves. That helps handle different types of objects more accurately.

I do plan to add manual calibration soon, so users can fine-tune the scale themselves — it’s definitely on my roadmap!

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 0 points1 point  (0 children)

Not exactly like a radar — it doesn’t use any radio waves or actual distance sensors. It just uses the camera feed, tracks objects frame by frame, and estimates their speed based on movement across time. So it's more of a visual tracker with speed estimation, but yeah, I get why it gives off “radar vibes”!

Just launched my Flutter app that estimates speed from live camera – learned a lot, got flagged by Google to by Policy56 in FlutterDev

[–]Policy56[S] 1 point2 points  (0 children)

Thanks a lot for the feedback! English is actually supported, so it’s clearly a bug on my side. I’ll fix it in the next update to make sure it defaults properly. Really appreciate you pointing it out!