Best course of action so far in my opinion as we want minimal additional work for you while you’re building a path away from the current working ecosystem. Let’s not dedicate too much time to Google’s bullshit (should I say BS? B*****?) before we actually have to.
Yeah, unless there is a significant listener base who exclusively was using this app and has no other option, I’d encourage focusing on other priorities.
Are there stats for active users of the app?
I’ve changed our Google Play Store target audience to be 18+ and up:
The target age group for your app is: 18 and over
I’ve put up a change that will make any requests
stream-app makes to https://resonate.is will open in the user’s browser, and not the app. This should make Google be okay with the donations page, as it will no longer be “in-app”. This will only affect Android users, iOS users will still be able to navigate to resonate.is pages.
These should hopefully address these two issues:
Fingers crossed that these two quick fixes appease Google Play Store. The new app bundle has been submitted to them and is currently pending their review.
Can I get some updated (and succinct) copy on the needs as it relates to progress on the mobile app that I can share through various channels in order to solicit more volunteer dev help?
I think the move to a new framework as expressed bellow is currently in a very rough state because @piper and @psi won’t be able to really do the work until the 1st week of August (could be until the 8th of August, maybe slightly earlier). So we might want to wait then to do a proper call for developpers but I’ll leave that judgement call to Piper and Psi.
Furthermore, as it stands, Piper, Psi and @jeremy do not currently have access to the Resonate server which is limiting to do the work they need to do and we’re waiting on @auggod and @peter to walk them through the process of having complete access to all the resources they need, which I think should be sorted before early August so that they can start right back on it when they’re back.
Until then I think this sums up the needs succintly for now
Note that all I’ve mentionned above was just a short summary of what’s been discussed and decided collectively at the dev stand up meeting two days ago in the presence of @brndnkng and @Hakanto as well ! Hope this helps !
Also incidentally @jeremy just posted this which is I think the single most important document about how to further proceed with Resonate dev work :
@jeremy has this proposal which @psi and I think is a great next step - we’d like outside devs to weigh in on it and potentially get involved in helping with that if the proposal is approved. We had an awesome Dev Standup Meeting last Wednesday with brandon and Peter H and a bunch of others on the call that was really productive when we discussed this and the current blockers, and we collectively decided on the call that it was time for @jeremy to post his proposal publicly.
Maybe something like the following would work for a succinct social media post to attract more devs:
Resonate has a new tech-related proposal on the floor (Some proposals to improve product development at Resonate) to consolidate and simplify its back-end infrastructure. We would like to invite devs to provide initial feedback on the proposal, and to get involved and assist in this work.
@zetto.plus, let me know what you think about all of this (I know this is a lot to chew on). Thank you so much for your efforts and your continued pushing to do socials and to bring more devs on board (which we definitely, desperately need).
In other news, @relish and other Android users, Google has reinstated
stream-app in the Google Play Store! Give it a whirl and let me know if you run into any issues, but it looks like we’re back up and running from what I can tell over here.
Mobile App Update - Release v1.1.9 / 19
Because the forum now lives at https://community.resonate.coop (part of 🚧 Warning: Resonate Infrastructure In Flux Coming Week(s?) (effective immediately)), I’ve created a new release of
stream-app to allow users to continue to navigate and use the community forum in-app, instead of it automatically opening in the user’s browser. For those who don’t know, you can scroll to the bottom footer (or even quicker, press in the top right, click Settings, and because it’s a shorter page you can get to the bottom quicker) and press
Forum - you can actually browse the forum using the app! I like doing this because it provides a bit more screen space (no browser URL bar at the top) and a more focused experience.
These new builds have been submitted to Google Play Store and Apple App Store, and are currently being reviewed - should be live sometime tomorrow.
Thank you @piper for pursuing this app so diligently and keeping the community in the loop via the Forum.
Minor note: I’ve updated the topic above as well as the
stream-app’s Readme file regarding its development status - initially I stated that development on the repository would be discontinued in favor of the
mobile repository, but I’ve since realized that’s an incorrect characterization - it’s essentially in maintenance mode (we will continue to fix bugs as they arise and fix problems where possible). The repository is essentially as feature complete as it can be within the confines of the
react-native-webview library, so new features aren’t really possible without switching to regular
react-native (the goal of the
Just wanted to post this clarifying update/edit to make sure people are aware that we’re still currently supporting and maintaining the
mobile (our long-term goal) is being built out.
Please disable smooth scrolling. Feels like scrolling to a point where I didn’t intention it to be scrolled to.
I’ve responded on the issue, but I’ll copy paste my response here as well:
I’m guessing you’re on Android? What version?
At first glance, I would have though this issue pertains:
However, we are not using
androidHardwareAccelerationDisabled, which was causing the problem for the users in that issue.
This app uses your phone’s default browser, so if you have a way of disabling smooth scrolling in your phone’s default browser, that would probably fix this issue. I don’t have an Android myself so I’ve never run into this bug nor do I have a way to test it.
In the meantime, I will try to experiment with bumping the
react-native-webview version to the latest to see if that solves that for you. Here is the latest release, version
20 on Android (
1.2.0 for iOS). It has been submitted to the Google Play Store and Apple Stores for review, and will be available publicly after they are past review:
|Library||Previous Version||New Version|
Thank you for reporting this issue!
I‘m on iOS
@pabloscloud, 1.2.0 is now live on Apple Store TestFlight, if you want to test and let me know if those updated packages fix your issue:
I noticed on GitHub that you said you’re on iOS 16.0 which is due to be released this fall (in beta). Sounds like this could be because you’re on an iOS beta release instead of a stable version? When you open stream.resonate.coop in Safari, do you have the same issue?
@pabloscloud New release here, should be available for testing via TestFlight sometime today after it’s been reviewed by Apple: Release 1.2.1 · peterklingelhofer/stream-app · GitHub
- Use default
decelerationRateproperty for iOS browsers
(normal) , rather than WebView default (
Crossing my fingers this fixes your issue.
Hi, I got the app update last night and was asked to take a screenshot and send it to the dev, so here it is
Awesome, @Sylvia, thank you for posting this!
The new login associated with our migration off of Wordpress routes us through a new URL (https://id.resonate.coop) for login in the player, I’m adding that new URL to our list of allowed in-app URLs, so users can once again log in in
stream-app. I’m submitting the new release to app stores, pending review people from Google/Apple, the update should be available in the next 4-48 hours to everyone (it’s available immediately for those able to install binaries on their mobile devices here).
Delighted to share that the “Learn” menu dropdown being non-functional for iOS is FIXED on the production server! To be clear, this fixes the menu and allows full functionality for mobile/iPad iOS users in all browsers and for iOS
We’ve also been pushing out a bunch of other fixes for the player (which also fix things for the mobile app) just to handle things associated with the transition off of WordPress. Special thanks to @auggod and @psi for all of their hard work on this.
You’re wonderful, I’ll give this a try when I can.
A couple of updates:
- Allowed iOS users to use the Learn dropdown on the ID server, anytime a user visits any page on https://id.resonate.coop on iOS, be it in the stream-app or their mobile browser, the “Learn” dropdown should now work as intended.
- Made some headway on the Resonate’s new mobile app - we can now play/pause, skip, rewind through tracks on a test playlist on the new mobile app (not yet available in app stores). This is still very preliminary (UI will change a great deal) but this is really exciting. Because we won’t be bound to the web player’s functionality anymore, we’ll be able to do fancy things like push notifications on new music releases (if the user wants them) and other similar things that can probably really boost community engagement.