1. Will Toyota at some stage provide a virtual device for testlab?
For
high volume consumer electronics, product validation is always handled
using physical board farms; pre-launch and post-launch.
2. Something to take back to your managers will Toyota require access to Firebase - "personally i think you do, a fine balance between managing your interest whilst protecting user privacy".
I
think the Database choice is dependent on the overall system design.
Personally I would look into ObjectBox, ObjectBox Sync, or create a Rust
shared module (loaded via FFI). For Rust my colleague has open sourced
a Rust crate called Membrane. It auto generates Dart code from Rust
code, zero copy, supports asynchronous green threading, and is *very*
efficient. Synchronous support is nearing completion.
https://github.com/jerel/membrane
ffigen is
another approach for creating Dart code from a C header. It's a basic
solution, involves more Dart work, and not as sophisticated as what you
can do using Membrane.
https://github.com/dart-lang/ffigen
https://github.com/dart-lang/ffigen
gluecodium is also another option HERE is using:
My understanding is that ffigen and gluecodium are not as efficient as the Rust Membrane solution.
3. Before I get much further along I'll need to know what your expectations will be for flutter app developers, we can then in corporate it and build an AGL flutter app baseline policy requirement thing
I
think it's all relative to the system you're integrating into. If you
have a paying customer - they would drive this. If you are targeting
AGL to showcase at trade shows, then you would want to have the best
performance on a given platform. In general good performance on less
hardware is the name of the game. Flutter can outperform QT and
Web/_javascript_ in regards to system RAM and responsiveness, with less
Engineering NRE; if done correctly. It's important to start developing
in-house expertise on a couple of platforms. Understand how they work,
how designs scale/perform, etc. It will help to direct design
decisions. I've seen some really cool products get designed on desktop,
only to fall short on platform hardware (mostly Web/_javascript_).
Desktop and limited resource hardware runtime environments are two
different universes. Your design needs to be stable, and run well on
the lowest limited resource hardware that you plan to market/sell to.
Another important aspect is testing on a loaded system; never trust an
unloaded system to represent the end user experience. So the general
expectation is that AGL Flutter App devs have experience with limited
resource hardware environments.
Cheers,
Joel
_._,_._,_
Links:
You receive all messages sent to this group.
View/Reply Online (#9807) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [list-automotive-discussions82@xxxxxxxxxxx]
_._,_._,_
