For sure. Inbox is pretty much the last feature to implement before I go through and do a big overhaul. Getting all of the functions in place ahead of time gives me a good idea of how things need to come together so I can go back through and make things as elegant as possible.
Developer here. I've been looking at the API calls made by the app, and I'll try to give a good example of what is going on:
To be honest, you're probably not going to see a drastic change in API calls right now. The only things that you are calling the API for are:
Load items in the feed
Load post/comments
Load profiles
Submit votes
Submit comments
Submit posts
One initial call at app launch to obtain user info (subscriptions, settings, saved posts, etc, lemmy's API gives you all of this in one call)
This is about the same use that you're going to see in the actual web version.
While there may be upsides and downsides to how they are doing it right now, you can get pretty much all of the info you need through one API call. For example, if I get a post, the response will include most of the user info, most of the community info, and obviously all of the post info, plus more. I don't need to make separate calls to retrieve all of that data.
Same goes for user info. In just one call, I can retrieve all of the information as far as subscriptions, moderated communities, user settings, and more without having to make a separate call for each one.
The issue is going to be mainly just the influx of traffic in general, not the apps themselves from what I can tell.
I'm also including the app's name in the user agent so that if something were to ever become a problem, anyone can reach out and discuss what they are seeing so that it can be corrected.
Edit: I think one of the biggest issues that larger instances may run into is data usage. Nearly all photos that get posted to Lemmy are hosted on particular instances instead of services like Imgur. There's ups and down to both, but in the short term I can see this possibly as being an issue if instances are not being ran on providers who are lenient or provide their data at low costs.
Should have the search done today. I wanted it done yesterday but time got short.
I know that there's a few UI issues, but I have some designs already ready to begin implementing, so things are going to change a lot on that front for the better.
As far as promotion, most definitely will. I still want to make sure that I iron out a bunch of the issues before I do anything major though. However, I do want to aim to have something stable for the 30th of June that can be available on the App Store without TestFlight.
The new designs include buttons for upvoting and downvoting posts on the comment item. This will be enabled/disabled via a setting.
Good call on showing that.
I will definitely be having them auto collapsed at some point here soon.
I'm going to experiment with a better way to select those. In addition, need to have good ways to select for comment sorting and stuff too.
I'll have the edit done soon...