There’s not a lot of reason to hate it if implemented correctly which it very well might not be at first and likely will cause some headaches. Regardless, Apple should also do a better job of telling users the reasons too if they are going to be doing this.

Right now, you fill out a whole bit of information about why your app might use specific private info, but Apple only shows minor information about it to the user. I’d much rather the user know the specific reason I’m using, for example, location instead of just for “App Functionality”. Would make a better user-developer relationship in my opinion and promote good transparency.

Sorry I’m not 100% sure about this, but is it possible to do it with Lemmy in the PWA? If so I’ll add it. Not able to look it up ATM though.

Shouldn’t it look like that?

But lol alright yea that’s bad. I’ll work on it.

You got a Snapchat screenshot? I got…let’s just say it was two older gentlemen having some fun

Hey all. Replying from .world since…well you guys know.

Anyway, thank you for all your support over the past weeks. It’s helped us get to this point.

A word of caution: The build that was released is slightly outdated and there are a few issues that have already been addressed in that build. Unfortunately because you can’t replace the build in review, we were not able to update it as we went through this nearly week-long back and forth with Apple. It required an appeal to get us onto the store.

With that said, I’ll be releasing the final version of 0.0.2 tonight to TestFlight, and will begin build versioning starting at 0.1.0, which will be the next release on the store. I’ll try and have something submitted to them tonight and hopefully it will be reviewed and released within a day or so.

Cheers!

All stuff I’ve got on the todo list. Thanks!

Don’t worry I have your back. We’ll take ‘em together.

You had to be there.

Appreciate your work as always.

Hey, memmy dev here. here’s the link to the test flight

Hey, memmy dev here. here’s the link to the test flight

Hey, memmy dev here. here’s the link to the test flight

Keyboard should use dark theme now in latest release. Let me know if it still doesn’t? As for the theme, I have a few that I’ll add.

memmy dev here. That’s why I’m so excited to see multiple groups working on things! I could never appease everyone with one design, and frankly I find I prefer the one in memmy (well of course right?) over the one that mlem uses. But that’s me coming from using Apollo for Reddit for years. There were quite a few different UIs for Reddit apps as well.

Like I said to someone else, I think that anyone who knows Swift should go over and help out with the Mlem development. They have a great app as well and we all need all the help we can get!

https://lemmy.ml/c/memmy

I plan to support Android too, by the way. It is already about 90% functional, mainly just some styling issues due to a few quirks between iOS and Android rendering. I’ll keep you guys all posted!

Glad to hear it’s working well! Let me know if you run into any issues or have ideas!

Although it should have been fixed to not crash (release was only just pushed though), it does not currently support KBin. I will look into implementing the API and support this. Might be a bit, since it will require actually writing an API wrapper (from what I have seen anyway), but that isn’t too much work. I’ll put it on the list.

Ah I didn’t know about this. I’ll have to see how to get that information and render accordingly. Thanks for letting me know!

Have you checked the TestFlight app for an update?