FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“SYSTEM AND METHOD FOR MANAGING ONE OR MORE CROSS-PLATFORM
APPLICATIONS”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specifcaton partcularly describes the inventon and the manner in which it is to be performed.

SYSTEM AND METHOD FOR MANAGING ONE OR MORE CROSS-PLATFORM
APPLICATIONS
FIELD OF INVENTION
[0001] The present disclosure relates generally to the field of communication system. More particularly, the present disclosure relates to a method and system for managing one or more cross-platform applications.
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] In the recent years, various tools have been developed to help software developers develop high-quality cross platform applications. For example, one of the currently known tools can be used by developers to develop applications that can run on both iPhone operating system (iOS) and Android platforms. The developers and programmers can develop application apps through Dart language. Although these tools bring many innovations, cross-platform solutions, and opportunities, they also bring many problems.
[0004] For instance, for updating a user interface (UI) and/or a UI function, a traditional method is to use a state management ‘setState’ function for managing a state of UI. However, there are a number of challenges with using such state management functions. It leads to stateful components, which can make code more complex and harder to maintain readability. Managing and tracking state changes within a component can introduce bugs and complicate code maintenance. The `setState` can be scattered across different components, making it difficult to track and understand the flow of state. As the application grows, maintaining a clear picture of state management becomes challenging, impacting debugging and code comprehension. The `setState` can lead to unexpected side effects and difficulty in reasoning

about state changes, particularly when dealing with asynchronous updates or complex dependencies.
[0005] Thus, there exists an imperative need in the art to provide an efficient system and method for solving the user interface (UI) state update issues and for managing one or more cross-platform applications, which the present disclosure aims to address.
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0007] An aspect of the present disclosure may relate to a method for managing one or more cross-platform applications. The method comprises extracting, by a translator unit of a data access layer, event-based data from one or more data sources. The method further comprises generating, by the translator unit of the data access layer, an event-based data model based on the event-based data. The method further comprises receiving, at a logic unit of a logical layer, the event-based data model from the translator unit. The method further comprises extracting, by the logic unit of the logical layer, one or more use cases. The method further comprises identifying, by the logic unit of the logical layer, a requisite data based on the event-based data model and the one or more-use cases. The method comprises displaying, by a stateless UI widget of a presentation layer, the requisite data.
[0008] In an exemplary aspect of the present disclosure, the event-based data is extracted as a raw data from the one or more data sources.
[0009] In an exemplary aspect of the present disclosure, the one or more-use cases correspond to a user interface (UI) representation of the raw data for one or more particular events.
[0010] In an exemplary aspect of the present disclosure, the event-based data model provides the requisite data based on the one or more-use cases.

[0011] In an exemplary aspect of the present disclosure, the requisite data corresponds to a particular data required as per the one or more-use cases.
[0012] In an exemplary aspect of the present disclosure, the data access layer, the logical layer, and the presentation layer are configured to communicate with each other.
[0013] In an exemplary aspect of the present disclosure, the data access layer, the logical layer, and the presentation layer are configured to operate in a stacked configuration.
[0014] In an exemplary aspect of the present disclosure, one or more layers are customizable.
[0015] In an exemplary aspect of the present disclosure, the one or more layers are implemented model-view and view model (MVVM) based stack layer architecture.
[0016] Another aspect of the present disclosure may relate to a system for managing one or more cross-platform applications. The system comprises a data access layer comprising one or more data sources configured to store event-based data. The data access layer further comprises a translator unit configured to extract the event-based data from the one or more data sources. The translator unit is further configured to generate an event-based data model based on the event-based data. The system further comprises a logical layer that comprises a use case unit configured to store one or more uses cases. The logical layer further comprises a logic unit configured to receive the event-based data model from the translator unit. The logic unit is further configured to extract the one or more use cases. The logic unit is further configured to identify a requisite data based on the event-based data model and the one or more use cases. The system further comprises a presentation layer that comprises a stateless user interface widget configured to display the requisite data.
[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing one or more instructions for managing one or more cross-platform applications, the one or more instructions including executable code, the executable code when executed, may cause a translator unit of a data access layer to extract event-based data from one or more data sources. Further, the executable code when executed may cause the translator unit of the data access layer to generate an event-based data model based on the event-based data. Further, the executable code when executed may cause a logic unit of a

logical layer to receive the event-based data model from the translator unit. Further, the executable code when executed may cause the logic unit of the logical layer to extract one or more use cases. Further, the executable code when executed may cause the logic unit of the logical layer to identify a requisite data based on the event-based data model and the one or more use cases. Thereafter, the executable code when executed may cause a stateless user interface widget of a presentation layer to display the requisite data.
[0018] Yet another aspect of the present disclosure may relate to a user equipment (UE) for managing one or more cross-platform applications. The UE comprises a processor configured to: extract an event-based data from one or more data sources. Further, the UE generate an event-based data model based on the event-based data. Further, the UE receive the event-based data model from a translator unit, extract one or more use cases. Further, the UE identify a requisite data based on the event-based data model and the one or more-use cases. Thereafter, the UE display the requisite data to a user.
OBJECTS OF THE INVENTION
[0019] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0020] It is an object of the present disclosure to provide a system and a method for providing stack layer architecture for flutter applications.
[0021] It is another object of the present disclosure to provide a system and a method for stack layer architecture with singleton pattern in cross platform application.
[0022] It is yet another object of the present disclosure to provide a system and method for Model- View-View Model (MVVM) and event driven based stack layer architecture with stateless UI widget, which update specific widget based on triggering event as per application use cases.
DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0024] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0025] FIG. 2 illustrates an exemplary block diagram of a system for managing one or more cross-platform applications, in accordance with exemplary embodiments of the present disclosure.
[0026] FIG. 3 illustrates a flow diagram of a method for managing one or more cross-platform applications, in accordance with exemplary embodiments of the present disclosure.
[0027] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0028] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.

