On the open-source side, the honest answer is that the app is the easy part and push is the hard part. Linphone is the main open-source client on all four platforms, and its push story is Flexisip, their open-source SIP proxy/push gateway. You'd run Flexisip in front of FusionPBX, rebuild the app under your own name, and register your own Apple (APNs/PushKit) and Google (FCM) credentials so the pushes come from your app. It's doable, but you're signing up to maintain the push gateway, the certificates and the app store builds yourself, and iOS is strict: since iOS 13 every VoIP push has to show a CallKit call straight away, so the app and gateway have to get that right or Apple will start dropping your pushes.
If you go the open-source route, the things that bite people with FusionPBX are ring group timeouts that are too short for a phone that's still waking up (25 to 30 seconds per mobile member is a safer start), and making sure the push gateway, not the sleeping phone, is what holds the registration.
If you'd rather not run the push side yourself, that's what the commercial options do for you. Full disclosure, I work at SessionTalk, and we do a white-label softphone for iOS, Android, Windows and macOS that's published under your own developer accounts, with the push infrastructure run by us and working with FusionPBX as a normal SIP endpoint:
https://sessiontalk.io/whitelabel-sip-branded-mobile-dialer-softphone. We've also written up the different ways to add push to FusionPBX, including the self-hosted route:
https://sessiontalk.io/blog/fusionpbx-push-notifications-softphone-ios-android