Happy to get criticism, but this sentence was not constructive in any way:
As an iOS dev, swift engineer, and major critic of javascript and other non-native, hacky, pragmatic solutions, using React Native on an app intended for one platform is probably more than a little bit to blame here.
Sorry we don't know Swift, but I assume the same thing could happen in Swift if you started rewriting the entire state management in a Swift app. We chose to write it in React Native because we both know JS/React, but we wanted to focus on iOS because that's what we use. Saying it's partially our fault for not using Swift is not constructive.
Please be more respectful as a fellow dev. We are doing this in our spare time and we don’t know Swift. We are doing this for fun, if you don’t like our hacky JavaScript app you can go use a different app. It doesn’t affect us since we are not making money off of this lol. I’m literally doing this in my spare time for free. This also has ABSOLUTELY nothing to do with JavaScript and react native, it’s our state management.
You are seeing state issues on Memmys side, but i am pretty sure it is not posting on the wrong account (although we could be not updating the current account state correctly anymore). We replaced our state management library so there are bugs with it we need to iron out. You are just seeing something show up that is essentially cached wrong on Memmys side. But if you want something more stable, leave TestFlight and get the App Store app as i believe that one isn’t updated with the state management lib (could be wrong).
We are trying something new and making it a drawer, rather than just copy what Apollo did. We can look into making going back remember if you had the subscriptions open or not though
Happy to get criticism, but this sentence was not constructive in any way:
Sorry we don't know Swift, but I assume the same thing could happen in Swift if you started rewriting the entire state management in a Swift app. We chose to write it in React Native because we both know JS/React, but we wanted to focus on iOS because that's what we use. Saying it's partially our fault for not using Swift is not constructive.