[0029] The ensuing description provides exemplary embodiments only, and is not intended to
limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description
of the exemplary embodiments will provide those skilled in the art with an enabling description
5 for implementing an exemplary embodiment. It should be understood that various changes may
be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0030] Specific details are given in the following description to provide a thorough
10 understanding of the embodiments. However, it will be understood by one of ordinary skill in
the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
15 [0031] Also, it is noted that individual embodiments may be described as a process which is
depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but
20 could have additional steps not included in a figure.
[0032] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as
25 “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or
advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar
30 to the term “comprising” as an open transition word—without precluding any additional or
other elements.
[0033] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing
7

instructions. A processor may be a general-purpose processor, a special purpose processor, a
conventional processor, a digital signal processor, a plurality of microprocessors, one or more
microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a
microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array
5 circuits, any other type of integrated circuits, etc. The processor may perform signal coding
data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
10 [0034] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-
device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited
15 to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital
assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required
20 to implement the features of the present disclosure.
[0035] As used herein, “storage unit” or “memory unit” refers to a machine or computer-
readable medium including any mechanism for storing information in a form readable by a
computer or similar machine. For example, a computer-readable medium includes read-only
25 memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical
storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
30 [0036] As used herein “interface” or “user interface refers to a shared boundary across which
two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
8

[0037] All modules, units, components used herein, unless explicitly excluded herein, may be
software modules or hardware processors, the processors being a general-purpose processor, a
special purpose processor, a conventional processor, a digital signal processor (DSP), a
5 plurality of microprocessors, one or more microprocessors in association with a DSP core, a
controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0038] As used herein the transceiver unit include at least one receiver and at least one
10 transmitter configured respectively for receiving and transmitting data, signals, information, or
a combination thereof between units/components within the system and/or connected with the system.
[0039] As discussed in the background section, the current known solutions have several
15 shortcomings. The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing method and system for managing
one or more cross-platform applications. The present disclosure provides a novel solution for
solving user interface (UI) state update issues and for managing one or more cross-platform
applications. The present disclosure provides a solution which may display an updated
20 component only for any change(s) on a stateless UI widget and the entire UI will not be update.
[0040] As used herein, cross-platform applications may be any application, program and/or
utility, which may work on different operating systems and/or platform. The different operating
systems or platforms may be such as Windows, Android, iPhone operating system (iOS),
25 Macintosh operating systems (Mac OS) and etc.
[0041] As used herein, a Model-View-ViewModel (MVVM) includes a Model, a View, and a
ViewModel components. The Model (M) represents a data repository for an application. It is
responsible for managing and storing a data, as well as providing methods to manipulate that
30 data. The View (V) represents a user interface. The View component is responsible for
displaying the data to a user and capturing their interactions. The ViewModel (VM) acts as an intermediary between the Model and the View. It transforms the data from the Model into a format that the View can use via the user interface. It also exposes commands and properties that the view can bind to the data.
9

[0042] As used herein, data access layer may represent data repository for accessing, reading, writing, and fetching the data related to the application and/or a program.
5 [0043] As used herein, logical layer may be responsible for implementing, enabling, and using
a predefined logic for operating the application and/or the program. The logical layer interacts to the data access layer based on receiving any event or input from a presentation layer.
[0044] As used herein, the presentation layer may provide an interface for interacting with the
10 user. The presentation layer may receive any input or trigger an event from the user and
transmits said input or the triggered event to the logical layer.
[0045] As used herein, stack layer architecture or stacked configuration may represent a set of layers which may have individual functionalities. The stack layer architecture may have such
15 as, but not limited to, a three-layer architecture – the presentation layer, the logic layer and the
data access layer. The three layer of the stack layer architecture may be present on top of each-other in desired order of execution. For example, in the three-layer architecture i.e. the stack layer architecture, the presentation layer may be present on top, followed by the logical layer, and finally the data access layer at the bottom. The three layers are configured in a stacked
20 architecture and may communicate with each-other and may share necessary information for
the data processing during usage of the application and/or the program. Further, the one or more layers of the stack layer architecture may be a customizable layer. Furthermore, the one or more layers from of the stack layer architecture are encapsulated within their corresponding class providing a clear separation of concerns, so that individual layer may modify and maintain
25 independently. In an exemplary aspect, the one or more layers may be implemented in a model-
view and view model (MVVM) based on the stack layer architecture.
[0046] As used herein in an exemplary aspect, the present system and method provides an
event driven architecture combined with a singleton pattern. The singleton pattern may be used
30 for creating an object of a particular class in the application, so throughout the lifecycle of that
particular application, it should be created only once and may be used throughout the life cycle of the application. The singleton pattern may be a design pattern that enables the instantiation of the class to a singular instance. The Singleton pattern provides a global point of access to the layer instances. When a layer needs to interact with another layer, it retrieves the instance
10

