Note that verified routes work just fine with the localized routes, provided the user constructs them:
From the ex_cldr_routes default path structure:
~p"/pages_#{@locale}/#{@page}"
But your library also generates the explicit locale helpers, so the user calls those when they are in areas specific to that locale (page_de_path(.... So that usecase simply becomes writing the actual verified path:
~p"/pages_de/#{@page}"
And for convenience, your library currently providers a LocalizedHelpers module, so it could also provide the same kind of thing which wraps the canonical ~p:
localized_path(@locale, ~p"/pages/#{@page"})
So I’m not seeing the issue with verified routes. In fact, I actually think it’s a big win to simply write the paths vs helpers when that’s all the user needs, (~p"/pages_de/#{@page}" vs Routes.pages_de_path(@conn, @page) and the localized_path macro would also still be quite nice.
Lastly, your library users can still use helpers (by not passing helpers: false to Phoenix.Router) and use all the existing functionality if they so choose 
