# Concerns about improvements speed **URL:** \ **Category:** App\ **Created:** [September 18, 2026, 10:32pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547 "2026-09-18T22:32:11Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![SmurfyPanda](https://forum.kurviger.com/user_avatar/forum.kurviger.com/smurfypanda/32/27060_2.png) [@SmurfyPanda](https://forum.kurviger.com/u/SmurfyPanda)\ **Post date:** [September 18, 2026, 10:32pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/1 "2026-09-18T22:32:11Z")
Hello, I quite like Kurviger, however I started to feel that the speed of improvements and upgrades is quite slow. Take this please as a constructive critique. Kurviger is missing a lot of features, and this forum is full of suggestions and requests, some of them years old. They just do not translate to the app in any timely manner. The last meaningful update was over 4 months ago. I would describe the few other features since then as “we’ve put a button here, moved switch there”. I do not believe that for example putting an altitude icon to Android Auto was a huge development effort. Last year the last update was in July and then nothing until January where we received update that shuffled nav UI and added ability to upload POI pictures. This year, I would say only two major updates arrived, but they’re still only half baked. One is the ability to share folders to other users. Finally. But still, it is read only and you can’t even put the shared folder as an overlay. The second is the road closures. Finally. But the first thing everyone wanted is to see the road closures directly on the map without routing. 4 months after release, still not possible. Competition in the moto nav app market is getting stronger, especially lately. Even another update slow poke like Calimoto started to release big and small updates quite faster than before. Not to mention apps like Stegra, where they may not release so many updates, but each of them is absolutely massive. And they write detailed blog post on the new updates and also inform what they’re working on in the next update. This forum is full of people voting and suggesting various features (of various quality of course). Kurviger developers however keep their users in the dark for months at a time on what they’re working on and then they release some minor update. I, and I’m sure many others, would appreciate more clarity on what it is being worked on, at what time can we expect it and overall prioritization of the most requested features. And not just one time. But some regular updates on the progress and heading would be nice and a bit of urgency to release features in time for the next riding season. ---
**Author:** ![Hobbyfahrer](https://forum.kurviger.com/user_avatar/forum.kurviger.com/hobbyfahrer/32/32029_2.png) [@Hobbyfahrer](https://forum.kurviger.com/u/Hobbyfahrer)\ **Post date:** [September 19, 2026, 6:47am UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/2 "2026-09-19T06:47:29Z")
There have actually been far more significant updates and enhancements than you’ve listed here. > [@\[App\] Kurviger App 3.6.X](https://forum.kurviger.com/t/app-kurviger-app-3-6-x/25262): > > We are happy to announce that we released version 3.6.0 of the Kurviger App. This update contains the following changes: Navigation: New navigation UI Navigation: Set UI background and transparency [iOS] CarPlay: Improve behavior for iOS26 [iOS] CarPlay: Improve sizing of elements on the map Cloud: Ability to upload photos to public POIs and personal favorites Cloud: Ability to upload profile picture In order to keep this thread clean, I would like to ask you to provide feedback [in the discus…](https://forum.kurviger.com/c/news-and-updates/release-feedback/73) ---
**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\ **Post date:** [September 20, 2026, 12:03pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/3 "2026-09-20T12:03:20Z")
Thanks for your feedback and I am sorry to hear that you feel this way. When we work on bigger changes we don’t release updates as often, but this simply means there is bigger change to come in the future. We have quite a few changes in our pipeline and hope that we can release them in the coming weeks. I agree that there are still a ton of features we can add to Kurviger - and this will never change I guess. No matter how many features we add, there is still a ton we could add. I think it is very important to understand however, that we don’t measure our success by the number of features we implement. We simply can’t work on every feature at once, so we go step by step. ---
**Author:** ![multinerd](https://forum.kurviger.com/user_avatar/forum.kurviger.com/multinerd/32/21423_2.png) [@multinerd](https://forum.kurviger.com/u/multinerd)\ **Post date:** [September 25, 2026, 5:31pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/4 "2026-09-25T17:31:39Z")
I do agree with your opinion that we would love to see a more insight to the development pipeline. But generally I am cautious with asking tons of new features. I always prefer a mature and reliable product over a overfeatured one. For me robustness and reliability is the first and most important ting when it comes to motorcycle navigation. Every app has its special philosophy and we developers have to take care that we do the things which our clientele likes. But a product must be consistent in UX/UI design to be pleasant to be used. In turn this means that no app can satisfy each and every feaure request users potentially ask for. This would lead to an inconsistent app (because many feature requests are even contradictionary). Long story short: I totally agree with the slow pace of development which you complain about. But if I can choose between slow cycles of well designed and usability tested updates and high paced and unmature updates, I will always, really always opt for the first. I pay for the SW, so I want it to work right out of the box, each and every time. If I were bored and had time to test features and learn all bugs I would opt for a free beta testing account rather. More over, a navigation app is a navigation app after all. Once it is mature enough to deliver exactly this functionality, why should it get quick and huge updates? Ideally a good SW should get asymptotically less feature updates as it is closing in to perfection. Every app has its strengts and weaknesses. Sometimes we forget that we should first learn to really master a piece of SW and work with the features and functions it has. Only if we just cannot live without a feature we should ask for it. If we are jut impossibly be satisfied with the basic concepts of an app, we ought consider using another product. Happy to hear your thoughts. But yes, please let us understand the develop roadmap of kurviger better. ---
**Author:** ![SmurfyPanda](https://forum.kurviger.com/user_avatar/forum.kurviger.com/smurfypanda/32/27060_2.png) [@SmurfyPanda](https://forum.kurviger.com/u/SmurfyPanda)\ **Post date:** [September 26, 2026, 5:57am UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/5 "2026-09-26T05:57:41Z")
Nobody wants unstable product. But no updates do not equal a stable product. And Kurviger is far away from being a mature navigation product. I also pay for it. And since it is a subscription, I would also like to see a direction and continual improvement at a reasonable pace. Especially since I do not invest only money into it, but my time and energy. I’ve spent many hours creating, curating and sorting my rides, I would hope not to redo all that effort in a different app. What troubles me is the significant delays in implementing even the trivial changes. Just few examples: Kurviger implemented road closures - Fantastic - Everybody complains however that it is not shown on the map unless you are directly passing thru it. But Kurviger tries to avoid the closure and does not signal you there is one. So, from user perspective it just does not want to navigate you via a certain point and only after really forcing it, you’ll be allowed to see that it’s because there is closure. - So, the logical solution would be to show the closures on the map the same way as other POI. - The hard part of obtaining and processing the data was done. Great job. But the simple “show road closures on the road” button is missing even 4 months after the introduction of the function. Kurviger implemented folder sharing - Fantastic, although only in “read only” mode. - But you cannot add shared folder as an overlay - Even 5 months after the feature was released, simple adjustment of the filter so I can add an overlay of the folder shared to me is not implemented… I’m not even talking about implementing real features like real offline navigation, location sharing, etc. Currently, the most requested feature on this site is the creation of favorites while navigating. And after 3 years it is still missing. Kurviger was sending “feelers” few months ago about this feature, so I would presume it is close to arriving, yet it is frustrating that such fairly rudimentary thing takes so long to implement. And instead of clarity on what is being worked on, we get “stay tuned” as if these plans are of some strategical importance. ---
**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\ **Post date:** [September 27, 2026, 7:05pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/6 "2026-09-27T19:05:57Z")
> [@SmurfyPanda](#): > > And Kurviger is far away from being a mature navigation product. I am sorry to hear that you feel this way. While I accept your opinion, I’d just like to note that I disagree. While there are things that we can improve, a lot of things work very well and are rock solid for years. > [@SmurfyPanda](#): > > even the trivial changes We are actually looking for a developer, if these things are actually trivial for you, please [apply](https://tti-gmbh-tgu-kurviger.workwise.io/). That said, the things you mentioned are far from trivial. > [@SmurfyPanda](#): > > - Everybody complains however that it is not shown on the map unless you are directly passing thru it. Is that true? Everybody complains about this? Sure, it would be nice addition, no doubt. But to be honest, I mostly care about closures on my route. That is the crucial part. Ever since we added this feature have seen very few road closures. Before I regularly hit them on my rides. I’d like to add that we talk to a lot of our users and ask these things to get a better understanding or priorities. The reason this is not yet implemented is that so far other things are more important our users. It might be different for you personally. I can tell you that we still have this feature on our road map and it will be added in the future. We actually resolved the major technical blocker for this feature and a few other related features. So we are closer to this feature than we were 4 months ago 🙂. > [@SmurfyPanda](#): > > And instead of clarity on what is being worked on, we get “stay tuned” as if these plans are of some strategical importance. Let me be clear, it’s not about strategic importance. I am not a fan of promising something like “this will be done by X” and “this will be done afterwards” etc. and then people are frustrated because priorities changed, things take longer, etc. ---
**Author:** ![t00thl355](https://forum.kurviger.com/user_avatar/forum.kurviger.com/t00thl355/32/27045_2.png) [@t00thl355](https://forum.kurviger.com/u/t00thl355)\ **Post date:** [September 27, 2026, 7:30pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/7 "2026-09-27T19:30:27Z")
> [@SmurfyPanda](#): > > - Everybody complains however that it is not shown on the map unless you are directly passing thru it. But Kurviger tries to avoid the closure and does not signal you there is one. I see it this way: - If the avoidance is switched-off the road closure is shown as a red section (and relevant) - If the avoidance is switched-on, then Kurviger does not show it because it is not on the route (and therefore not relevant) I did not quite grasp what your proposal is. I assume you are not suggesting that all road closures worldwide should be displayed at all times. So what would be the criteria to display the closures? > [@boldtrn](#): > > Ever since we added this feature have seen very few road closures. I have seen 5 today, on a 150km ride home. Not in the app, but the signs on the road. Every time, Kurviger took the correct turn and avoided them as expected (hoped). I did not have to stop anywhere and scratch my head where to go. Good work 👍 > [@boldtrn](#): > > people are frustrated because priorities changed, things take longer, etc. The ones are frustrated about that and the others are frustrated for not knowing if the features you confirmed being on ToDo list are coming anytime soon. People have expectations, even if you do not initiate them directly. Can’t please everyone, I guess. 🙂 ---
**Author:** ![Hampic](https://forum.kurviger.com/user_avatar/forum.kurviger.com/hampic/32/7313_2.png) [@Hampic](https://forum.kurviger.com/u/Hampic)\ **Post date:** [September 27, 2026, 7:43pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/8 "2026-09-27T19:43:15Z")
> [@boldtrn](#): > > Let me be clear, it’s not about strategic importance. I am not a fan of promising something like “this will be done by X” and “this will be done afterwards” etc. That was one of the most ridiculous things at work—constantly dealing with all those targets and deadlines. Without any reason. Kurviger works very well, but I am also impatiently waiting for further features. 😉 ---
**Author:** ![SmurfyPanda](https://forum.kurviger.com/user_avatar/forum.kurviger.com/smurfypanda/32/27060_2.png) [@SmurfyPanda](https://forum.kurviger.com/u/SmurfyPanda)\ **Post date:** [September 27, 2026, 8:29pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/9 "2026-09-27T20:29:52Z")
I suggest for it to work like every other bloody nav app: ![Screenshot 2026-09-27 at 22.21.40](https://forum.kurviger.com/uploads/default/original/3X/7/9/79d3d8d815e8bf1ce705f94263fd73f1c984bd62.jpeg) ![Screenshot 2026-09-27 at 22.22.53](https://forum.kurviger.com/uploads/default/original/3X/2/5/258a2928c2708902f4e1840e0d1b1f83c91f3af2.jpeg) Now I can’t determine if Kurviger doesn’t route trough somwhere because it has a closure, there is a bug/bad data in the OpenStreetMaps or if it is another Kurviger routing glitch. ---
**Author:** ![SmurfyPanda](https://forum.kurviger.com/user_avatar/forum.kurviger.com/smurfypanda/32/27060_2.png) [@SmurfyPanda](https://forum.kurviger.com/u/SmurfyPanda)\ **Post date:** [September 27, 2026, 8:43pm UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/10 "2026-09-27T20:43:09Z")
The point is, we don’t know what you are working on. > We are actually looking for a developer, if these things are actually trivial for you, please [apply](https://tti-gmbh-tgu-kurviger.workwise.io/). Oh yes, I expected somebody will bring the typical “if you don’t like what you are being served, cook it yourself” > Is that true? Everybody complains about this? Sure, it would be nice addition, no doubt. But to be honest, I mostly care about closures on my route. That is the crucial part. Ever since we added this feature have seen very few road closures. Before I regularly hit them on my rides. This discussion was about the slow progress, lack of clarity and communication. I provided some examples to ilustrate the point and now these examples are nickpicked instead of dealing with the main point of it. ---
**Author:** ![Andy2](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/a/b9bd4f/32.png) [@Andy2](https://forum.kurviger.com/u/Andy2)\ **Post date:** [September 28, 2026, 5:28am UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/11 "2026-09-28T05:28:54Z")
> [@SmurfyPanda](#): > > know what you are working on. > > > We are actually looking for a developer, if these things ar The name says it all, and Kurviger has been looking for staff on FB and their website for weeks. just wanted to mention that . DOT ---
**Author:** ![Toffel](https://forum.kurviger.com/letter_avatar_proxy/v4/letter/t/9dc877/32.png) [@Toffel](https://forum.kurviger.com/u/Toffel)\ **Post date:** [September 28, 2026, 7:11am UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/12 "2026-09-28T07:11:13Z")
Just let the team work, as they feel good. I like the attitude of not promising. If I would know, in what they are working - I still would not know, how this fits my expectation. It does not really help. As former Kurvinado I saw some features in the pre-versions, cancelled a week before it was published to beta, just because they were not happy with the implementation. Let them have the freedom to decide. Otherwise they will have at the end some unmaintable code. I think we had this season a rock stable piece of software with only minor glitches. It is also helpful to have a look on features what Kurviger already has compared to competitors. Sure, I also have a lot of wishes, ideas for refinements of available functions. But this could lead to other missing stuff. Wishes are always against endless ressources, the team must sort it and set priorities, find the balance for techies and new customers starting a learning curve. ---
**Author:** ![zaphod\_42](https://forum.kurviger.com/user_avatar/forum.kurviger.com/zaphod_42/32/499_2.png) [@zaphod\_42](https://forum.kurviger.com/u/zaphod_42)\ **Post date:** [September 28, 2026, 7:17am UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/13 "2026-09-28T07:17:11Z")
> [@t00thl355](#): > > I assume you are not suggesting that all road closures worldwide should be displayed at all times. So what would be the criteria to display the closures? Here my proposal: > [@Avoid Current Closures | Aktuelle Sperrungen vermeiden](https://forum.kurviger.com/t/avoid-current-closures-aktuelle-sperrungen-vermeiden/26174/207): > > Eine Anregung zur Anzeige der “aktuellen Sperrungen”: Wenn die Vermeidung eingeschaltet ist, wird automtisch eine Umgehung der Sperre erarbeitet, jedoch ist der Grund für die “neue” Routenführung nicht erkennbar. Erst nach dem Ausschalten der Vermeidung “aktuelle Sperrungen” wird es klar: - Vielleicht könnte man im Fall der Umfahrung einer Sperre deren Anzeige beibehalten und auch den Hinweis zur Verfügung st… combined by this one: > [@Sperrung (Anzeige abschaltbar)?](https://forum.kurviger.com/t/sperrung-anzeige-abschaltbar/26955/11): > > Die Sperrungen (ob nun potentiell oder aktuell) stören mich auch mehr als sie mir nutzen. Vielleicht sollte es einen “Schalter” geben, mit dem ich das Ganze nur bei Bedarf aktivieren kann - nach dem Motto “vertrauen sie mir - ich weiß was ich tue”. Oder die Anzeige der Sperrungen nicht in der “Routen-Information” des Höhendiagramms verankern sondern in der “Höhe (und Sperrungen)”-Einstellung, dort ist momentan außer der Höhe eh nichts zu sehen, und die bleibt ja erhalten. in English: A suggestion for displaying “current road closures”: When the “avoid” feature is enabled, the app automatically calculates a detour around the closure, but the reason for the “new” route is not apparent. It only becomes clear after disabling the “current road closures” avoidance feature: ![image](https://forum.kurviger.com/uploads/default/original/3X/7/6/764bfe0ee987fff0499ea3f0a51df032dcabfc46.jpeg) Perhaps, in the case of bypassing a roadblock, the roadblock indicator could be kept in place and the warning message could also be displayed? ![image](https://forum.kurviger.com/uploads/default/original/3X/f/f/ffb33bc2a366519299557a4e0a73946d6e085ff9.jpeg) The road closures (whether potential or current) bother me more than they help me. Maybe there should be a “toggle” that lets me enable this feature only when needed - along the lines of “trust me - I know what I’m doing.” Or don’t include the road closures in the “Route Information” section of the elevation profile; instead, put them in the “Elevation (and Road Closures)” setting - there’s nothing else to see there right now anyway, and the elevation data remains unchanged. ---
**Author:** ![t00thl355](https://forum.kurviger.com/user_avatar/forum.kurviger.com/t00thl355/32/27045_2.png) [@t00thl355](https://forum.kurviger.com/u/t00thl355)\ **Post date:** [September 28, 2026, 8:26am UTC](https://forum.kurviger.com/t/concerns-about-improvements-speed/27547/14 "2026-09-28T08:26:20Z")
> [@SmurfyPanda](#): > > The point is, we don’t know what you are working on. I think, we all collectiely give a lot of feedback and wishes to Kurviger and keep them as our expectations. Someone would be interested in improving AA, someone else needs an additional language, someone wants road blocks, audio points, charging stations, favourites while riding… you name it. The wishes are quite numerous, very diverse and sometimes even contradicting each other. Kurviger team has to set it’s priorities somehow and we have to accept that they will not always match our expectations. The lack of knowledge about “work in progres” makes us think that some features take extremely long time to implement (which we perceive as “slow”), allthewhile Kurviger team is actually not even actively working on it. A bit of more transparency would help us adjust our expectations and our perception of “slow” should follow automatically. The fact that they are actively hiring developers is enough feedback from my point of view. You could also question the efficiency of the work and how many discussions are needed for simple features, but that is a team internal topic in which users do not have direct insight and cannot influence in any way. That is on the team to decide. > [@zaphod\_42](#): > > Here my proposal: Thanks, but let’s keep this discussion in the dedicated threads, @SmurfyPanda has right, we drifted away to off-topic details in this thread.