of that layer through the static method defined in the corresponding singleton class. This
ensures that all layers access the same instance of a particular layer, maintaining consistency
and centralized control. Hence, the memory consumption for creating the objects or for creating
the data is less as compared to the current known methods. The Singleton pattern ensures that
5 only a single instance of each layer is used, making it easier to manage and control the overall
system behaviour.
[0047] As used herein, “widget” may represent an application program or utility that displays
information and provides interaction between the user and the application for use. The widget
10 may be a stateless widget or a stateful widget. The stateless widget may be immutable and
cannot be changed after creation. In an exemplary aspect, the state of the stateless widget may be such as, but not limited to an icon, a text, and the like. Whereas the stateful widget’s state may be changed in real-time.
15 [0048] In an exemplary aspect of the present disclosure, the present method and system, with
combining the stack layer architecture with the singleton design pattern, may have following functionalities as:
a) Layer definition: Defining individual layers of functionality in the application. Each layer
20 should have a specific task or purpose, such as presentation/UI, business logic layer, data
access layer, etc. Each layer may be encapsulated within its own class.
b) Singleton Pattern Implementation: Implementing the Singleton pattern in each layer (such
as presentation/UI layer, business logic layer and data access layer) for ensuring that only
25 one instance of each layer is created and accessed globally. This can be achieved by creating
a private constructor, a static method to access the instance, and a static variable to hold the single instance within each layer class. The private constructors are used to control object instantiation and can only be called within the class. The private constructor may use in singleton design pattern. The singleton design pattern may ensure that a class can only have
30 one instance and provide a global point of access to that instance. In the singleton design
pattern, the static method is commonly used to manage the creation and access to the single instance and the instance is stored in the static variable.
11

c) Layer Stacking: Stack the layers on top of each other in the desired order of execution. The
order may vary based on the specific requirements of your application. For example, in a
typical three-layer architecture, you may have the presentation layer on top, followed by
the business logic layer, and finally the data access layer at the bottom.
5
d) Layer Communication: Each layer should communicate with each-other through well-
defined interfaces and/or contracts, which enables loose coupling and allows for easier
maintenance and future changes. For example, for MVVM model, the View Model (VM)
layer acts as an intermediary interface between the Model layer and the View layer for
10 presentation of UI use case. Each layer has defined separate and independent functioning
and logics. The loose coupling facilitates strict separation between components or layers so that each layer or component may modified or maintained individually/ separately easily without impacting functioning of other layers.
15 e) Dependency Injection: This functionality helps to decouple the lower-level layers to the
higher-level layers and simplifies testing and configuration. For example, the presentation or UI layer, business logic layer, and data access layer may modify and maintain individually and separately, which simplifies and makes easier to test and configuration updates of application.
20
f) Encapsulation and Modularity: Each layer is encapsulated within its own class, providing a clear separation of concerns. This encapsulation enables modularity, making it easier to understand, modify, and maintain individual layers independently.
25 g) Singleton Access: The Singleton pattern provides a global point of access to the layer
instances. When a layer needs to interact with another layer, it retrieves the instance of that layer through the static method defined in the corresponding Singleton class. This ensures that all layers access the same instance of a particular layer, maintaining consistency and centralized control.
30
h) Scalability and Flexibility: The stack layer architecture allows for scalability by adding or removing layers as per the application requirements. The Singleton pattern ensures that only a single instance of each layer is used, making it easier to manage and control the overall system behaviour.
12

[0049] However, there may be add/define or modify more functionalities or logics, as per need in stack layer architecture.
5 [0050] Hereinafter, exemplary embodiments of the present disclosure will be described with
reference to the accompanying drawings.
[0051] FIG. 1 illustrates an exemplary block diagram of a computing device [100] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [100] may also implement a method for managing one or more cross-platform applications utilising the system. In another implementation, the computing device [100] itself implements the method for managing the one or more cross-platform applications using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0052] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a processor [104] coupled with bus [102] for processing information. The processor [104] may be, for example, a general-purpose
20 microprocessor. The computing device [100] may also include a main memory [106], such as
a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The main memory [106] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [104]. Such
25 instructions, when stored in non-transitory storage media accessible to the processor [104],
render the computing device [100] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
30
[0053] A storage device [11], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED
13

(OLED) display, etc. for displaying information to a computer user. An input device [114],
including alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [102] for communicating information and command selections to the processor [104].
Another type of user input device may be a cursor controller [116], such as a mouse, a trackball,
5 or cursor direction keys, for communicating direction information and command selections to
the processor [104], and for controlling cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
10 [0054] The computing device [100] may implement the techniques described herein using
customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104]
15 executing one or more sequences of one or more instructions contained in the main memory
[106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be
20 used in place of or in combination with software instructions.
[0055] The computing device [100] also may include a communication interface [118] coupled to the bus [102]. The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122]. For example, the
25 communication interface [118] may be an integrated services digital network (ISDN) card,
cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [118] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the
30 communication interface [118] sends and receives electrical, electromagnetic, or optical signals
that carry digital data streams representing various types of information.
[0056] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the communication interface [118].
14

