To make life easier, it would be nice, if custom created POI's (turned on to be viewed) would appear in search for navigating and selectable as destination. This would make, on some occasions to me, the creation of favourites obsoletes to me.
I've created over the time abbreviations (prefixes) I use in front of my custom POI, as categorizations, colours and symbols I have etc. will always be lost when converting, importing, and exporting etc. Just to give an example what I put in front is like:
AIR - Airport
BEA - Beach
BRG - Bridge
BUS - Bus-Station
BUY - Grocery
CAF - Café
CCH - Church, Abbey etc.
CPG - Campground
CTY - City (I like to visit)
EAT - Eatery, Restaurant, Street Food
ENT - Entertainment, Cinema
FER - Ferry
FTF - Fortification, Castle, Burg
FST - GAS, Fuelstation
GCH - Geocaches
GEO - geological place
GRD - Garden, Parc
HBR - Harbour
HKE - Hike
RNP - regional or national Parc
and a few more... what you see above, behind the dash is the explanation, which will be of course be replaced by the name of my custom POI, like "BUY - MEC Outdoorstore Halifax" or "CCH - Aachen Dome" etc.
Now, with search, I wish to get the closest around me custom POI included in search, when searching for my next stop and navigation point.
Let's say, I am at the middle of nowhere in Denmark near Ahus, and I have made some custom POI where I can get LPG for my car or cooking stove. I would go to the MyRoute Nav app and start type "FST - " which would ideally list my custom POI: "FST - Ahus Shell with LPG".
Mit freundlichen Gruessen / Met vriendelijke groet / Best regards
Joerg
(Cookie-On-Tour.de)
@Cookie-On-Tour Fun suggestion 
@Corjan-Meijerink well, I just thought that all POI to be included into search would be too much, except for the ones we have already buttons for (like restaurant, parking etc.), it would be easier to just ask to add the custom POI DB into search and it might be easier to implement the custom POI DB as a source
@Peter-Schiefer I am talking about the steps later, when my works is done and I have worked out the POI's of my interest, that I want to visit (or not).
So, I have prepared my own custom list of POI - the way I arrange, categorize, and use them, with my prefixes as said - this is my organisational structure.
I don't want to access common or published POI. I want an easier access to my custom POI (and yes - some of my custom POI may equal to published and official ones, but I create my own ones on top, to distinguish between those I care and (may) want to visit - all other ones I disregard).
If you try to search for your custom POI while at the navigation screen with the magnifier glass you will not be successful, you can search only for public POI and by category. You cannot search by free text to find your custom POI; this is my request.
@Corjan-Meijerink well, I just thought that all POI to be included into search would be too much, except for the ones we have already buttons for (like restaurant, parking etc.), it would be easier to just ask to add the custom POI DB into search and it might be easier to implement the custom POI DB as a source
