It is often good for the ecosystem that we have choice of tools for a given task, so I applaud the general effort gone into this additional "Google Photos 'Clone'".
Here the challenge is to actually understand what "Google Photos" is before claiming that this is a Clone.
In order to successfully clone Google Photos, one needs:
1.- A backing storage.
2.- A web application.
3.- A mobile application (and optionally a desktop application).
4.- A data synchronization model to maintain a 2-way sync between backing storage and each locally installed application.
5.- A data model of pictures, timeline, and albums, that does not depend on where the picture is physically stored (for example, I can create an album on my phone offline, and whenever I come online the sync happens and the same album appears on the web application view).
6.- AI features (eg. face detection) sprinkled on top of the backing storage, and available on both web application and locally installed applications.
From a cursory review, this current attempt only satisfies 1 and 2.
Here the challenge is to actually understand what "Google Photos" is before claiming that this is a Clone.
In order to successfully clone Google Photos, one needs:
1.- A backing storage.
2.- A web application.
3.- A mobile application (and optionally a desktop application).
4.- A data synchronization model to maintain a 2-way sync between backing storage and each locally installed application.
5.- A data model of pictures, timeline, and albums, that does not depend on where the picture is physically stored (for example, I can create an album on my phone offline, and whenever I come online the sync happens and the same album appears on the web application view).
6.- AI features (eg. face detection) sprinkled on top of the backing storage, and available on both web application and locally installed applications.
From a cursory review, this current attempt only satisfies 1 and 2.