I admittedly didn’t read the article. Is that the reason or does someone already have an app called X? Either way they can just call it like “X - Formerly known as Twitter” but he’s probably too childish to do that.

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.

Oh nothing happened. I have an account on .ml that I usually use but it’s been acting super slow all day long. Just something us refugees have to deal with 🦾

There are some options for font size, font weight, etc. inside of the settings.

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.

Makes me feel better that I’m not the only one who had this oversight 😅

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!

There are a few things that are a bit harder to do with RN given a bit of easy access to APIs, but you can always make modules to interface with native code. For one, this little image thing I used is just pulled from a library. It’s a bit iffy, and I am writing a replacement for that now. Same with markdown rendering.

As far as the UI itself, it gets pretty close to what you’d see with a native UI, if not exact. But I certainly do understand why from a dev standpoint you’d like to use SwiftUI, it’s great!

If there’s anything that you’d like to see in the UI though let me know!

Fixed that in the latest release. Sorry about that…

Those are some of the main reasons. Also, the fact that it can be easily released as an Android build as well is nice, especially for users who would want a more Apollo-like feel on android devices. I have not personally tested Jeroba, but from screenshots I have seen (while it does look great!) it doesn’t have the same look as some of the old Reddit apps.

Bottom line is this is a huge preference thing. I don’t want to take anything at all away from Mlem. If you know Swift and think you can contribute to that project then by all means you should! Looks like a great project. Glad that there’s so many people working on things for Lemmy already!

Yup. I took it for a spin on a simulator and things are about 90% functional out of the box. There’s some weird scaling issues with the text, but I believe that to be the patchwork way I’m rendering the markdown right now. Once I finish the markdown parser it should be the same across both platforms.