datetimepicker VS mattermost-mobile

I want user to be able to set a date and time, which led me to install https://github.com/react-native-datetimepicker/datetimepicker. Ive tried following the instructions but when I press the button to open the picker I get this error: "Invariant Violation: requireNativeComponent: "RNDateTimePicker" was not found in the UIManager.".

DatePickerAndroid has been merged with DatePickerIOS and will be removed in a future release. It can now be installed and imported from '@react-native-community/datetimepicker' instead of 'react-native'. See https://github.com/react-native-datetimepicker/datetimepicker'

As mentioned, we used the factors discussed above to assess several React Native date picker libraries, and React-Native DateTimePicker stood out from the pack. It is the most popular, has the most downloads, and was created and is maintained by the React Native community—the same group that builds and maintains most popular packages in the React Native ecosystem.

Expo is just https://github.com/react-native-datetimepicker/datetimepicker which is just the system datepicker.

Literally "going" with them this time, since their server is written in Go (I apologize for my hurtful sense of humor). During Hacktoberfest, I worked on their mobile app, which is written in TypeScript using React Native. However, the issue I got this time was related to their server, and this would be my first time working on a Go project.

Mattermost Mobile - mattermost/mattermost-mobile#8278

Another week (and a few more days) has gone by. While my work on the mattermost mobile app (#8260, #8278) is still on hold, I turned my attention back to Tiling Shell, as the maintainer finally reached out to me on my PR from 2 weeks ago.

After I filed my PR, the first comment I received was regarding the async practice in my code. Only there did I realize the importance. I went into research mode, and turned out it wasn't as difficult as I feared. With the experience from the past months, I was able to comfortably understand it and make the requested changes on the PR.

Mattermost, Inc. | Senior React Native Engineer | REMOTE (US Only) | Full-Time

At Mattermost we build an open core, chat and collaboration platform focused on making users with mission critical work more productive while also allowing our customers to self-deploy and have full control over their own data.

We’re looking for a Senior React Native Engineer who has the depth to significantly move the performance needle of our app while also having the breadth to contribute across our stack.

Check out our open source mobile codebase: https://github.com/mattermost/mattermost-mobile. Meta uses the Mattermost RN app as the benchmark for performance testing of their Hermes JS engine: https://mattermost.com/blog/hermes-mattermost/. Want to set the bar for what a complex, high performing React Native app can do? Want to do it open source? Join our team!

Apply here: https://jobs.lever.co/mattermost/a38ea8f0-6c27-4178-a988-801...

I've got as far as downloading the mattermost apps: https://github.com/mattermost/mattermost-mobile/releases/tag/v2.3.0 and have been using fastlane/match but i haven't been able to build it or run it in xcode.

Mattermost has a few products/versions, i used the selfhosted enterprise version because its also MIT licensed, so free of charge and also very well documented. It may not well suited for business projects, features are build for technical teams/projects. - Features: https://mattermost.com/pricing - Deployment Options: https://mattermost.com/download/#server - Mobile Apps for both worlds: https://github.com/mattermost/mattermost-mobile An other very special app, focused on productmanagement, https://www.documize.com . Never had a scope for to use it in productive, but may match!? :)

Mattermost Beta (version 1.55.1): Secure, self-hosted workplace messaging

This was the first commit on a clean, orphaned branch on our mattermost-mobile repo. This commit kicked off the work on mobile v2. At that time — some of you may not have been born yet (or not yet born into Mattermost — which would include yours truly) — it had become clear a bit of a reset was required. Mobile v1 had grown organically, as many products have, out of a proof-of-concept. Some fundamental design decisions (like only supporting a single server, or how state management works) were foundational limitations and effectively impossible to fix iteratively. A more hard cut had to be made. Not a full rewrite per se, but close. This work kicked off inside of the mobile team, but after about a year also started to include a whole slew of engineers across the organization, as well as product and UX.