Cultural heritage digitalisation projects are increasingly part of EU co-funded initiatives that require technical partners to deliver complex digital systems within strictly defined deadlines, budgets and reporting obligations. A digital guide that leads visitors along a cultural route, smart info points that respond to physical presence and a mobile application that works without an internet connection are not separate products, they are components of one integrated system that must be conceived, developed and delivered as a whole. Such a project does not begin with building an application, but with terrain analysis, defining user scenarios and understanding the technical constraints that physical locations impose on the digital system. Prolink has developed competencies that cover the full scope of such a project, from technical specification and user experience design to IoT infrastructure implementation and a multilingual content layer, and the experience gained on the architectural heritage digitalisation project provides a concrete reference point for consortia planning a similar application.
What a digital guide is and why it is not the same as a mobile application
The term digital guide is often used as a synonym for a mobile application, but in the context of cultural routes and heritage projects it refers to a far more specific product with its own requirements at the level of architecture, content and user experience. A digital guide must work in the field where mobile networks are unreliable, which means offline content availability is not an option but a technical requirement that affects the entire application architecture from the design phase. It must be localised into multiple languages because cultural routes target international visitors, and translating the interface is not the same as translating the content because each language carries its own logic for navigating and contextualising heritage. It must integrate with physical infrastructure in the field via QR codes or NFC technology, which means each location on the route is simultaneously a digital and physical object with its own identity in the system. It must have an administrative layer that allows content editors to update texts, photographs and audio recordings without technical intervention, because heritage projects have a long lifespan and content changes with new research and seasonal programmes. It must support different user profiles, from the individual tourist walking the route at their own pace to an educational group whose guide coordinates movement and delivers content to multiple devices simultaneously. Prolink approached the development of the specification for the architectural heritage digitalisation project from exactly these requirements, defining the digital guide as a product that provides visitors with a continuous and rich experience regardless of field conditions and the user's level of technical literacy.
Smart info points as the physical interface of the digital system
Smart info points are hardware installations placed at locations along the cultural route and serve as the physical interface to the digital system, but their role goes beyond simply displaying content on a screen. An info point that responds to visitor presence via sensors, communicates with the mobile application via Bluetooth or NFC, reproduces multimedia content and records visits for the project consortium's analytics is functionally an IoT device that must be designed with clearly defined communication protocols, power supply requirements and a long-term maintenance strategy. The hardware selection is not a trivial decision because an info point installed outdoors must withstand weather conditions, have vandal-resistant housing and power supply that can come from the grid, solar panels or batteries depending on the location, and each of these scenarios introduces different technical requirements. For projects funded by EU funds it is particularly important that the hardware component meets the digital transition requirements defined in the tender documentation, which means the technology selection is not purely a technical but also an administrative decision that must be documented and justified in the project application. The software layer of the info point must be centrally managed, meaning a content administrator can update all points on the route simultaneously from a single interface without physical access to each installation, and the system must record usage data that forms part of mandatory reporting to the funding body. Prolink analyses location conditions, power and network infrastructure availability, tender documentation requirements and long-term maintenance costs when specifying info points, and proposes hardware and software solutions that are compatible with project requirements, technically reliable and financially sustainable throughout the entire project lifespan.
Mobile application for a cultural route: iOS, Android and offline architecture
The mobile application at the centre of the digital guide must cover several functional layers simultaneously and each of them has its own architectural implications that must be resolved in the specification phase, not later in development. An interactive map with GPS navigation must support offline operation, which means cartographic data must be downloaded and stored locally on the device, with logic that determines what level of detail is downloaded, how much storage it occupies and when it is updated. Multimedia content by location, which includes text, photographs, audio narration and video recordings, must be organised in a structure that allows selective downloading by route or location because users must not be forced to download the entire application content before they can head into the field. Integration with info points via NFC or QR codes must be robust enough to work even when the user has no mobile data, which means the application must locally store the identifiers of all points on the route and know which content to display without a server call. The administrative CMS must be available as a web application that allows content editors to manage all locations, languages and media content from a single interface, with a view of visit statistics and usage analytics required for EU reports. Simultaneous development for iOS and Android means architectural decisions in the early phase determine overall costs, and Prolink uses Ionic as the technology framework for such projects, sharing the code base between platforms and enabling a consistent experience on all devices at significantly lower development and maintenance costs. Ionic does not mean a compromise on functionality as it supports native hardware integrations including Bluetooth communication with info points, NFC reading and GPS navigation that are essential for a cultural route project. Prolink defined all these layers in detail when preparing the specification for the cultural route project, with a clear functionality priority table that distinguished the MVP to be delivered in the first phase from extensions coming in later development cycles.
Multilingualism as an architectural requirement, not a translation service
Cultural projects targeting international visitors and meeting EU tender application requirements regularly include multilingualism as an obligation, but implementing multilingualism in a digital guide requires architectural decisions that cannot be added retrospectively without significant rework costs. A system supporting Croatian, English, German and Slovenian as equal languages must have a CMS that allows editors to manage content in all languages independently, with clearly defined processes for entry, proofreading and publication without technical intervention from the development team. Each location on the route has its own text description, audio narration and potentially video content in each of the supported languages, which means the total volume of content that must be produced, edited and stored is many times greater than it appears at first glance and must be budgeted for in the project application from the outset. The application interface must be adapted for languages with longer words and more complex grammatical structures because a design that looks clean in English often breaks in German or Slovenian if typography and layout are not designed with this in mind from day one. Audio narration in multiple languages introduces separate logistics for recording, processing and storing audio files that the application must serve to the user in their chosen language without delay, and the quality of narration directly affects the perceived value of the entire project because it is the most intimate layer of experience the visitor receives in the field. Prolink defined multilingualism at the architectural level from day one on the architectural heritage digitalisation project, with clearly separated content layers by language and a CMS structure that allows editors to manage each language independently without the risk of a change in one language unintentionally affecting another.
EU funds and a technical partner: what a consortium needs from Prolink
Projects funded by EU funds have specific requirements for the technical partner that differ from standard commercial engagements because documentation, reporting and compliance with tender conditions form part of the delivery just as much as functional software. A technical partner who understands the structure of an EU project can help the consortium prepare the technical part of the application by defining the scope of development, system architecture and cost estimates in a format that is directly usable in project documentation, without the need for subsequent adaptation and translation of technical language into administrative language. Delivery deadlines must be aligned with project milestones defined in the contract with the funding body, which means the development plan is not an internal document of the development team but a binding instrument that must be realistic, detailed and aligned with the capacities of all partners in the consortium. Prolink went through this process as part of the cultural route project, from initial specification and cost estimation in the application phase to technical implementation and documentation that accompanied every project milestone, including technical reports that were part of mandatory reporting to the funding body. Understanding that cycle, from application to final report, distinguishes a technical partner who has been through an EU project from one who is only estimating what such an engagement requires, and that difference becomes visible at the latest at the moment of the first audit or scope change request.
Why clients choose Prolink
Consortia applying for tenders such as CR.EU.IN.HERITAGE or related Creative Europe and European Regional Development Fund programmes need a technical partner who understands both the technical and project context, because misalignment between these two layers is the most common reason for delays and budget overruns in EU projects. Prolink brings concrete experience of delivering a digital system for a cultural route that included a mobile application built on Ionic, smart info points with IoT integration, a multilingual CMS and administrative analytics, which means cost and timeline estimates for a similar project are not theoretical but based on real data. Consortia planning a similar application who are looking for a technical partner that can participate in documentation preparation, take responsibility for technical delivery and follow the project cycle through to the final report are welcome to contact the Prolink team during the application preparation phase, when the space for quality planning is greatest.