1. A method (300) for managing co-development of applications, the method (300) comprising:
receiving (305), by a server (105), a request corresponding to a first user to edit a Graphical
User Interface (GUI) of a development environment for an application, wherein the application
5 comprises a plurality of pages, and wherein the plurality of pages comprises a plurality of blocks;
retrieving (310), by the server (105), lock data of each of the plurality of blocks and a first
set of user privileges associated with the first user, wherein the lock data of each block comprises
a lock status, and wherein the lock status is indicative of whether a corresponding block is in a
locked condition or an unlocked condition;
10 determining (315), by the server (105), editability of the first user to each of the plurality
of blocks based on the lock data of each of the plurality of blocks and the first set of user privileges;
and
rendering (320), by the server (105), the GUI on a first user device associated with the first
user, based on the editability.
15
2. The method (300) as claimed in claim 1, comprising:
receiving (505), by the server (105) from the first user device associated with the first user,
a selection command to edit a first block of the plurality of blocks in a first page of the plurality
of pages, wherein a lock status of the first block is indicative of the first block being in the unlocked
20 condition; and
generating (510), by the server (105), a locking request for the first block based on the
selection command.
3. The method (300) as claimed in claim 2, comprising:
25 validating (515), by the server (105), the locking request through an Application
Programming Interface (API); and
upon successfully validating,
modifying (520), by the server (105), the lock status of the first block to indicate
that the first block is in the locked condition;
30 identifying (525), by the server (105), the first user as an active user corresponding
to the first block with the modified lock status; and
51
rendering (530), by the server (105), the first block as editable by the first user
device associated with the first user.
4. The method (300) as claimed in claim 3, comprising rendering (535), by the server (105), the
5 first block as non-editable by a second user device associated with a second user, wherein the first
user and the second user are concurrently editing the development environment.
5. The method (300) as claimed in claim 3, comprising:
detecting (605), by the server (105), an engagement of the first user with the first block;
10 and
classifying (610), by the server (105), the first user as one of an active user or an inactive
user of the first block based on the detected engagement.
6. The method (300) as claimed in claim 5, wherein detecting (605) the engagement of the first
15 user with the first block is based on ping messages received from the first user device, and wherein
the method (300) comprises:
initiating (615), by the server (105), a timer based on the engagement of the first user,
wherein the timer comprises a first predefined expiration time period;
identifying (620), by the server (105), the first user as the active user corresponding to the
20 first block when at least one ping message is received within the first predefined expiration time
period; and
identifying (625), by the server (105), the first user as the inactive user corresponding to
the first block when at least one ping message is not received within the first predefined expiration
time period.
25
7. The method (300) as claimed in claim 5, comprising:
when the first user is classified as the inactive user corresponding to the first block, sending
(705), by the server (105) on the first user device, a first notification indicating an expiration of
the first predefined expiration time period.
30
8. The method (300) as claimed in claim 7, comprising:
52
receiving (710), by the server (105) from the first user device, a response to the first
notification within a second predefined expiration time period;
in response to receiving the response to the first notification from the first user device
associated with the first user, identifying (715), by the server (105), the first user as the active user;
5 and
maintaining (720), by the server (105), the lock status of the first block to indicate that the
first block is in the locked condition after receiving the response to the first notification within the
second predefined expiration time period.
10 9. The method (300) as claimed in claim 7, comprising:
modifying (725), by the server (105), the lock status of the first block to indicate that the
first block is in the unlocked condition when a response to the first notification from the first user
device is not received within a second predefined expiration time period.
15 10. A system (200) for managing co-development of applications, the system (200) comprising:
a processing circuitry (205); and
a memory (210) communicatively coupled to the processing circuitry (205), wherein the
memory (210) stores processor instructions, which when executed by the processing circuitry
(205), cause the processing circuitry to (205):
20 receive (305) a request corresponding to a first user to edit a Graphical User
Interface (GUI) of a development environment for an application, wherein the application
comprises a plurality of pages, and wherein the plurality of pages comprises a plurality of
blocks;
retrieve (310) lock data of each of the plurality of blocks and a first set of user
25 privileges associated with the first user, wherein the lock data of each block comprises a
lock status, and wherein the lock status is indicative of whether a corresponding block is
in a locked condition or an unlocked condition;
determine (315) editability of the first user to each of the plurality of blocks based
on the lock data of each of the plurality of blocks and the first set of user privileges; and
30 render (320) the GUI on a first user device associated with the first user based on
the editability.