Ouff, guess I set the cache limit to 512GB instead of 512MB, mbđ Can add a manual cache clear as well
@lemm.ee
Wow, that's crazy, thanks for letting me know.
The app should only be using background refresh to finish image downloads (so like if you're at 98% downloaded and close the app it still works), but looks like something went really wrong here. Probably got stuck in a loop trying to download a missing image all night or something.
Definitely, I've implemented a few swipe actions already, but they're still a bit buggy so I need to rework the gestures before it's ready to release.
Edit: The latest release now has customizable swipe gestures!
IMO the most important thing by far is making the core app experience as solid as possible. Things like post feeds, comment sections, posting, sharing, image viewers, inboxes, replying, editing, text selection, user profiles, swipe gestures, searching, font settings, sorting options, display options, hiding read posts and everything else you'd expect takes a lot of time to develop, maintain and polish. The vast majority of my development time is spent on improvements, bug fixes and new features for everyone, and I really do care a lot about creating a great experience that can help improving Lemmy overall. Offering some more niche nice-to-have features on top of that is a good way to support everything else.
I'm not going to add a higher tier - as I briefly mentioned in an earlier comment my goal is rather the opposite. If Lemmy keeps growing, Avelon Pro could at some point make sense as a $5-or-something one-time upgrade. Unfortunately that's just not the case right now.
Yeah, this is exactly right. I was brainstorming names and came up with Avelon - turns out I was actually just remembering the name of the british legend just slightly wrong. Read up on it a bit more, and figured an "island" away from the big social media giants could be a nice metaphor to use in a Lemmy app name. Ended up keeping Avelon (with an E) since I thought it sounded pretty cool and was more unique.
Hi, sorry for the late (and long) reply. You're right, $30 is definitely a lot to be asking for an app. I'll try to explain where I'm coming from, and why I've landed on this price & monetization model. If anyone have any suggestions on how I can improve things while considering my points as well I'm definitely open to discuss.
But this app is paywalling basic stuff like a comment jump button (everyone else has this for free), content filtering, video scrubbing
When I was working on this update I spent a lot of time considering which features were "essential" and which features were more convenience/nice-to-have features. Two of the bigger features I've decided should be free are multiple accounts & post creation, both of which have been paid features in other apps. I thought everyone having access to these was way more important than app themes or a smart jump button.
Everything that was free in the last version is still free, and of course there's a bunch of new non-pro stuff too. My intent with this update was not to paywall "basic" features, but to offer more hardcore users some extra niceties that in turn support development. I don't expect the majority of people to upgrade, which is totally fine. I'll still keep improving the app for everyone regardless.
make it a reasonable one time purchase for things that donât cost you money (under $10 imo, $5 wouldâve been an easy sell). If you want to justify a subscription model you are gonna need to build features that justify it
I get that the lifetime price is high, I really do. The #1 reason I'm going for this type of subscription model is that Lemmy is so small. Apps like Apollo easily had tens of thousands of users and could therefore charge way way less. For some context - if every single active Avelon user paid for a $5 upgrade, which I'm sure you'd agree is unreasonable, that'd still be barely enough to finance one month of development. That's it. I'm not saying this justifies the price, but Lemmy is still very niche, and with such a niche market the development cost will naturally be spread among much fewer users. With the slow growth of the Lemmy userbase a one-time purchase is very risky from my perspective, and I want Avelon to make sense over a long period of time. I think the devs of both sync (which is $99) and Bean (which is $50) realized this too.
I do believe Avelon can continue to play a part in lowering the barrier of entry to Lemmy and improving the platform as a whole by pushing for more high quality apps. I hope to see Lemmy continue to become the best link-aggregator platform ever, and as that happens prices will naturally decrease.
Thank you! I've got some pretty cool nice-to-have features in the works to make Avelon do everything I miss from the Apollo days. My current plan is to release these as an optional Pro upgrade as a way to support development. All the crucial stuff will be free since I really want to see Lemmy succeed. The upgrade will be mainly for people wanting a little extra to spice up their Lemmy experience & support development
I posted a reply to your post about that, its a bug with an accessibility setting in iOS. Forgot to include the fix in 1.0.7, but you can resolve it for now by disabling "Button Shapes" in the iOS accessibility settings.
And for you running the latest update, check out these link previews:
I really want this too actually, but I honestly have no idea how Apollo did this. Might have to write the whole iOS-navigation-UI-stuff from scratch which is a bit much. I considered adding a floating back button of some kind - not quite the same, but better with a broken wrist hopefully.
Hi, thanks for reporting this bug. My phone doesn't freeze, but the post caused the app to crash yeah. Uploading a build that fixes the problem now.
For anyone interested in dev stuff, this issue was caused by an infinite loop in the regex replace function in swift. A part of my comment processing code fixes a few markdown issues where people often place an image inline that should actually be a big regular image. I forgot a single character in the regex that in some very rare circumstances (like the post you mentioned) caused the matcher to create another string that also matched, which is then replaced again, and again and again and again. Regex is great.
thanks for using Leebra!
go to feed...