In the Internet example, a server [130] might transmit a requested code for an application
program through the Internet [128], the ISP [126], the local network [122], host [124] and the
communication interface [118]. The received code may be executed by the processor [104] as
it is received, and/or stored in the storage device [110], or other non-volatile storage for later
5 execution.
[0057] Referring to FIG. 2, an exemplary block diagram of a system [200] for managing one or more cross-platform applications, is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one data access
10 layer [202], at least one logical layer [204] and at least one presentation layer [206]. The data
access layer [202] further comprises at least one data sources [202a], at least one translator unit [202b], and at least one view model [202c]. Further the view model [202c] is configured for representation of UI use cases. Further, the logical layer [204] comprises at least one logic unit [204a] and at least one use case unit [204b]. Furthermore, the presentation layer [206]
15 comprises at least one stateless user interface (UI) widget [206a]. Also, all of the components/
units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise multiple such units or the system [200] may comprise any such numbers of said
20 units, as required to implement the features of the present disclosure. Further, in an
implementation, the system [200] may be present in a user device to implement the features of the present disclosure. The system [200] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [200] may reside in a server or a network entity. In yet
25 another implementation, the system [200] may reside partly in the server/ network entity and
partly in the user device.
[0058] The system [200] is configured for managing the one or more cross-platform
applications, with the help of the interconnection between the components/units of the system
30 [200].
[0059] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these
15

units for clarity, it is recognized that various configurations and combinations thereof are within
the scope of the disclosure. The functionality of specific units as disclosed in the disclosure
should not be construed as limiting the scope of the present disclosure. Consequently,
alternative arrangements and substitutions of units, provided they achieve the intended
5 functionality described herein, are considered to be encompassed within the scope of the
present disclosure.
[0060] In order to manage the one or more cross-platform applications, the one or more data sources [202a] of the data access layer [202] is configured to store event-based data.
[0061] As used herein "event-based data" refers to a pattern where the flow of information and actions within a system are driven by events. The event-based data represent one or more occurrences or one or more changes in state that are significant to the functioning of the application. The Event-based data architecture typically involves an event generation, an event handling, an asynchronous processing, and an event sourcing.
[0062] As used herein “event generation” refers to one or more events that are triggered by one
or more specific actions or one or more changes within a system, such as one or more user
interactions, one or more sensor readings, or one or more updates from one or more external
20 systems.
[0063] As used herein “event handling” signifies that upon the event generation, the one or
more events are captured and processed by one or more designated event handlers or one or
more listeners. The one or more designated event handlers or one or more listeners respond to
25 the one or more events by executing one or more predefined logic or one or more workflows.
[0064] As used herein “asynchronous processing” refers to a process wherein the one or more
events are processed asynchronously, which allows the system to continue functioning without
waiting for one or more immediate responses to each event to promote scalability and
30 responsiveness.
[0065] As used herein “event sourcing” refers to a process wherein the event-based data may also involve capturing and storing every state change as an event to provide a detailed audit
16

trail of system behaviour and supports one or more features like replaying events for debugging or rebuilding system state.
[0066] For Example: In an application such as mobile application or mobile web application:
5
[0067] Event: A user clicks a button to submit a form.
[0068] Event Handler: An event handler listens for the "submit" event on the form element.
When triggered, it collects form data, performs validation, and submits it to a server via an API
10 call.
[0069] Asynchronous Processing: The UI remains responsive while waiting for the server response, as the event handler manages this process asynchronously.
15 [0070] Further, the translator unit [202b] of the data access layer [202] is configured to extract
the event-based data from the one or more data sources [202a]. Furthermore, the translator unit [202b] of the data access layer [202] is configured to generate an event-based data model based on the event-based data.
20 [0071] In an exemplary aspect, the one or more data sources [202a] may be at least one of a
storage unit, a database and/or a server. Further, the data source [202a] is configured to store event-based data which may depend on implementation of an application, a program and/or use cases scenarios. For example, the event data of a particular event may be different for a desktop application, a mobile application, a web application, or for usages of applications, etc.
25 The event data may corresponds to any update event, change event or a modification event that
may associated with the application. In an implementation, the event data may corresponds to user interaction with the application (for example mobile application, web application) in any form such as a touch interaction, a click interaction, a press interaction, a text input interaction and the like. The user may interact via a user interface (UI) based on a device and an application
30 type such as the application is the mobile application or the web application. In an exemplary
aspect, the UI may be a part of the stateless UI widget [206a] of the presentation layer [206a]. The user interaction with the UI may trigger change in state of the application, which is received by the data access layer [202].
17

[0072] Further, the one or more data sources [202a] of the data access layer [202] may store such as user interaction data and state change of the application data as an event-based data. In an exemplary aspect, the translator unit [202b] may be an application program interface (API) or a processor. 5
[0073] The translator unit [202b] may extract the event-based data as a raw data from the one
or more data sources [202a]. The translator unit [202b] may generate event-based data model
from the event-based data. For example, the translator unit [202b] may generate for employee-
employer use case for the update event- an employee model; for mobile application use case
10 for the update event - an application development model etc.
[0074] Further, the use case unit [204b] of the logical layer [204] is configured to store one or more uses cases.
15 [0075] Further, the logic unit [204a] of the logical layer [204] is communicatively attached
with the translator unit [202b] of the data access layer [202] and use case unit [204b] of logical layer [204]. The logic unit [204a] of the logical layer [204] is configured to receive the event-based data model from the translator unit [202b]. Further, the logic unit [204a] of the logical layer [204] is configured to extract the one or more use cases from the use case unit [204b]
20 based on the received event-based data model from the translator unit [202b]. Thereafter, the
logic unit [204a] of the logical layer [204] is configured to identify a requisite data based on the event-based data model and the one or more use cases.
[0076] The use case unit [204b] of the logical layer [204] may store one or more use cases or
25 scenarios such as, but not limited to, the employee-employer use case, the application
development use case and an application state modification use case, etc. In an exemplary
aspect, the one or more-use cases correspond to a user interface (UI) representation of the raw
data for one or more particular events. The one or more particular events may be also triggered
based on the user interaction via the UI. The one or more particular events may associate with
30 such as, but not limited to, state change, icon change for an application.
[0077] Further, logic unit [204a] of the logical layer [204] is configured to receive the event-based data model, such as, but not limited to, the employee model, the mobile application update model and an application development model from the translator unit [202b] based on
18

