4. Product Overview
eBattery is an EV super app that brings electric vehicle owners' daily use, trip, communication and vehicle ownership needs together in a shared mobile experience. The product is designed so that its core, built around the map, artificial intelligence, route and trip planning, community and the Game Zone, expands with charging transactions, payment, shopping, insurance and home charging services.
At the core of the app is the user's ability to keep the same vehicle and trip context while moving between different needs. A station reviewed on the map can be added to the route plan; a trip prepared with AI can be edited on the relevant planning screen; the resulting plan can be shared in the community. In this way, each module takes on a function that helps the user complete what they started.
The product experience is shaped around three core elements: quick access to what is needed, consistency across information, and user control. The user should be able to find the right service easily, understand which conditions the information they see represents, and make decisions about the recommendations.
This section describes eBattery's user-facing product structure. Map, AI, route and trip planning, community and Game Zone make up the current product core. Charging and payment, EV Market, mobile charging support, insurance and home charging services fall within the post-launch expansion scope. The Web3 layer is a separate development area covering RWA-based station projects, Launchpad, monitoring of project performance and secondary-market transactions subject to eligibility conditions.
4.1 Home Screen and User Experience
4.1.1 The Role of the Home Screen and Information Priority
The home screen is the starting area that lets users reach their core needs in eBattery. When users open the app, they may want to discover nearby stations, plan a trip, go to the community or check their progress in the Game Zone. The screen’s information layout supports easily understanding these different purposes and starting the relevant action.
In the main experience, access to frequently used functions comes first. Clear transitions are built between core areas such as the map and station discovery, route and trip planning, the AI assistant and the community. Detailed settings and secondary actions are presented in the context of the relevant module.
The aim of this approach is for the user to get to what they need without spending much effort learning the app's structure. A user looking for a station can continue the discovery flow without having to deal with the details of shopping or game mechanics. A user who moves to the Game Zone reaches that module's own progress and interaction structure.
Information priority is also assessed according to the moment of use. While vehicle and battery information gain importance when preparing for a trip, location, socket compatibility and available service information come to the fore when examining a station. In this way, screens focus on the decision the user will make at that stage.
4.1.2 Discovery and Quick Access from the Map
The Map is one of eBattery’s main work areas. Users can browse charging stations around them, in the area they want to go to or along their trip route on the map.
Choosing a station starts with seeing a point on the map and moves on to a detailed review. The user can examine the station's operator, socket types, charging power and location; within the scope of accessible data, they can find information such as price and operating status. Real-time availability information is provided for stations supported by the relevant integration.
Filters on the map make it easier to find options that suit the user. Criteria such as socket type, power, operator and availability help narrow the search to the user’s vehicle and needs.
The map's quick access menu brings together four core functions:
| Quick access function | The transaction it offers the user | Purpose in the experience |
|---|---|---|
| Favorites | Reaching saved stations and assessing them by proximity | Making repeated discovery needs easier |
| Layers | Switching between normal and satellite view, managing visible content | Adapting map information to its purpose of use |
| Send Alert | Creating a traffic accident, emergency ambulance and vehicle breakdown report | Passing short-term information to people nearby |
| Emergency Charge | Quickly creating a route to the nearest suitable charging point | Reducing the time spent searching for and navigating to a station |
Road alerts are visible on the map for 10 minutes as pins of different colors by type. Colors, icons and descriptions are used together to make the nature of the report clear.
The social map, in turn, supports making users who turn on location sharing visible and reachable. Station discovery and social visibility are managed as separate preferences serving the user’s different needs.
4.1.3 Getting Started with the AI Assistant and First Interaction
The AI assistant connects the need a user expresses in natural language to the relevant functions of the app. The user can define a route, ask for trip planning, search for a suitable station or have available efficiency information interpreted.
AI Chat’s opening experience includes suggestion cards and shortcuts that make the first interaction easier. Plan Route, Plan Trip, Suggest Nearest Station and My Efficiency and similar entries let the user see which areas the assistant can help with. The user can pick one of these options or type a message directly.
The assistant's visual identity supports the consistency of the conversation experience. The animated avatar in the welcome area moves to a smaller position tied to the messages once the chat starts. In this way, the visual element that guides at first entry becomes one that supports reading the content during the conversation.
Displaying responses progressively helps the user understand that the operation is still in progress. For operations that require computation, such as creating a route or trip, the process status is also explained.
If the user has saved vehicle information, the assistant uses that context. Information missing for the trip, such as the starting point, destination, or current battery level, is completed during the relevant step. This approach reduces repeated questions while preserving the information needed for the decision.
4.1.4 Result Cards and Moving to Action
The outputs of AI interaction are supported by result cards that take the user to the relevant app screen. These cards combine a short preview of the generated result with the action needed to continue.
A route card can show the start and destination points of the journey and a basic summary of the plan. The user can open the route screen from the card and review the details. A trip card links the days and stops of the generated plan to the relevant trip screen. A station card gives access to the details of the selected service point.
This structure creates continuity between the conversation and the app functions. The user can move on to the relevant result without having to search again on another screen for the station the assistant suggested, or re-enter the details of a prepared route.
| Result type | The core context the card carries | Continued area |
|---|---|---|
| Route | Selected vehicle, start, destination and trip summary | Route planning screen |
| Trip | Target region, duration and visit plan | Trip planning screen |
| Station recommendation | Station identity, location and suitability information | Station detail screen |
| Efficiency assessment | Summary of the period reviewed and the accessible measurements | Efficiency screen |
Actions such as saving, sharing, adding to favorites or starting the route are offered according to the scope of the relevant result. The actions on the card express the user's next step clearly.
4.1.5 Preserving Context Across Modules
In eBattery, a function can have more than one entry point. A user can reach a station from the map, from an AI suggestion, or from their favorites. Likewise, a chat can be started from the community area or from a profile on the social map.
These entry points require the relevant information and transaction history to stay consistent. A one-to-one conversation started from the map belongs to the same communication flow as the message history in the community module. The map is one of the entry points that give access to this conversation.
Back navigation behavior is also designed to match the path the user took. A user who goes from the map to a profile and then to messaging should find the map context they started from when they go back. Similarly, a route opened from an AI card stays tied to the plan that card represents.
This approach also matters for shared content. The recipient of a route or trip card should be able to see which plan the card represents. When the plan is meant to be applied with the recipient's own vehicle, the energy and charging assessment is made with the new vehicle context.
This way, content sharing and personal planning complement each other; another user’s plan is not automatically applied to a new user under the same energy conditions.
4.1.6 The Place of the Game Zone in the Main Experience
The Game Zone is a separate section of the experience that supports eBattery's user engagement and loyalty. While the main app flow contains short game-related summaries and access points, the detailed game mechanics are gathered in their own area.
Daily Chest progress is one example of this link. The user can see the status of completed quests in summary form and go to the Game Zone for the relevant action. A display such as "2/3 quests completed" lets progress be understood without opening the detailed quest list.
Vehicle upgrades, virtual trips, quests, the reward wheel, the reward store and rankings are presented within the Game Zone’s own screen layout. This layout helps keep the depth of the game experience while the map and trip functions maintain their focus.
The vehicle status in the game is not interpreted as the physical condition of the user's real vehicle. The virtual vehicle's level, upgrades and trip results belong to the game system. The real vehicle profile is used for functions such as station compatibility and trip planning.
4.1.7 Visual Language, Readability and Transaction States
eBattery's visual approach is shaped around blue and purple tones, consistent icons, soft transitions and a clear information hierarchy. While the blue at the center of the brand identity supports main actions and navigation, text and symbols are used together with color so that different states can be understood.
Visual consistency makes different modules feel like parts of the same product. Cards, buttons, headings and back behavior are arranged with similar logic. An interaction a user learns on one screen stays familiar on another.
Clarity about transaction states is an important part of the experience. While a plan is being prepared, it is shown that the calculation is in progress; while data is refreshing, that an update is under way; and when no result is found, under what conditions the search can continue.
A concrete example of this principle is that a station whose live status cannot be accessed is not treated as "available". Similarly, the calculated charging time is presented as an estimate. The user can tell whether the information shown is a confirmed record or the result of a calculation.
Performance is also part of this whole that the user sees. Navigating the map, switching between modules and AI operations are handled in a way that preserves the usability of the interface. Understanding the progress of an operation makes it easier to manage waiting time.
4.2 Module Map
4.2.1 Functional Structure of the Product
eBattery’s modules form a whole that meets the needs of an electric vehicle owner at different stages. This structure is organized around discovery and planning, communication and participation, transactions and service access, and economic participation in physical infrastructure.
Each module has its own role. The connections between modules are built through shared elements such as the vehicle profile, the station record, the route plan, the user account and content cards.
| Module | Core function | Position within the product scope |
|---|---|---|
| Map and station discovery | Finding, filtering and reviewing stations | Current product core; dynamic information depends on integration |
| eBattery AI | Understanding the need in natural language and directing to the relevant functions | Current product core |
| Route planning | Creating a journey based on the vehicle and energy needs | Current product core |
| Trip planning | Organizing visit points, duration and charging needs together | Current product core |
| Community and messaging | User communication and sharing experiences | Current product core |
| Game Zone | Virtual vehicle, quests, progress and loyalty | Current product core |
| Charging and unified payment | Session and payment management on supported networks | Post-launch integration phase |
| EV Market and mobile charging support | Access to product and service providers | Post-launch expansion |
| Insurance and comprehensive vehicle insurance | Access to quote, policy and renewal services | Post-launch partnership and integration phase |
| Home Charging Network | Developing equipment, installation and points suitable for sharing | Phased expansion |
| Web3 and RWA | Economic participation in station projects and performance tracking | Area of development under the 2027 target |
This map shows the product vision in which modules are connected to one another. The geographic scope and transaction capabilities of the services in each module are expanded together with the relevant integration and operating structure.
4.2.2 How the Map, Route and Trip Planning Work Together
The map provides a spatial view of service points and trip context. Route planning builds a trip that can be driven between the start and destination points. Trip planning then adds the places to visit and the time that can be set aside to that journey.
These three functions working together make it possible to arrange the plan at different scales. The user can first choose a station and create a route to it. In another case, they can first set the destination and assess suitable charging stops along the route. When preparing a trip, they can plan visit points and charging breaks together.
AI provides a shared interaction and explanation layer for these flows. It interprets the user’s preference, explains the main reasons behind the plan and makes it easier to move to the relevant screen.
Changing the plan also affects the related energy assessment. If a new stop is added or the selected vehicle is changed, the route and charging need are reconsidered under the new conditions. The stop order and road preferences explicitly set by the user are preserved as inputs to planning.
This shared structure reduces the trip being rebuilt in a disconnected way on different screens.
4.2.3 How Community and Messaging Connect to the Product
The Community module lets users connect around electric vehicle ownership. Brand- and model-focused groups, topic threads and direct messaging meet different communication needs.
In the community experience My Joined and Explore the distinction is important. Joined brings together the groups the user is a member of. The Discover area helps find accessible groups in the selected language. A user joining a group in a different language does not require their existing membership to be searched for again every time the language changes.
The chat language can be managed separately from the app's general interface language. This way, users can use the app in their preferred language and also join communities in other languages.
Route, trip, and efficiency cards connect the community to the other modules. When asking for opinions on a particular plan, the user can share a preview of the plan. The recipient can access the details of the relevant content from within the app.
Reaching AI Chat from the community area as well allows the same assistant experience to be used from different entry points. In the interface, the identity and function of AI interaction are clearly separated from conversations with people.
4.2.4 Game Zone, Progress and Loyalty
The Game Zone offers an electric-vehicle-themed virtual progression experience. The user upgrades their virtual vehicle, completes quests, manages their in-game trips, and takes part in reward mechanics under the relevant rules.
The vehicle upgrade system; Battery, Motor, Tire, Charging Unit, Aerodynamics, Navigation, Chassis, Suspension, Brake and Lighting categories. The effects of these categories belong to the in-game attributes of the virtual vehicle.
Different functions are kept separate in the points structure:
| Item | Role in the product |
|---|---|
| EP — Energy Points | Resource used for in-game upgrades and related mechanics |
| XP | Indicator related to experience, progress and titles |
| CC — Charge Credit | Resource linked to real service or reward benefits offered under the program terms |
| Reputation | A criterion that supports the assessment of contribution quality and fair use |
EP cannot be purchased; EP and Charge Credit are not converted into each other. Charge Credit is not converted into cash or crypto assets. Its areas of use are defined by the relevant program and service terms.
Daily quests, the daily chest, the Reward Wheel and season rankings make up the different interaction areas of this structure. The availability of rewards and the scope of service are shown with rules the user can review.
The Game Zone belongs to the Web2 loyalty structure. Progress in the game does not automatically create an economic right in RWA stations.
4.2.5 Charging Session and Combined Payment
The charging and payment module is a post-launch development area that combines station selection with the use of the service at supported operators.
In the targeted flow, the user selects the station and a suitable socket, reviews the price and service conditions, completes the required authorization and starts the charging session. The ongoing session is monitored with the information provided by the operator integration; the completed transaction is saved to history.
In this experience, station, session and payment records are linked to one another. The user can consider together which station they were served at, the energy and time information available, and the resulting transaction amount.
Transaction statuses are shown clearly. Payment authorization, the start of charging, completion of the session and the formation of the final amount are different stages. Making these stages visible makes it easier for users to follow their transaction and get support when needed.
The scope of the module is developed according to operator, country and payment service connections. Which transactions a station shown on the map supports is indicated on that station's screen.
4.2.6 EV Market, Mobile Charging Support, Insurance and Comprehensive Coverage
EV Market is a post-launch marketplace area where products and services related to electric vehicle ownership are discovered. Home charging devices, portable charging equipment, cables, compatible accessories and vehicle care products are considered within this scope.
At the center of the product experience is understanding technical specifications and vehicle compatibility. Users should be able to check whether a product suits their own vehicle and purpose of use, and reach the seller, delivery, return and after-sales service terms.
Mobile charging supportis one of the important components of EV Market on the service side. The aim is for users who have run out of energy or need help reaching a suitable station to reach the relevant providers in the areas where service is offered. The feasibility of the service is assessed together with location, vehicle compatibility and the provider’s operational coverage.
This service is used at different stages than the Emergency Charge function on the map. Emergency Charge provides fast routing to a reachable station. Mobile charging support addresses the need for service to reach the point where the user is.
In insurance and comprehensive coverage, the aim is to enable, through partners, offer review, coverage comparison, policy transactions and renewal tracking. Topics such as battery, charging equipment or roadside assistance are shown according to the actual scope of the policy offered.
4.2.7 Home Charging Ecosystem
The Home Charging area is being developed to link device selection, installation, use, and the sharing of suitable points.
In the first stage, the user is supported in evaluating home-type devices and installation services. Vehicle compatibility, usage needs and the technical conditions of the installation site are considered together. The device's product features and the suitability of the installation on site are separate matters to assess.
In later stages, the aim is for private charging points with suitable operating and access conditions to join the network and be discovered on the map. A point being visible is managed together with its sharing hours and service conditions.
This module expands eBattery's physical service ecosystem. EV Market contributes to device and service discovery, the map to location access, and suitable integrations to usage and payment flows.
4.2.8 The Web3 Layer and Access to Station Projects
The Web3 layer is a development area designed for economic participation in eBattery’s physical charging infrastructure and for monitoring project performance.
The Launchpad is the access area where the technical and economic information of station projects is presented. Within the eligibility conditions, users can review projects and obtain information about a station’s location, device structure, investment scope and economic rights.
The digital identity assigned to each station links the physical asset with the relevant technical records and project information. Appropriate data obtained during operation is connected to digital record-keeping and reporting processes through IoT and oracle infrastructure.
The investor experience covers calculating the distributable net profit after expenses and tracking monthly distributions. The secondary transaction area, in turn, is designed to support the relevant rights changing hands under valid transfer and investor eligibility conditions.
This structure can be linked to the shared user account; the investor identity and required verifications are managed in the relevant Web3 transaction flow. A driver’s use of map or community services does not depend on their participation in investor functions.
4.3 Vehicle-Focused Personalization
4.3.1 Using the Vehicle Profile as a Shared Reference
The vehicle profile is one of the core sources of information that allows eBattery to produce results suited to the user. A station’s technical compatibility, a trip’s energy need or the suitability of a piece of equipment is evaluated together with the characteristics of the selected vehicle.
For this reason, brand and model information is the starting point of personalization. Details such as model year, battery option, and technical variant help to correctly represent vehicles that have different characteristics under the same model name.
The vehicle profile is used as a shared reference across different modules. The Map can evaluate suitable sockets based on this profile; route planning can link energy calculations to the relevant vehicle; and EV Market can present product compatibility information in the same context.
In route planning, the user can select their saved vehicle or define a different vehicle profile for that trip. Which vehicle the plan was created for is kept visible.
This approach bases personalization on concrete technical characteristics. The user’s preferences, in turn, help organize the options within this framework of technical compatibility.
4.3.2 Technical Vehicle Information, Trip Data and Preferences
The information used for personalization does not change at the same rate. A vehicle’s socket type may stay constant for a long time, while the battery level can differ on every trip. The user’s toll-road preference can be changed for a specific trip.
eBattery addresses this information in three main groups:
| Information group | Example areas | Purpose of use |
|---|---|---|
| Vehicle features | Make, model, year, usable battery capacity, socket type, AC and DC charging specifications | Technical compatibility and the basic energy model |
| Trip information | Starting battery level, departure point, destination, intermediate stops and time plan | Calculating the relevant trip |
| User preferences | Road options, speed or efficiency priority, operator and break preferences | Organizing suitable alternatives by personal priorities |
This distinction helps prevent an old value from being used in the wrong context on a new journey. The battery level the user entered in a previous plan is not accepted as the current status of the new journey.
Similarly, a preference chosen for a specific trip and a permanent user preference are handled separately. When a user wants to avoid a toll road for one trip, applying that to all future plans should be up to their own choice.
4.3.3 Personalization Appropriate to Data Source and Freshness
The source of vehicle information determines which assessments can be made. Technical information taken from model specifications, the battery level entered by the user and a measurement taken directly from the vehicle connection are different types of data.
In the current planning approach, the user manually enters the battery level at the start of the trip. The saved vehicle profile is used together with this value to assess the energy need. Obtaining live data through vehicle manufacturer connections and other supported integrations is a later development area.
This distinction also sets the scope of efficiency comments. The system makes its assessment at the level of the information it can access. A comment that requires detailed driving data is not produced from the vehicle model and starting battery percentage alone.
In the results shown to the user, the timing and nature of the data matter. Current measurements, user reports, and model-based estimates are each treated according to their own meaning.
This way, personalization proceeds at the level of explanation that the accessible data supports. As new integrations are added, the scope of the assessments is expanded as appropriate.
4.3.4 Vehicle Compatibility in Map and Charging Recommendations
The vehicle profile links the options shown on the map to the user's technical needs. Connector compatibility, AC and DC support, and the vehicle's charging characteristics are the main inputs for evaluating a station.
Technical compatibility comes before personal preferences. A user's preference for a particular operator does not make a connector the vehicle cannot use suitable. Preferences help in evaluating the usable options among themselves.
The maximum power stated on the station is also interpreted together with the vehicle's specifications. The estimated charging experience presented to the user is not based solely on the device's label value; it is assessed using the vehicle and station information that is accessible.
The timing of availability information also matters. The current status the user sees on the map may differ from the status at the moment they arrive at the station. The interface presents real-time information and, where available, predictive assessments separately.
This approach turns the station card into a more meaningful decision tool. The user can more easily understand why an option suits their own vehicle and journey.
4.3.5 Personalization in Route and Trip Plans
Route personalization assesses the vehicle’s technical specifications together with the user’s trip purpose. Between the same start and destination points, different suitable plans can arise depending on different priorities.
A user who prioritizes time can focus on total trip duration. A user who prioritizes efficiency can give more weight to energy needs and charging cost. A user who is sightseeing can place visit points and break arrangements at the center of the plan.
| Use case | Key information in personalization | Expected product approach |
|---|---|---|
| Short daily trip | Current energy, nearby stations and frequently used places | Quick and simple assessment |
| Intercity travel | Vehicle range, starting battery, stops and road preferences | Building a route with charging breaks |
| Multi-day trip | Number of days, interests, visit durations and daily energy need | Editable plan split into days |
| Traveling with a different vehicle | Technical specifications of the new vehicle | Evaluating the previous plan with the new vehicle context |
In a trip plan, the user's intervention is preserved. Removing a stop, changing a visit duration or adding a new place requires the relevant part of the plan to be reassessed.
Planning services work with the data scope that is accessible. Traffic, station status or other environmental inputs are used to the extent they are supported. Capabilities such as including weather conditions in a more detailed energy model and adapting with live vehicle data are expanded through development phases.
4.3.6 How the Vehicle Profile Contributes to Community and Service Discovery
Vehicle information can help the user discover relevant communities and services. Connecting with owners of the same model, reviewing equipment compatible with the vehicle, or finding answers to specific usage questions are examples of this contribution.
On the community side, the vehicle model can help recommend relevant groups. The groups the user joins and the information they share on their profile are up to their own choice. Not every field used for technical personalization needs to be visible on the social profile.
On the EV Market side, the compatibility assessment is based on matching the product’s own features with the vehicle profile. A similar brand or model name is not considered sufficient on its own; the technical specifications and terms of use of the relevant equipment are taken into account.
For insurance and installation services, the vehicle profile can provide the initial information. Additional information required by the quote or installation assessment is completed in the relevant service flow.
If the vehicle is changed, new recommendations are generated according to the current profile. Previous trip and transaction records, meanwhile, are meant to stay understandable in the vehicle and service context in which they took place.
4.3.7 Explicit Preferences and Recommendations That Evolve Over Time
In eBattery’s personalization approach, preferences explicitly stated by the user take primary priority. The selected vehicle, road constraints, route mode and break preferences are direct inputs of the relevant plan.
Recommendations learned from behavior are addressed in a later development layer. For example, a user who often chooses certain operators, or who keeps turning to other options instead of some recommendations, may be taken into account to understand their preferences better.
This learning does not require a single behavior to be interpreted as a lasting preference. A user may have chosen a particular station because of that day's conditions. Behavior patterns are assessed together with the relevant context and sufficient observation.
When an explicit user preference conflicts with a suggestion inferred from past behavior, the choice the user specified for that transaction takes precedence. Personalization supports the user in understanding and managing their options.
Notifications and proactive suggestions follow the same approach. Users can adjust which areas they want to be informed about. The app knowing the person gains value when control remains with the user.
4.3.8 The Separate Purposes of the Real Vehicle, the Virtual Vehicle and the Investor Identity
The eBattery account forms a shared foundation that provides access to different product areas. The profiles and records used in these areas are separated according to the functions they represent.
Actual vehicle profile, is used in services such as station compatibility, energy need, route planning and product suitability. It represents the technical context of the user's physical vehicle.
In-game virtual vehicle, is related to upgrade categories, levels and virtual trip mechanics. A battery or motor upgrade in the game does not change the real vehicle’s capacity or performance.
Investor ID is related to eligibility, authorization and economic-right records in the Web3 layer. The station's digital identity also represents the physical project asset, separate from the investor's or driver's personal vehicle profile.
These distinctions make the product's different purposes of use easy to understand. Within the same app, the user can plan a trip, communicate in the community and join the Game Zone; what information and what right each action rests on stays clear.
eBattery's vehicle-focused personalization works within this framework: technical suitability is based on real vehicle data, trip suggestions on current planning inputs, social visibility on user preferences, and economic participation on the relevant project terms.
