iOS/Android Wrapper

[JorenC]

Apparently, we would be able to release the app to iOS stores, as the 'app functionality' condition is sufficed even by a web-app, as per Primacy trying and succeeding.

Considering the app is made in React, it shouldn't be too hard to create an iOS wrapper around the app, there are multiple solutions. One such is Apache Cordova (https://fjolt.com/article/react-apache-cordova-ios-android) which is open source and backed by Apache, so should be good.

As I gather from the tutorial page linked, it allows us to migrate our app into one solution, where a router will detect whether the app runs on web or in the iOS/Android wrapper, allowing one source code to be maintained.

There are notification plugins that handle notifications into both Android and iOS (although some plugins seem to be outdated, but Cordova contains its own solution (https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-dialogs/index.html), but my L337 coding skills are not sufficient to judge this, and I don't know how notifications are routed (Firebase, I believe, then this solution might work: https://medium.com/@carlospcpro/how-to-add-push-notifications-to-your-cordova-app-in-ios-and-android-using-firebase-done-right-4f6c64dc50f0).

@zond maybe you can take an evening to investigate and see if this would be a workable solution - I would be able to foot the development costs for iOS development if necessary.

[zond]

I think this solution is simpler than using React native, and it should let us use iOS notifications. Definitely a practical way to do it, if someone wants to contribute some time to try it out :D

Perhaps something @johnpooch would want to try out instead of React Native for a simpler alternative? WDYT @johnpooch?

[johnpooch]

Hey guys yeah this looks like it should be pretty straight forward. Longer term I reckon using react native would be better because this approach seems experimental and I can imagine us having weird bugs that only occur in the app emulation set up. I think using native code would make for a better user experience. My only concern would be that by releasing an experimental version of the app we could gather some negative reviews if it felt like it wasn't a real app or something. Could be a good stop gap. Alternatively we could wait and try to make a proper native experience. I'm easy 😊 happy to try smash this out and we can see how it performs

[JorenC]

We can always start with the free Dev account, test whether it works, then release in batches/closed beta right?

…

On Mon, 16 Aug 2021, 14:46 John McDowell, ***@***.***> wrote: Hey guys yeah this looks like it should be pretty straight forward. Longer term I reckon using react native would be better because this approach seems experimental and I can imagine us having weird bugs that only occur in the app emulation set up. I think using native code would make for a better user experience. My only concern would be that by releasing an experimental version of the app we could gather some negative reviews if it felt like it wasn't a real app or something. Could be a good stop gap. Alternatively we could wait and try to make a proper native experience. I'm easy 😊 happy to try smash this out and we can see how it performs — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#255 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXURGOKJN3OE7XCCQCTWQLT5ECD7ANCNFSM5CDF3PMA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[zond]

That sounds like it could work :)

[JorenC]

As Primacy has proven it's doable, let me know when you want me to get an Apple Dev account... hint hint