2 Edit: Ok back up as .79

Edit: Expired .78 because of a super annoying keyboard autofocus on the traverse page. Releasing .79 in about 5 minutes.

Hey all! Here are this version's changes:

• Fix infinite spinning on profile page
• Images that also have a post body now show both
• Fixed duplicate NSFW setting
• Keyboard for search now includes "@" for easy access
• Sign in/sign up screens now include "." for easy access as well
• Onboarding screen should render correctly on all devices
• You can save posts now. They will be synced with your Lemmy account. You can view them on your profile page
• All of your subscriptions will now show up and you can search through them. Also a more attractive and easy way to access them
• Default Active search was added to settings
• Settings was moved to profile. We will revisit this if it's a user issue (i.e. people can't find it, you guys don't like it, etc.)
• Issue with communities having an "infinite render" are fixed

We're getting there!

Happy scrolling!

Hey all!

Here are today's updates:

• Crashes are fixed for:
  • Subscriptions
  • Community Blocks
  • Other notifications that had a "toast" popup
• You can now edit comments by pressing the "..." in the post view. I'll finish post edit tomorrow.
• There is a whole new onboarding process for new users. If you want to give it a spin, just reinstall Memmy and check it out. I'll have some screenshots below as well.
• You can toggle when your messages will be marked as read (thanks to https://github.com/ktgd)
• Posts that are stuck to the community or local will now show as such (thanks to https://github.com/qoopa)
• You can toggle a setting now to allow images to take up the full height of the screen in the feed view (instead of being downsized to fit)
• Other bug fixes

Onboarding

As we prepare for an App Store release today, we hope that these types of changes help to make it easier to get people to figure out registration. If you have ideas on how we can make this easier, please let us know!

Hey all. I want to do two things in this post. I'll get the first one out of the way real quick.

Community Rules

While I appreciate all the support and fun, I'd like for us to not attack or belittle, or make fun of any of the other apps or developers that are being made. Even if a comment could be interpreted as doing so, I'd rather us not share that content.

This obviously cannot be controlled by me outside of this community, but I'd like to emphasize that I think we should follow this behavior as a Lemmy community. There may be features of Memmy that are superior right now to those in other apps, and I am certain there are features in other apps that are superior to those in Memmy. The thing that matters is we are all working toward making a more accessible, friendly, and fun way to access Lemmy, and that is something that will help this community grow.

There's a reason that there were multiple successful iOS and Android apps for Reddit. There's a reason that even with an official Mastodon app, there are other apps that interact with Mastodon as well. No single developer can create THE app that will appeal to every user. I can't do that, nor can anyone else. So let's keep the spirit up for all the devs and work on this as a team.

With that said, here are some ground rules.

Rules

1. Be polite.
2. Don't start drama or anything that could be perceived as starting drama.
3. Don't trash talk, belittle, or joke about the work of other developers. This doesn't mean you can't say "I like this feature in X better than in Y". That's fine. But let's not start with "lol I had to delete that app it was garbage, idk wtf they are doing over there..."
4. Try to stay in-scope. Everything so far has been fine. Keep all the feature requests and bug info coming (although bug reports should mainly be posted to GitHub as it is much easier to view and triage there)

I might update this if I think of anything else, but that's pretty much it. I'm also not saying that anyone DID do anything like this, but I saw some content that could have been PERCEIVED as such.

Roadmap

We are looking at an MVP release to the App Store being submitted before the 1st. It will be either tomorrow or day after tomorrow. I am not sure how long it will take for review, but I'd give it a range of 12 hours (unlikely) to two days (maybe even longer).

After this MVP gets released, we will start implementing community feature requests. All of the posts you guys are making here and on GitHub are not going unread. We will figure out which ones we need to prioritize, which ones we want to prioritize, and which ones can be pushed back. We will release a detailed roadmap of this soon.

We have fixed all of the issues with crashes and that update will be released within the next day on TestFlight. We have also done the following:

1. Revamped the community/subscriptions screen
2. Created an interactive onboarding process for new users who don't know about Lemmy. It will help with picking an instance, give you details about the instances you can join, etc. Full .18.1 captcha support.
3. Cleaned up some more theme issues and UI issues.
4. Added editing of posts/comments

I think this is enough to give us an MVP for release. At the very least, I want to get something to Apple that they can put through the initial review process so that we can make sure we are fully compliant with their rules.

Hey all!

Edit 2: Well that was cool:

Looks like I hit a stray key before building...resubmitting now as version 0.0.1.75

Edit: Update released.

Going to be pushing an update here in a few hours with the following changes:

• The issue where tapping a post in your profile would cause a crash is fixed. We were getting ready to fix up profiles and this happened...sorry
• Profile page is now available for any user. Just tap their name in the feed or search.
• You can now swipe on an item in your inbox to mark it as unread. Still need to finish up mentions and messages, but I'll have that done tomorrow.
• Additional themes and a better way to select them. I'll get system default added either tomorrow or day after that.
• Other bug fixes under the hood

Let me know what all needs working on still and we will get it fixed up! Happy scrolling!

On a side note, I want to ask the following of everyone:

If you are having issues subscribing to communities (crash), please let me know the instance you are on and the community you are trying to subscribe to. I'm really curious to know what is going on there, as I am 100% unable to reproduce this issue but obviously it's happening to a lot of you.

There has not been any significant change to the subscription logic which makes me think that this might have something to do with something going on with a certain instance, but I cannot be sure. I am also curious if this is something that happened with the latest update to .18 and the use of the .18 API and API client inside of Memmy. There appears to be proper error handling here in this logic, so I am not sure what might be causing that crash.

Thanks!

Hey all!

As always, thank you for being a tester. Because of your efforts in reporting, things are continually improving and we are finding new issues to patch up.

Before I explain, I just want you to know that this is not a rant or anything. It has nothing to do from any feedback from you guys, but something I wanted to clear up ahead of time, especially going into the fairly soon release of a stable build on the App Store.

I just wanted to give a quick explanation of how Sean and I are using TestFlight. I'm not sure how other apps are handling this, but my current use and future plan is to use TestFlight for "hot off the press" builds. That does not mean that no testing has gone into them, but it does mean that the testing will have been limited.

Were we a big team, we would send things through QA before releasing whether to TestFlight or for production to the App Store. However, we are not, and it is primarily only two people contributing to the actual codebase. We are extremely grateful to the people who are submitting PRs with improvements and fixes however, and would love for that to continue.

With that said, TestFlight will continue to be for hot releases. Things might break, things might improve. And you guys, the community, are that QA team. There's no way we could get this sort of feedback or anything without you guys, and we are grateful for that. I just don't want you all to feel that we are throwing bugs at you for no reason.

Once a stable build is released on the App Store, I'd love for some of you to stick around with us in TestFlight to continue doing what you are doing. Builds to TestFlight will likely become more frequent rather than less with a proper CI/CD pipeline will be established to release new version tags on Git directly to TestFlight.

I also want to make sure that all of you know that regardless of whether you receive a response or not, your issues are seen and are being addressed. I think it goes without saying that this community has grown extremely fast. To go from having zero users to nearing 10000 in less than two weeks is a difficult task to juggle, especially when dealing with a brand new codebase, a brand new API, and all the while attempting to integrate and push at lightning fast speeds.

Thankfully we are starting to get to a point where integrations do not need to be made as fast (most necessary features are now implemented), so there is going to be way more smoothing out the edges coming up now.

Thanks as always for your help and understanding!

Hey all, this is an update that includes a lot of fixes before the next visual release. Here are the changes that were made:

• Compact mode now features thumbnails for URLs
• Adds a clear option to the search bar
• Adjustable thumbnail in compact mode and the ability to disable the vote icons in compact mode (thanks to https://github.com/qoopa for this)
• Image animation was tweaked again for your convenience, but it will be reworked here in the near future to act more like Apollo
• Posts are now marked as read whenever you view them. They will be grayed out in your feed once they are marked as read. Thanks for the help from https://github.com/ktgd
• You can now select the intensity of haptic feedback (thanks to https://github.com/yrahul3910)
• There is a font slider to adjust the text size to your liking. No more glasses!
• Issues where people couldn't post in communities becuase of a language issue are now fixed.
• Comment and post votes now update when you make a vote
• Upvote icons and other post action icons are now animated
• A very terrible animation for comments (I added it in for testing and have not removed it yet. This will be completed in the next update)

This resolves the bulk of bugs that were causing people issues. The next update will be mostly visual changes.

Thanks guys!

Just a test.

Don't PUSH me, cause I'm close to the edge!

Hey all!

First, for those concerned, I have a multi-day vacation coming up here this week, so I'll be taking a nice break and cooking up a new batch of meth for the next spree (I kid I kid).

Here's the updates for the day for you:

• You can delete accounts now.
• Themes have been tweaked
• Push notifications - Available in Edit Account Settings
• Swipe co.....wait did you say push notifications? Yea, we'll talk about that down below.
• Swipe colors are theme-based now. Will continue tweaking these as needed.
• Other tweaks
• Oh and compact view users can now press the image to open it up.

Issues I know about and will address tomorrow:

• Voting on comments doesn't update the vote
• Going to a user profile is not yet complete. Don't worry, most of this should be done tomorrow. I've got pretty much all the designs laid out and components now made for them. Just a matter of swapping out the old with the new :)

Push Notifications

I've set up a server that will perform checks for push notifications. Here are the ground rules you should know about:

1. I cannot guarantee the availability of this. As we scale, I will scale as well, so it won't be a problem with that. What I mean is that I cannot guarantee what Lemmy instances are going to do as far as rate limiting (I'm not 100% sure how it works yet). Although I am not spamming any requests at all (you're going to be making more requests for notifications just by having the website open), there will obviously be multiple users making requests from the same IP address now. Depending on what instances owners have in place, some requests might fail to go through. I'll monitor and see what happens.

2. Before you enable notifications, a message will appear letting you know that you are sending your authentication token to the Memmy server. This is NOT your password, HOWEVER, it does allow Memmy (and anyone who has access to it) access to your account. So, long story short, you are trusting me (and only me, nobody else has access to this server) with access to your Lemmy account.

This is not optimal. I would much rather have scopes where all I can do is READ your mentions/replies/etc, and this might be something that gets integrated later on in the API. We will see what happens with that in the future. For now though, there is only one scope of authentication.

If you do wish to revoke this token in the future for whatever reason, all you need to do is change your password and the token will be invalidated.

Again...you are infact sending your authentication token to the server and I technically do have access to it. Just as a heads up.

3. Here is how it works:

• You enable push notifications in the app

• Your username, instance, auth token, and push notifications token are sent to https://memmy.app

• The server attempts to access the Lemmy API endpoint /site. When authenticated, this endpoint returns user information.

• The server checks that the username in the API response matches the one sent to the server. If it does not, then either the authentication token was invalid or the username was not correct.

• If everything is correct, the server stores the username, instance, authentication token, and push token in the database.

• The server will check for replies (currently this is all I am checking for as to not create too much traffic) periodically. This should happen once per minute, but as users increase, there may be delays as I scale.

• The server will get the latest reply ID and see if it is greater than the last one received. If so, this is a new reply and it will be sent to the user. That reply ID will then be stored in the database.

• Subsequent devices are also supported. Notifications will be sent to each device.

4. Full source code is available to view at https://github.com/gkasdorf/memmy-push

5. To instance admins: All requests made to instances include the user-agent "Memmy Push/0.1 on behalf of username". The username is included to inform you that these are not requests made for one specific individual, but for multiple users. If this ever becomes a problem on your instance, please let me know as I would really like to make this work great for everyone, not just the users. This is a team effort.

On that note, please also let me know if you see any trouble with traffic coming from the app. Similarly, requests are made with the user-agent "Memmy ios version".

Feedback

Let me know what issues you have with this feature. Obviously it is new and I'm not sure how great it works yet. From my testing it works fine. I will slowly expand on the notifications delivered from this, however, I first want to make sure we approach this slowly so that we do not create an absurd amount of traffic that cannot be handled. I will closely monitor traffic and adjust timeframes if necessary.

The next update will include mostly visual and UI changes as we move toward normalizing the entire design of the app and bring about a great UX for all of you.

I'm also aware of a number of issues, and don't think they are unnoticed. Now that we have all the features in place, we can go through and fix every last one of these issues 👍

And lastly on that note, thanks for your guy's debug logs. We are now reaching a point where we are seeing on average 1 crash per 1000 sessions and debug logs are coming in quite less frequently than before. All good news :)

See you in the next update. Till then, happy pushing!

This is only the first update for today. It includes mostly bug fixes but a few visual features as well:

• Subscribe button now updates after subscribe/unsubscribe
• More adjustments to font size. Trying to get this right sorry…
• Keyboards should ALL use the correct theme
• Actions sheets also should ALL use the correct theme
• Comments rework:

1. Should fix ALL issues where the profile feed would show duplicate comments
2. Should fix ALL issues where the inbox showed duplicate comments
3. Should fix ALL issues where pressing a comment in either of the above might take you to the wrong spot
4. Should fix ALL issues where replies don’t show up
5. Note this is a big change in the logic, so if you run into issues please let me know ASAP so I can resolve them.

• Dracula theme and Dracula purple theme added. Thanks to Sean for this as well as https://github.com/daltonlicause for his color additions.
• Other themes should be much better now, sorry for the dark mode update from yesterday. On that note, I’ll get a REAL OLED theme written up.
• Also on the theme note, I will be creating a theme.readme as well as a post on /c/[email protected] about how you can contribute your own themes to the project.
• Landing page looks much better now, thanks to https://github.com/ntoporcov. I hope he continues to support the project and make some great changes for you guys. Sorry, I am not generally a frontend developer and as such don’t have the touch for design like some of these amazing people do.
• Thanks to Sean again for working on these themes. He went through and made the necessary changes to let the community do their own theming.

The update coming next will include many features. Like I told you yesterday, you’ll be in for a treat. I’ll see you guys in that update. Until then, happy scrolling!