# July
Welcome back to another update - just one month till the end of summer... I hope you've managed or at least have plans to still manage to enjoy some of this Summer, now that COVID restrictions are easing up.
As mentioned last month, this month is all about fixing and improving current systems - and I plan to continue doing just that for August as well. For the full list, head over to changelog
{% content-ref url="/pages/-LyzPuzyf4eGs0086Fjm" %}
[Changelog](/changelog.md)
{% endcontent-ref %}
## :bug: Bug Fixes
There are a bunch of recent and old bugs that I've been addressing this month, but there is plenty to go, hence my plan to continue squashing them. Below are some of the highlights, but you can find the full list in the Changelog.
New MangaDex API has come with their own share of problems and new challenges that I had to figure out.
* One issue was occurring when trying to set chapters as last read → it wouldn't work if there was a page number in the URL, which has now been fixed.
* Another big issue was due to the new way that MangaDex updates are retrieved, which is a more efficient method, but took a bit of time to figure out. As a result, when integration was updated at first, Kenmei would miss a bunch of updates → but that is now fixed and as far as I know, most updates should be going through without issues.
I've also, at long last, managed to fix **Remember Me not staying set**, so some people would get logged out before 2 months have passed. This is a bug that's been around for awhile now, so I am very happy to get it fixed. Do let me know if you are still having this issue!
## :sparkles: QoL Improvements
There have been a bunch of small Quality of Life improvements that I've worked on this month. From **upgrading servers** to **handling background jobs better** and **cleaning up codebase** in general, to make it easier to manage and improve going forward.
One of the visual improvements you'd see → is an improved icon, when you add the app to your Home Screen. It looked quite ugly before, but now looks like any other app. If you are using Kenmei on mobile, but haven't added it to your home screen, I highly suggest you do so, as it comes with **improved performance** and **ease of use**, just like a regular app would
Another annoying issue that got fixed, has to do with the Title Search, especially on mobile. Check some of the issues as reported by one of the members on our Discord ([do join](https://discord.gg/XeTFtYW), if you haven't already)
All of these issues have now been addressed, so it should be easier to use the search bar on mobile and desktop
Finally, I've increased the speed of polling for new updates. New chapters will now be requested every **15** minutes, instead of every **30** minutes, a **2x speed increase.** As mentioned before, I will continue to decrease the speed, as systems get more mature and smart - the goal is to get to near real-time updates.
## :chart\_with\_upwards\_trend: Progress Overview
After the big releases last month, I continue to mostly focus on bug fixes, improvements of systems and so on. The only big feature I am going to start exploring, is the long requested Manual Chapter selection. But the main focus is still polishing of *all* existing features, instead of bringing out new features.
#### Current focus:
1. Admin control panel
2. QoL improvements across the board (new sorting, filters, etc)
3. Manual Chapter Selection
4. Bug hunting and fixing
5. Migrating remaining UI components to use the new design
Till next time 👋
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://news.kenmei.co/monthly-updates/2021/july.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.