Jason, +1
just got a request to add Biometric authentication on Android and iOS. Do you have done this yet ? Am 05.01.20 um 16:12 schrieb Nelson, Michael: > Jason, thanks for making these great points focused on missing features. > Let's also not forget mobile specific bugs that sit unaddressed. > > Mike > > -----Original Message----- > From: Interest <interest-boun...@qt-project.org> On Behalf Of Jason H > Sent: Saturday, January 4, 2020 3:49 PM > To: Lars Knoll <lars.kn...@qt.io>; interestqt-project.org > <interest@qt-project.org> > Subject: [Interest] The Mobile Agenda? > > So it looks like the QtWS 2019 videos are up on YouTube. > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_watch-3Fv-3DYmwAeS-5FojPA&d=DwIGaQ&c=9mghv0deYPYDGP-W745IEdQLV1kHpn4XJRvR6xMRXtA&r=gqkHidFt_OznI1nBLNO0BnY0UT1ILkTMEW_qQQbTmCk&m=udWwVeDC5d8x9i-GGrsUlyzaDh_8l_874S9CaY6DA3g&s=kVDYbsUThHDxyV5SM35vedYZIUsyXduaRGqMScK30PM&e= > "Qt 6 will bring massive improvements to QML and 3D development" > > At time 53:40 Lars is asked a question about mobile, and answers "We will > continue to support them. Was that the answer you were looking for? > (giggles)" - Actually, no it is not. > At 57:00 Lars takes another question about mobile, and responds with a > hesitant "Um, yes..." and continues" We have a lot of ideas... want to make > sure Qt is working nicely on mobile.. things have been moving quickly... have > to catch up there". > Actually the QA segment ended up being bookended by Mobile questions. > > Well I'm glad to hear Lars admit that there is catching up to do, but I take > issue with the claim that things have been moving quickly. The majority of > mobile features that I and others are requesting are not bleeding edge, it is > basic things, like > * NFC on iOS (Available iOS 11, September 19, 2017, 2+y) > * Media keys (volume, play/pause, etc., Since before Qt 5.2) > * Push Notifications (Since before Qt 5.2) > * Display control (Since before Qt 5.2) > * Battery Info (Since before Qt 5.2) > * Vibration/haptics control (Since before Qt 5.2) > * DeviceInfo (model, OS version, hardware enumeration, etc) > * Biometric authentication > * Datatype conversion (Java and ObjC to Qt types and back) > > Many of these are not that hard, the code is known and settled, I've posted > code where I think it helps, but the issue is for every app I make, I have > the friction of adding 8 of my own classes to every project... which is > composed of bout 8 files, and the tome doctoring manifests and plists). The > expense of these classes is over, but these classes that took me days to > create and test in environments where I am not expert. I hack at native > Objective C and Android, and those experiences are troubling. I don't mind > for some really weird feature, but what is being asked for by me and the > community is pretty basic stuff. Objective-C code examples are becoming rarer > as Swift takes over. The experience of using Eclipse or XCode is another > problem itself, as the Qt integration is less than ideal. (Even ignoring > having to use 2 IDEs to code.) > > Mobile (in general) really hasn't advanced in any way that Qt needs to react > to, there's a lot of new biometrics stuff, but really we only need a way to > integrate for authentication. (Fingerprint, FaceID, etc) Also the only thing > I know Android has changed lately is the permission requests, but Qt already > has a helper for that. > > A lot of these needs are tracked at: > https://urldefense.proofpoint.com/v2/url?u=https-3A__bugreports.qt.io_browse_QTBUG-2D74049&d=DwIGaQ&c=9mghv0deYPYDGP-W745IEdQLV1kHpn4XJRvR6xMRXtA&r=gqkHidFt_OznI1nBLNO0BnY0UT1ILkTMEW_qQQbTmCk&m=udWwVeDC5d8x9i-GGrsUlyzaDh_8l_874S9CaY6DA3g&s=Z8qkrPvJrbw_WWF92VSjRB54ItmnT7UUxrEeriWJKXY&e= > which was opened 11 months ago, but there has not been *any* activity, at > least visibly. > > However I have had several mobile support issues serviced and closed, but I > also have a commercial support agreement. > > If you are interested in my current code (that I recently refactored to be > more granular than a monolithic catch-all shim that I had before) I can see > about getting it shared to Qt, at least as inspiration (I don't use D-ptrs > and am not subject to binary compatibility constraints). I think the most > complicated bit on anyone's list is the Push Notifications, as the two > platforms have different message structures. > > So my question to Lars is: > Lars, can we get a better (in terms of: better stated, more attention, > schedule clarity) commitment to mobile in 2020? I think with not a lot of > effort we could get everything of what we are asking for, and then we can get > out of your hair. > > > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.qt-2Dproject.org_listinfo_interest&d=DwIGaQ&c=9mghv0deYPYDGP-W745IEdQLV1kHpn4XJRvR6xMRXtA&r=gqkHidFt_OznI1nBLNO0BnY0UT1ILkTMEW_qQQbTmCk&m=udWwVeDC5d8x9i-GGrsUlyzaDh_8l_874S9CaY6DA3g&s=FTPeFfzPXBpqCgbrFfZh3XPZEBSfpXptennpQBOjwjQ&e= > Please be advised that this email may contain confidential information. If > you are not the intended recipient, please notify us by email by replying to > the sender and delete this message. The sender disclaims that the content of > this email constitutes an offer to enter into, or the acceptance of, any > agreement; provided that the foregoing does not invalidate the binding effect > of any digital or other electronic reproduction of a manual signature that is > included in any attachment. > _______________________________________________ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
