next generation mobile🎉

[johannesjo]

@jiongxuan I thought it might be good to have separate place to discuss things related to the new mobile releases. Just wanted to keep you in the loop :)

So far all seems to work fine and I will start roling out the app to everyone. 🎉

[jiongxuan]

Thanks for the update and the separate discussion space! Looking forward to the rollout. Let me know if there’s anything I can assist with! 🙌

[johannesjo]

Hey @jiongxuan ! I have question! To make all cors problems go away on android (which would allow Jira and webdav work without a hassle) it would be great if we could also handle POST requests and other requests with a payload. Do you see a good way to implement such a feature? One approach I found was to manually send the request bodies over via javascript (e.g. by patching a prototype), but that doesn't feel to clean. Do you see a better way to implement something like this?

[jiongxuan]

@johannesjo I should note that my experience with pure H5/JS projects is somewhat limited. I’ve worked on them but don’t have extensive expertise, so apologies if I miss something here.

To clarify, have you already encountered a situation where CORS becomes unusable after an Android update? I haven’t been able to reproduce this issue on my end so far. If you’ve encountered it, could you please share the steps or specific configurations to reproduce the problem? That would help a lot in understanding the situation better.

[johannesjo]

Hey @jiongxuan ! I just wanted to reach out to ask, if all is well with you!?

I hope I didn't bother you too much with my many requests. I totally understand if it became a little too much. If that is the case, I am very sorry for that. Working on something like Super Productivity should be fun and not feel like work!

If you ever feel like reaching out to talk more privately, please feel free to send me a mail to [email protected] anytime!!!
(maybe give me a heads up here, since stuff lands in the spam folder quite often...)

All the best to you and thank you once more for your exceptionally awesome contributions!!

[jiongxuan]

@johannesjo Thanks for checking in! Work has been super busy lately, so I haven’t had much time for Super Productivity, but I’m still very excited about the project and the issues we discussed. I’ll do my best to take a look soon! 😄

No worries about the requests—I’ve always enjoyed contributing, and your support makes it even better.

I’ll drop you a heads-up if I email you to avoid the spam folder. Thanks again for reaching out! 🤝

[johannesjo]

Alright! I am happy to hear that! I totally understand that work comes first! I Great to have you on board! :)

[jiongxuan]

If we’re talking about building the next generation of mobile app, iOS support is definitely something we can’t ignore (and perhaps even Harmony Next in the future). With Capacitor now in the mix, it feels like there’s a more practical path forward for iOS as well.

That said, iOS does come with its own challenges, especially being a more closed ecosystem. Things like developer accounts, recurring fees, and other Apple-specific requirements might add overhead. I’m curious—what’s your take on these considerations?

[johannesjo]

Personally I hate publishing to apple 😄! In my experience it has been so finicky and gathering lots of special and otherwise useless knowledge was required. But we'll make it work, I am sure!

In general I think our approach should be to keep things as simple as possible for us (at least in the beginning) and maybe start with a very basic version maybe without all the adjustments the android version has. We could also disable features on iOS that would require more work. With more iOS developers starting to use the app, quality should improve over time.

Would creating a first draft for iOS be something, you'd be interested in working on?

[jiongxuan]

I completely agree with your approach—starting simple makes a lot of sense. For example, we could skip things like notifications or background services for now and focus on just getting the app up and running. As the user base grows and more feedback comes in, we can look into refining and adding those features over time.

As for interest—do you remember my earlier questions about the iOS version? (johannesjo/super-productivity-ios#1) I was already considering the idea back then. That said, since my expertise is more on the Android side, I didn’t dive deeper. If you’re up for handling the App Store deployment, I’d be happy to put some time into building the first draft for iOS. Just a heads-up, though—work has been really hectic lately, so it might take me a little while. Apologies in advance for the delay!

[ghost]

Disclaimer: I am really new to programming, and I am totally clueless about many things, so my apologies for any errors.

I noticed that the Android version is written with Kotlin. So, can't we kinda migrate it to KMM? That way, we can share the code between IOS and Android. Also, we can have a jar version so people with out of support operation systems like Windows 7 can use it too. (#3677)

[johannesjo]

Just a heads-up, though—work has been really hectic lately, so it might take me a little while. Apologies in advance for the delay!

No worries! Work comes first :) Thank you very much for the offer!

Maybe I also find some time to dabble a bit with the iOS release over the coming holidays, but I am not sure since there are two other more complex features I'd like to implement first (reworking how issue providers are integrated and a due date for tasks). I let you know if I do so.

@inattentive-nerd thanks for the suggestion, however KMM won't really help us, since we already have an approach with capacitorjs that is better suited to the web heavy code base.

[johannesjo]

Hey @jiongxuan ! How are you doing? :)

I was wondering if you could help out with a subject I am have been struggling with for quite some while now. It's about circumventing CORS issues on android, which would much improve any issue provider and calendar support and might make also syncing via webdav work better. Main problem is that we currently can't handle any request that has a request body attached to it due to the limitations of shouldInterceptRequest().

I was wondering if it would be a good idea to include this third party lib to improve on the situation:
https://github.com/acsbendi/Android-Request-Inspector-WebView

It would be great to have your input on this, since you are so much more experienced with android development!