the employee-employer use case, the application development use case and an application state
modification use case. The data access layer [202], the logical layer [204] and the presentation
layer [206] are present in a stacked and event-based architecture and may be configured to
communicate with each-other. The event-based data model may provide the requisite data
5 based on the one or more-use cases. The requisite data may correspond to a particular data that
is required as per the one or more-use cases, such as, but not limited to, associated with text change and icon update.
[0078] In an exemplary use case in accordance with the present disclosure, such as the employee-employer use case, the logic unit [204a] may identify for the employee model, the event-based data such as an address update event, in said exemplary use case the requisite data may be identified as a present address for one or more employees. In an aspect of the present disclosure, the requisite data may be a single or a group of data (for example, a first name, a last name, a present address, a permanent address for the employee model) based on implementation of usage of the application. In an exemplary aspect of the present disclosure, such as the application state modification use case, the logic unit [204a] may identify for the application development model, the event-based data as an update event, and the requisite data as a state change, a change information, a change display for the application.
20 [0079] Further, the stateless user interface (UI) widget [206a] of the presentation layer [206]
is configured to display the requisite data. The presentation layer [206] of the system [200] may display on the stateless UI widget the requisite data (such as the present address, the state change, the change information, etc. on the application) with that updated component. Further, in an implementation of the present disclosure, the presentation layer [206] of the system [200]
25 may display on the stateless UI widget the requisite data with updated component only wherein
the entire UI is not updated. In an aspect, the stateless UI widgets refer to a graphical component for interaction that are immutable after creation i.e., changes of any data, variables icons, buttons cannot take place after the creation. Further, in an implementation of the present disclosure, the presentation layer [206] of the system [200] may display on the stateless UI
30 widget the requisite data with updated component wherein the entire UI is updated.
[0080] In an exemplary aspect of the present disclosure, one or more layers i.e., the data access layer [202], the logical layer [204] and the presentation layer [206] of the system [200] are customizable and are configured to communicate with each other. The system [200] may add,
19

update, modify and delete a functionality associated with the one or more layers (e.g., data
access layer [202], logical layer [204] and presentation layer [206]) based on the use cases and
the event data model. This customization of the functionality of the layers enhances the
flexibility of adding services or features and development of the application.
5
[0081] In an exemplary aspect, the one or more layers of the system [200] are encapsulated
within their corresponding class. Each layer of the one or more layers is encapsulated within
its own class (such as business logic in view model layer), providing a clear separation of
concerns. This encapsulation enables modularity, making it easier to understand, modify, and
10 maintain each layer independently.
[0082] As used herein “Layers” refers to a logical division of functionality within an application. Such as a presentation/UI layer, a business logic layer, and a data access layer.
15 [0083] As used herein “Encapsulation” refers to bundling the data (state) and behaviour that
operate on the data into a single unit (a class) to hide the internal workings of the class from the outside world, allowing controlled access to the class's components.
[0084] As used herein “Corresponding Class” refers to a design construct where one or more
20 layers of a stack architecture (such as a presentation layer, a business logic layer, or a data
access layer) are encapsulated within dedicated classes. Each class is responsible for
implementing and managing the operations and data pertinent to its layer, promoting a clear
separation of concerns. This design enables independent modification and maintenance of
individual layers, enhancing code reusability, scalability, and maintainability within an
25 architecture of the application.
[0085] For example: in a typical mobile application or a mobile web application scenario: The
presentation layer could be encapsulated within classes responsible for rendering UI
components, handling user interactions, and managing client-side state. Further the business
30 logic layer classes in this layer would encapsulate the business rules, workflows, and
computations specific to the application's domain. Furthermore, the data access layer classes here would manage interactions with databases or external data sources, handling CRUD operations and ensuring data integrity. Thus, the class of each layer is designed to interact with
20

