3

youRant alpha 0.2 - The Notification Update!

https://github.com/yuriKhordal/...

Managed to finish this update JUST in time, literally going away for the deployment tomorrow.

First of all, Yay, with the addition of notifications, it's first **actual** alpha release (until now I considered releases as MVP.

New Features and Changes:
+ Added Caching. Rants and Images are now cached for a certain amount of time speeding up re-opening rants, not needing to load them again.
+ Added automatic retries for the dreaded Slim Application Error! GET requests will now retry up to 5 times before giving up. The error message in the app now also actually says it's a Slim Application Error instead of the previous unclear "Value <html><head><meta..." error.
+ Added devRant avatars in posts and comments, replacing the previous flat-coloured dots, now only actual dots are dots. :P Also replaced the ugly red dot that shows you are logged in with your actual avatar.
+ Added Notifications for mentions, using the RSS feed provided by retoor. They are currently limited, and do not work in the background for some reason. Regardless, when you open the app you will get notifications of all mentions since the last time notifications worked.
+ Added a limited profile page you can open by clicking the username row in a rant or comment. Currently only dispplays user info, but not actual content(rants, comments, upvotes, favories).

Bug Fixes:
* There was a function in a helper class that was accidentally using a feature of a high API level. It was rewritten.

Comments
  • 2
    It is actually pretty usable now, I've beeing using this app for the last few months, and aside from the not being able to open profiles to look at older posts of people(or myself), it is pretty usable.
  • 3
    update detection seems to be broken, it keeps telling me to update on launch. Good work otherwise, thank you!
  • 2
    Saw the same thing w/ the update mention. Otherwise works well on the newest Android 17 beta. Well done.

    > 'There was a function in a helper class that was accidentally using a feature of a high API level. It was rewritten.'

    This is very commendable. Nowadays way too many people are lazy to just go w/ the newest APIs && whatnot, not caring whether the features are actually necessary / being used, which artificially increases the min OS version requirement.
  • 2
    @lorentz Yeah, I accidentally put "v0.2.0-alpha" in the update detection while the version name in the app and in git is "v0.2-alpha" so it sees its version technically "differs" from the latest and concludes "Ah, there's an update"
    (The checker is extremely stupid, "If my version name != github latest version name, there was an update")
  • 2
    @D-4got10-01 I think it supports down to API level 24(Android 7.0)?
  • 2
    @SoldierOfCode Yup. Exactly that. Android >= 7 (API 24). Quite a nice spread.
  • 1
    That's amazing. I have to try it a bit later, I'm having a heavy day.

    Also, you got two kinds of people in the world. Those who deploy, and those who have deployed. Thanks for the gas prices btw :p But we all know the elite only needs a bicycle or race camel.

    The slim application error - You could've used dr.molodetz.nl as backend and that provides an error free api as well. That one fixes issues server-side (the retry logic). It's of course logic to request again when it fails, but never do it concurrently because I have found out that slim error is a memory related issue. It's also impossible to open rants with MANY comments.

    I'm so tired :(.
Add Comment