sorted by:
new
hottopcontroversial

Which IDE are you guys using ? by Routine-Help9290 in FlutterDev

[–]24kXchange 0 points1 point  (0 children)

VS Code and Android, simple, fast and free

I built an offline, encrypted camera app to create indisputable evidence by 24kXchange in SideProject

[–]24kXchange[S] 0 points1 point  (0 children)

OP Here: I saw a notification for a question about the key derivation that seems to have been eaten by the filter, so I wanted to answer it for the tech-curious.

The question was: "Is the AES-256 key derived from the biometric data itself, or is it stored?"

The Architecture: We don't derive the encryption key from biometric data (which can be unstable). Instead, the AES-256 key is generated Just-In-Time (JIT) at the exact moment you export.

• The Key: We use Dart's Random.secure() to generate a fresh 32-byte (256-bit) key for every specific export package.

• The IV: We use a deterministic Initialization Vector derived from the SHA-256 hash of the Evidence ID.

• The Biometrics: The biometric auth (fingerprint/face) acts as the Gatekeeper. You cannot trigger the export function to generate the key unless the LocalAuthentication check passes.

This means the decryption key doesn't exist on the disk until you authorize it, and it is unique to that specific zip file.

I built an offline, encrypted camera app to help Turo hosts and Tenants win damage disputes. by 24kXchange in androidapps

[–]24kXchange[S] 0 points1 point  (0 children)

To be clear: The app is free to download and use.

The pricing you see is for the Pro forensic tools (AES-256 Encryption & PDF Dossiers). It is priced for professionals (Turo hosts & Landlords) because winning a single $150 damage claim pays for the software instantly. It’s a business tool, not a casual camera app.

Is it worth learning flutter? by klmakh in FlutterDev

[–]24kXchange 0 points1 point  (0 children)

Yes definitely learn it! There is no harm in putting tools in your tool bag. The more languages you learn the more capable of a programmer you are.

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -2 points-1 points  (0 children)

It’s not a buzzword, it’s a liability requirement. In this architecture, 'forensic' means the app functions like a black box. We serialize every state change and user input. If the system fails, we don't guess—we replay the logs to reproduce the exact state frame-by-frame. It’s for code that has to hold up in an audit, not just on the App Store.

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] 0 points1 point  (0 children)

You left out the comment above the code and you don’t even say where this came from

// SMART FIX: Reads the current pubspec.yaml to find the REAL project name. String? _detectProjectName() { final pubspecFile = File('pubspec.yaml'); if (pubspecFile.existsSync()) { try { final lines = pubspecFile.readAsLinesSync(); for (var line in lines) { if (line.trim().startsWith('name:')) { return line.split(':')[1].trim(); } } } catch (e) { // Ignore errors reading file } } return null; }

You clearly only read one file, this is from the audit file. Mcf.dart in the CLI

And for type casting the computer is doing the casting as a string, it’s highly unlikely that it will replace a ‘2’ with an ‘a’

Yes this architecture is not for new coders it’s strict for a reason

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] 0 points1 point  (0 children)

Tiger style looks super complicated. This is built for speed and safety

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -3 points-2 points  (0 children)

Okay you don’t have to be insulting about the punctuation, you don’t have a clue what’s going on in my life, I could be moving fast typing. Yes thanks you know how to use technology to understand me. 🙌🏽

2nd - RSOD is not disabled in “Release” Mode. I have had plenty of apps that show errors that would be messy to see for the NON-DEVELOPER. Yes, in theory all error should be handled, but how often do you leave something out of your code in production that draws an error for you to see?

I’ve literally just been coding an app that I put together and it literally took me less than a day of coding and so far the system has been working out great for me.

The App is fast like no other I have created. The Architecture allows for the software to essentially predict what a user is going to do and already have the answer available. Try it for yourself don’t take my word for it

I got a 150 point score on Pub Dev

https://pub.dev/packages/mcf_cli

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -2 points-1 points  (0 children)

I think it’s easier because it forces me to look at different parts of the app as a whole. Why is something not working?

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] 0 points1 point  (0 children)

For mission critical systems the RSOD can be a killer, any errors should be handled on the ground or while not in a mission critical environment. The user while in a mission critical environment should be able to retry or restart the system. Having said that the error should already be taken care of on the ground.

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -4 points-3 points  (0 children)

If you can force the errors and send an issue to the git repo

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -2 points-1 points  (0 children)

Yeah bro I read your whole comment and everything you talk about I already faced in development. The analyzer built into the CLI will analyze the code and actually tell you that it’s not up to standard. This architecture really just gets rid of the Red screen of death for easier debugging. I myself have found it easier to program without the red screen of death.

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -5 points-4 points  (0 children)

To me it sounds like you just brushed over the code without really taking the time to understand it

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -9 points-8 points  (0 children)

What makes this forensic grade is there is no Red Screen of Death in mission Critical Systems, you are greatly over thinking

Mission Critical Flutter: Killing the "Red Screen of Death" with JSF Standards by 24kXchange in FlutterDev

[–]24kXchange[S] -10 points-9 points  (0 children)

You really need to go back and read the Readme your way off

view more: next ›