each other through well-defined interfaces, minimizing dependencies between layers and allowing for independent development, testing, and evolution of each component.
[0086] The present disclosure provides an event-driven architecture for managing one or more
5 cross-platform applications. In an exemplary aspect, one or more layers of the system [200] are
implemented model-view and view model (MVVM) based stack layer architecture. In an exemplary aspect, the events such as user interactions (e.g., button clicks, touch, text input) may trigger a change in the state of the application. The one or more events triggered by the UI widget, or components may drive the state change(s) and may communicate to data access
10 layer [202], which may trigger the application programming interface (API) to provide the raw
data. Further, the raw data then may convert into event models. Furthermore, the event model may be mapped with use cases to provide the updated state or change data to the UI widget or component. The event-based data models may provide specific data according to the use case, whole data may not provide to the UI widget or component.
15
[0087] Referring to FIG. 3 an exemplary method flow diagram [300] for managing one or more cross-platform applications, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement
20 the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step
[302].
[0088] At step [304], the method [300] as disclosed by the present disclosure comprises
extracting, by a translator unit [202b] of a data access layer [202], event-based data from one
25 or more data sources [202a].
[0089] In an exemplary aspect, the one or more data sources [202a] may be at least one of a
storage unit, a database and/or a server. Further, the one or more data sources [202a] is
configured to store an event-based data which may depend on implementation of an
30 application, a program and/or use cases scenarios. For example, the event data of a particular
event may be different for a desktop application, a mobile application, a web application, or for usages of applications, etc. The event data may correspond to any update event, change event or a modification event that may associated with the application. In an implementation, the event data may correspond to a user interaction with the application (for example mobile
21

application, web application) in any form such as a touch interaction, a click interaction, a press interaction, a text input interaction and the like. The user may interact via a user interface (UI) based on a device and an application type such as the application is a mobile application or a web application. 5
[0090] In an exemplary aspect, the UI may be a part of the stateless UI widget [206a] of the presentation layer [206a]. The user interaction with the UI may trigger change in state of the application, which is received by the data access layer [202].
10 [0091] The one or more data sources [202a] of the data access layer [202] may store such as,
but not limited to, user interaction data and state change of the application data as an event-based data. The translator unit [202b] of the data access layer [202] is configured to extract the event-based data from the one or more data sources [202a].
15 [0092] In an exemplary aspect, the translator unit [202b] may be an application program
interface (API) or a processor. The translator unit [202b] may extract the event-based data as a raw data from the one or more data sources [202a].
[0093] As used herein "event-based data" refers to a pattern where the flow of information and
20 actions within a system are driven by events. The event-based data represent one or more
occurrences or one or more changes in state that are significant to the functioning of the application. The Event-based data architecture typically involves an event generation, an event handling, an asynchronous processing, and an event sourcing.
25 [0094] As used herein “event generation” refers to one or more events that are triggered by one
or more specific actions or one or more changes within a system, such as one or more user interactions, one or more sensor readings, or one or more updates from one or more external systems.
30 [0095] As used herein “event handling” signifies that upon the event generation, the one or
more events are captured and processed by one or more designated event handlers or one or more listeners. The one or more designated event handlers or one or more listeners respond to the one or more events by executing one or more predefined logic or one or more workflows.
22

[0096] As used herein “asynchronous processing” refers to a process wherein the one or more events are processed asynchronously, which allows the system to continue functioning without waiting for one or more immediate responses to each event to promote scalability and responsiveness. 5
[0097] As used herein “event sourcing” refers to a process wherein the event-based data may also involve capturing and storing every state change as an event to provide a detailed audit trail of system behaviour and supports one or more features like replaying events for debugging or rebuilding system state. 10
[0098] For Example: In an application such as mobile application or mobile web application:
[0099] Event: A user clicks a button to submit a form.
15 [0100] Event Handler: An event handler listens for the "submit" event on the form element.
When triggered, it collects form data, performs validation, and submits it to a server via an API call.
[0101] Asynchronous Processing: The UI remains responsive while waiting for the server
20 response, as the event handler manages this process asynchronously.
[0102] Next, at step [306], the method [300] as disclosed by the present disclosure comprises generating, by the translator unit [202b] of the data access layer [202], an event-based data model based on the event-based data.
25
[0103] The translator unit [202b] of the data access layer [202] may generate the event-based data model based on the event-based data. In an exemplary aspect, the translator unit [202b] of the data access layer [202] may generate the event-based data model from the event-based data. For example, the translator unit [202b] may generate for employee-employer use case for the
30 update event - an employee model; for mobile application use case for the update event - an
application development model etc.
[0104] Next, at step [308], the method [300] as disclosed by the present disclosure comprises
receiving, at a logic unit [204a] of a logical layer [204], the event-based data model from the
35 translator unit [202b].
23

[0105] The present disclosure encompasses that the logical layer [204] comprising the logic
unit [204a] and a use case unit [204b]. The use case unit [204b] of the logical layer [204] may
store one or more use cases or scenarios such as, but not limited to, an employee-employer use
5 case, an application development use case and an application state modification use case and
the like. In an exemplary aspect, one or more-use cases correspond to a user interface (UI) representation of the raw data for one or more particular events. The one or more particular events may be also triggered based on the user interaction via the UI. The one or more particular events may associate with such as, but not limited to, state change, icon change for an
10 application. Further, logic unit [204a] or business logic unit of the logical layer [204] is
configured to receive the event-based data model, such as, but not limited to, the employee model, the mobile application update model, and an application development model from the translator unit [202b] based on the employee-employer use case, the application development use case and an application state modification use case. The data access layer [202], the logical
15 layer [204] and the presentation layer [206] are present in stacked and event-based architecture
and may be configured to communicate with each-other.
[0106] Next, at step [310], the method [300] as disclosed by the present disclosure comprises extracting, by the logic unit [204a] of the logical layer [204], one or more use cases.
[0107] The logic unit [204a] of logical layer [204] may extract from the use case unit [204b] one or more use cases, such as, the employee-employer use case, the application state modification use case and the like based on the received event-based data model from the translator unit [202b].
[0108] Next, at step [312], the method [300] as disclosed by the present disclosure comprises identifying, by the logic unit [204a] of the logical layer [204], a requisite data based on the event-based data model and the one or more use cases.
30 [0109] The logic unit [204a] of logical layer [204] may identify the requisite data based on the
event-based data model and the one or more use cases. The event-based data model may provide the requisite data based on the one or more-use cases. The requisite data may correspond to a particular data required as per the one or more-use cases such as, but not limited to, associated with text change and icon update.
24

