I went into a thread only to find that I had commented on it. My comment was one from an entirely different thread and Memmy somehow mistakenly decided to pulled that comment into that thread.
Sorry guys but Memmy has been unusable since we left version V.0.3.
Apparently, it did post the comment in the right place but it displayed it in the wrong thread just because… it felt like it?
🤷🏻♂️
Unusable? Bit dramatic.
Maybe help and report issues on GitHub if not already done.
I’ve been providing feedback via testflight. Is reporting on github the preferred way?
yes
IMO, not really. If I post something and it ends up being posted from the wrong account, thereby doxxing me (which has happened more times than I can count now), that’s pretty bad in my book. I keep downgrading to version .3 because it’s the last version that tells the truth about who is posting where.
I’d like to see the devs fix these major issues before adding more features…and I know that they’re working on it.
I simply want to browse and know that what I am posting is from the account name that is written in the bottom/middle of the app. At the moment, I can’t even trust Memmy to do that. As it stands, I have to remember to manually reload every tab in the app (or shut the app down and restart it with the user I switched to).
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.Ps. don’t even get me started about battery life, RAM usage, and background behavior of react native apps.
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.
Yeesh, you guys have been working on this app for less than 2 months and already a few of your users have developed a serious sense of entitlement.
Take it as a compliment, you’ve set an insanely high bar with Memmy - both in terms of its current state and the speed at which you made it. Please keep up the good work, and don’t let a few overly dramatic critics ruin it for you. They definitely don’t speak for the majority of your users.
Appreciate it! It’s definitely been an adjustment dealing with public criticism vs just my tech lead asking why all my commits say “wtf” on my last PR lol
I apologize. I hoped/figured you guys could take honest criticism (since it comes from a place of wanting you guys to do better and is completely constructive).
IMO, you currently have the best app for Lemmy. As a fellow dev, I’d want to hear brutally honest opinions of my app no matter how much it hurts…and it should hurt (as much as a dose of reality does) because this app has all the red flags that point to mounting and unmanageable state and complexity. Good luck refactoring it and I promise to also be as unbridled about my praise as I was about my criticism.
In the future, I promise to disguise my harsh criticisms and tech stack preferences so I don’t hurt your feelings.
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.
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.
In my book, that is actually a constructive critique. I am constructively telling you that javascript and react native are bad candidates for this type of thing and that I think it would benefit you long-term to switch to a native tech stack. As long as you didn’t personally invent javascript or react native, you shouldn’t be offended. I guess you could be offended if you simply refuse to learn swift while developing an app built solely for iOS but that’s not on me.
Dude just stop and realize you’re being pretty rude
You’re not being constructive or helpful. You’re coming off very entitled and negative.
If you don’t like the app, make your own. Simple as that
If you don’t want to (or cant) make your own app, let developers make what they want
There’s plenty of Lemmy apps built in SwiftUI, you can use those. But as you admit, Lemmy is the best of the list, and it’s built on a non native app. Go figure.
I bet this dude’s coworkers really love working with him. 😂
For someone that has contributed nothing to any of these projects you sure are an opinionated douche.
You should read the book Radical Candour. It will help you provide critical feedback in a respectful and empathic way. Saying “as a fellow dev…” is not a hall pass to light somebody’s work on fire, crap on their tech stack decisions, and claim your opinion is fact.
Strong opinions are good. I appreciate strong opinions. I have many of my own. And i know you’re excited for this app and that it’s become a daily staple for you so you want it to succeed. But React Native is not a bad technology stack. In its nearly 10 years it has evolved and improved dramatically. Huge apps are written in React Native. I bet you use, or have used, some of them and don’t even know.
Technology is a tool. You can write great software and equally bad software in any language or stack. I’ve used a lot of terrible iOS apps, and I’m sure some of them were written in Swift. A language or tech stack is not inherently bad, and claiming such is not constructive feedback, it’s being an asshole.
Don’t be an asshole.
Hi fellow, you’re actually pretty rude. Even your « I apology » comment is not an apology at all.
As an IOS dev, swift engineer, major critic bla bla bla, you should know that there are more constructive ways of providing feedback.
if you want native Swift UI then use mlem and complain there ✌️
I have been out today, but just saw this. While it looks like this has already died down a bit, I’d just give me two cents as well. No hard feelings about anything though.
First off, like was stated before, the current TestFlight release is - and was admitted to be - a major rewrite or a major portion of the app. In fact, it was performance itself that was a determining factor in the rewrite. As you probably know if you are a dev yourself, things like that don’t come cost-free. As a single person working on that aspect of things, it took a lot of work to tear out things and make them right. And - obviously as we can see here - they are not right. In fact, they are not even complete.
The reason that these builds get pushed to TF is that - again only being myself, Sean, and a few other contributors - it would be impossible to meaningfully conduct QA on the entire app and find these issues. There are issues that I am still unable to reproduce myself that I see people having. This is just part of development, and is something that will always be a part of development. A larger team would have a QA team that builds go through, which we do not have. And even in those cases where big QA teams find all the issues, how often do we see bugs still creeping through the holes? Often!
Now I think the reason that the comment might have been taken offensively was the mention of (and I can see you did end up crossing part of it out) “non-native, hacky, pragmatic solutions”. This is one of those things that we all know lots of people take seriously. In fact, it seems you possible that you are one of those people. I’ve fallen into the trap before too, so I get it. We can definitely get defensive over our work and the tools that we choose to use for that work.
Now, yes, you are right. The issue here might have been that when you changed accounts, things were not reloaded. This is something that must happen because there is zero correlation between post ID 4003 on lemmy.world and post ID 4003 on infosec.pub. And that is something that very well might be broken in the latest TF release (in fact, we know it is broken). And if I were a more dedicated and efficient person, I would have fixed it immediately after finding out and have pushed an update Sunday morning whenever I realized it. However, I am neither of those things and took the day off for myself. But we do know about it, and it will be fixed.
The statement that this is likely to be an issue with the tech stack is just not correct though. Additionally, the claims made here about battery life, memory usage, and “background behavior” are actually irrelevant. I’ll admit there might be higher battery usage with a RN app given the necessity of a bit more work going on, but not substantial on today’s devices. Memory usage is something that I have personally checked, and the app rarely uses over 120MB of memory (usually far less) and this is mainly due to images (I do believe that CPU might be one thing that is higher on RN in most cases, but memory seems to actually be about the same if not less).
A majority of the issues that people have (rightfully) had with RN over the past are the lack of native navigation (which is no longer the case in React Navigation 6), non-native animations (no longer an issue especially with Reanimated 3.x) and the native bridge requirement (this is being resolved now with the new architecture and the rolling out of Fabric). And while I do not admit to being the most knowledgeable RN dev (we are definitely learning with the process), I am certain that none of these performance issues are directly linked to React Native but rather something that we ourselves are doing.
And the claim that the stack itself is the reason for those issues is simply fascinating given the fact that not only other Lemmy apps I see being developed with Swift have performance issues in some places but most big-name apps I see these days have those same issues is telling of something. Not that the stack itself is causing issues, but that performance issues are something that happen and are dealt with. No one can blame any of the devs of any apps for these issues and I have seen all of them continually improve on them. I have been nothing but impressed by the Mlem team who’s app on the first day I downloaded it was - to be frank - pretty hard to use. Now, it has grown into quite something indeed and performance is quickly being addressed.
Lastly, perhaps you were unaware but the intention originally was to make an app that worked on both platforms. However, once it was seen that a number of fine apps were coming to the platform, we decided it would be best to focus on iOS. It is what we use, and what we care about the most.
Regardless, I am not offended by anything here and I am in fact someone who almost certainly not going to be learning Swift anytime soon. That is not because I have anything against Swift (I don’t have the same belief about the vast degree of superiority that it might have) but because I actually believe React Native to be a wonderful framework and I am intent on learning more about that itself. And while it certainly is not my reason for doing so (I do have quite a lot more experience with Javascript than either Swift or Java/Kotlin and that is the main reason), I am pretty sure that the continued growth, development, and real world use of React Native speaks for itself in terms of whether or not it is a viable solution for mobile app development.
Just my two cents. No hard feelings here.
you sound like a colossal douche
deleted by creator
Yea this is an issue with our state management, but it’s not actually posting the comment to that thread. Just essentially displaying a “cached” comment before we load the new comments of the new post.
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).
Thanks. I simply downgraded to 0.3 again (which is, I think) the last version that went to the App store.
I’ve also had my inbox not respecting marking responses as read for the last 3 days. I currently have 4 random messages that won’t go away.
Same. If you use the open envelope in the top right hand corner that should clear it.
Thanks. Seems to have worked, but sad the problem exists at all. ☹️
Edit: Glad the beta version is pulled and they’re getting ahead of it!
I’ve had messages displayed in the wrong thread on Lemmy in general. I don’t think this is a Memmy issue, but a Lemmy issue.
Sorry but it is ABSOLUTELY a Memmy issue.
You don’t have to apologize to me - I’m just saying I’ve seen this issue on the web browser too.
It must’ve happened on the same instance or something because I have never seen that. If it helps the devs, I should mention that I have an identical account on 6 different instances (which has turned out to be a good move since instances seem to go down as often as the sun rises).
It’s actually very likely not
Why?
I’ve never had a problem with this posting from my Lemmy.world account
Want to know where I did have issues? With my infosec.pub backup account