[0110] In an exemplary use case in accordance with present disclosure, such as the employee-
employer use case, the logic unit [204a] may identify for the employee model, the event-based
data such as an address update event, in said exemplary use case the requisite data may be
5 identified as a present address for one or more employees. In an aspect of the present disclosure,
the requisite data may be a single or a group of data (for example, a first name, a last name, a
present address, a permanent address for the employee model) based on implementation of
usage of the application. In an exemplary aspect of the present disclosure, such as the
application state modification use case, the logic unit [204a] may identify for the application
10 development model, the event-based data as an update event, and the requisite data as a state
change, a change information, a change display for the application.
[0111] Next, at step [314], the method [300] as disclosed by the present disclosure comprises displaying, by a stateless UI widget [206a] of a presentation layer [206], the requisite data.
15
[0112] The presentation layer [206] comprising a stateless user interface widget [206a] configured to display the requisite data. The presentation layer [206] may display on stateless UI widget requisite data (such as the present address, the state change, the change information, etc. on the application) with that updated component only wherein the entire UI is not updated.
20 the stateless UI widgets refers to a graphical component for interaction that are immutable after
creation i.e., changes of any data, variables icons, buttons cannot take place. Further, in an implementation of the present disclosure, the presentation layer [206] may display on the stateless UI widget the requisite data with updated component only wherein the entire UI is not updated. Further, in another implementation of the present disclosure, the presentation layer
25 [206] may display on the stateless UI widget the requisite data with updated component
wherein the entire UI is updated.
[0113] In an exemplary aspect of the present disclosure, one or more layers i.e., the data access
layer [202], the logical layer [204] and the presentation layer [206] are customizable and are
30 configured to communicate with each other. Further, one or more functionalities like addition,
updation, modification, deletion may be conducted or implemented in the one or more layers (e.g., data access layer [202], logical layer [204] and presentation layer [206]) based on the user case and the event data model. This customization of the functionality of the layers enhances the flexibility of adding services or features and development of the application.
25

[0114] In an exemplary aspect, the one or more layers are encapsulated within their
corresponding class. Each layer of the one or more layers is encapsulated within its own class
(such as business logic in view model layer), providing a clear separation of concerns. This
5 encapsulation enables modularity, making it easier to understand, modify, and maintain each
individual layers independently.
[0115] As used herein “Layers” refers to a logical division of functionality within an application. Such as a presentation/UI layer, a business logic layer, and a data access layer. 10
[0116] As used herein “Encapsulation” refers to bundling the data (state) and behaviour that operate on the data into a single unit (a class) to hide the internal workings of the class from the outside world, allowing controlled access to the class's components.
15 [0117] As used herein “Corresponding Class” refers to a design construct where one or more
layers of a stack architecture (such as a presentation layer, a business logic layer, or a data access layer) are encapsulated within dedicated classes. Each class is responsible for implementing and managing the operations and data pertinent to its layer, promoting a clear separation of concerns. This design enables independent modification and maintenance of
20 individual layers, enhancing code reusability, scalability, and maintainability within an
architecture of the application.
[0118] For example: in a typical mobile application or a web application scenario: The presentation layer could be encapsulated within classes responsible for rendering UI
25 components, handling user interactions, and managing client-side state. Further the business
logic layer classes in this layer would encapsulate the business rules, workflows, and computations specific to the application's domain. Furthermore, the data access layer classes here would manage interactions with databases or external data sources, handling CRUD operations and ensuring data integrity. Thus, the class of each layer is designed to interact with
30 each other through well-defined interfaces, minimizing dependencies between layers and
allowing for independent development, testing, and evolution of each component.
[0119] The present disclosure provides an event-driven architecture for managing one or more cross-platform applications. In an exemplary aspect, one or more layers are implemented
26

model-view and view model (MVVM) based stack layer architecture. In an exemplary aspect,
the events such as user interactions (e.g., button clicks, touch, text input) may trigger a change
in the state of the application. The events triggered by the UI widget or components may drive
the state change(s) and may communicate to data access layer [202], which may trigger the
5 application programming interface (API) to provide raw data. Further, the raw data then may
convert into event models. Furthermore, the event model may be mapped with use cases to provide the updated state or change data to UI widget or component. The event-based data models may provide specific data according to the use case, whole data may not provide to the UI widget or component. 10
[0120] Thereafter, the method [300] terminates at step [316].
[0121] The present disclosure further discloses a user equipment (UE) for managing one or
more cross-platform applications, the UE comprising a processor configured to: extract an
15 event-based data from one or more data sources [202a]; generate an event-based data model
based on the event-based data; receive the event-based data model from a translator unit [202b]; extract one or more use cases; identify a requisite data based on the event-based data model and the one or more-use cases; and display the requisite data to a user.
20 [0122] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for managing one or more cross-platform applications, the instructions including executable code, the executable code when executed, may cause: a translator unit [202b] of a data access layer [202] to extract event-based data from one or more data sources [202a]; the translator unit [202b] of the data access layer [202] to generate an
25 event-based data model based on the event-based data; a logic unit [204a] of a logical layer
[204] to receive the event-based data model from the translator unit [202b]; the logic unit [204a] of the logical layer [204] to extract one or more use cases; the logic unit [204a] of the logical layer [204] to identify a requisite data based on the event-based data model and the one or more use cases; and a stateless UI widget [206a] of a presentation layer [206] to display the
30 requisite data.
[0123] In an exemplary implementation of the present disclosure, for employee and employer situation, to display an information of a first name, a last name, a present address, and a permanent address of the employee is one of use case example. If there is requirement of
27

updating something on this particular use case. First there is need of calling an application
programming interface (API) to get a data so it may hold the first name and the last name, and
that data need to be converted into a model like such as an employee model. That employee
model may be given to a data source, then data source gives it to a logic entity. The logic entity
5 have all the information about the employee first name, the last name, and the address i.e. the
present address and the permanent address, along with other employee information such as a
salary information or an attendance information. For specific use cases to show only a specific.
information like the first name and the last name only, the logic entity extracts out only intended
information(s) i.e., the first name and the last name and generates at least one use case. This
10 use case is given to a stateless user interface (UI). Only that component may get updated, not
the whole UI get updated.
[0124] As is evident from the above, the present disclosure provides a technically advanced solution for efficient system and method for solving a UI state update issues and for managing
15 one or more cross-platform applications. The present system and method require less memory
consumption and performance of application may improve. The present disclosure provides an efficient system and method for solving the user interface (UI) state update issues and for managing one or more cross-platform applications. The present disclosure provides a method and system, which may display on the stateless UI widget updated component only for any
20 change(s), wherein the entire UI is not updated. Further, the present disclosure provides the
stack layer architecture with singleton pattern, which allows for scalability by adding or removing layers as per the application requirements. The Singleton pattern ensures that only a single instance of each layer is used, making it easier to manage and control the overall system behaviour.
25
[0125] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in
30 the art, whereby it is to be understood that the foregoing descriptive matter to be implemented
is illustrative and non-limiting.
28

We Claim:
1. A system for managing one or more cross-platform applications, the system
comprising:
- a data access layer [202] comprising:
o one or more data sources [202a] configured to store an event-based data; o a translator unit [202b] configured to:
▪ extract the event-based data from the one or more data sources [202a], and
▪ generate an event-based data model based on the event-based data;
- a logical layer [204] comprising:
o a use case unit [204b] configured to store one or more uses cases, and o a logic unit [204a] configured to:
▪ receive the event-based data model from the translator unit [202b],
▪ extract the one or more use cases, and
▪ identify a requisite data based on the event-based data model and the one or more use cases; and
- a presentation layer [206] comprising:
o a stateless user interface widget [206a] configured to display the requisite data.
2. The system as claimed in claim 1, wherein the event-based data is extracted as a raw data from the one or more data sources [202a].
3. The system as claimed in claim 1, wherein the one or more-use cases correspond to a user interface (UI) representation of a raw data for one or more particular events.
4. The system as claimed in claim 1, wherein the event-based data model provides the requisite data based on the one or more-use cases.
5. The system as claimed in claim 1, wherein the requisite data corresponds to a particular data required as per the one or more-use cases.
6. The system as claimed in claim 1, wherein the data access layer [202], the logical layer [204] and the presentation layer [206] are configured to communicate with each other.

7. The system as claimed in claim 1, wherein the data access layer [202], the logical layer [204], and the presentation layer [206] are configured to operate in a stacked configuration.
8. The system as claimed in claim 1, wherein one or more layers are customizable.
9. The system as claimed in claim 1, wherein the one or more layers are implemented model-view and view model (MVVM) based stack layer architecture.
10. A method for managing one or more cross-platform applications, the method comprising:

- extracting, by a translator unit [202b] of a data access layer [202], an event-based data from one or more data sources [202a];
- generating, by the translator unit [202b] of the data access layer [202], an event-based data model based on the event-based data;
- receiving, at a logic unit [204a] of a logical layer [204], the event-based data model from the translator unit [202b];
- extracting, by the logic unit [204a] of the logical layer [204], one or more use cases;
- identifying, by the logic unit [204a] of the logical layer [204], a requisite data based on the event-based data model and the one or more use cases; and
- displaying, by a stateless UI widget [206a] of a presentation layer [206], the requisite data.

11. The method as claimed in claim 10, wherein the event-based data is extracted as a raw data from the one or more data sources.
12. The method as claimed in claim 10, wherein the one or more-use cases correspond to an user interface (UI) representation of a raw data for one or more particular events.
13. The method as claimed in claim 10, wherein the event-based data model provides the requisite data based on the one or more-use cases.

14. The method as claimed in claim 10, wherein the requisite data corresponds to a particular data required as per the one or more-use cases.
15. The method as claimed in claim 10, wherein the data access layer [202], the logical layer [204] and the presentation layer [206] are configured to communicate with each other.
16. The method as claimed in claim 10, wherein the data access layer [202], the logical layer [204], and the presentation layer [206] are configured to operate in a stacked configuration.
17. The method as claimed in claim 10, wherein one or more layers are customizable.
18. The method as claimed in claim 10, wherein the one or more layers are implemented model-view and view model (MVVM) based stack layer architecture.
19. A user equipment (UE) for managing one or more cross-platform applications, the UE comprising a processor configured to:
extract an event-based data from one or more data sources [202a],
generate an event-based data model based on the event-based data,
receive the event-based data model from a translator unit [202b],
extract one or more use cases,
identify a requisite data based on the event-based data model and the one or more-use
cases, and.
display the requisite data to a user.