Page 1 of 2

ZX App - ZXDB for Android

Posted: Thu Jul 05, 2018 12:56 am
by Turrican
Hi all.
A first version of an Android app using the ZXDB API to make searchs.
Very early version that has only General and Magazine Searchs (and a very ugly UI).
The Magazine list shows the cover, number and release year (it takes a time to load the cover from the host site).
General search is cool... I could find a lot of software/books that I didn´t imagine that exists. Try 'Soccer' word.
Download and install the APK (virus free).
Feel free to make comments.

I will upgrade the app soon.

https://www.dropbox.com/s/sj0ihsm5r8kyq ... p.apk?dl=0



Image

Image

Image

Re: ZX App - ZXDB for Android

Posted: Thu Jul 05, 2018 5:07 am
by PeterJ
Very nice work!

Re: ZX App - ZXDB for Android

Posted: Mon Sep 16, 2019 12:39 pm
by Turrican
Hi all.
Just to say that the app has grown since then...
It is listed in Google playstore: https://play.google.com/store/apps/deta ... boys.zxapp
Now you can:
- download software (ZX Spectrum and ZX81 files)
- download books (pdf files)
- see YouTube videos (it opens the YouTube app)
- see pictures from softwares and inlays

more to come!

Re: ZX App - ZXDB for Android

Posted: Mon Sep 16, 2019 2:23 pm
by Einar Saukas
It looks awesome!

My only suggestion for improvement is an option in "General list" to choose if user wants to see a "loading screen" or "running screen" for each title. it's nice to see all loading screens by default, but when an user is searching for some specific game without recalling its name, then showing all running screens will make it much easier to find it.

Re: ZX App - ZXDB for Android

Posted: Mon Sep 16, 2019 2:55 pm
by Turrican
Einar Saukas wrote:
Mon Sep 16, 2019 2:23 pm
It looks awesome!

My only suggestion for improvement is an option in "General list" to choose if user wants to see a "loading screen" or "running screen" for each title. it's nice to see all loading screens by default, but when an user is searching for some specific game without recalling its name, then showing all running screens will make it much easier to find it.
Hi Einar. That´s good!
I´ll implement in the future.
Thank you for suggestions!

Regards.

PS: is there a way to know which type of inlay I´m getting? Such as: inside, front, back, etc?
Thanks.

Re: ZX App - ZXDB for Android

Posted: Tue Sep 17, 2019 10:07 pm
by Einar Saukas
Turrican wrote:
Mon Sep 16, 2019 2:55 pm
Thank you for suggestions!
You are welcome!

Turrican wrote:
Mon Sep 16, 2019 2:55 pm
PS: is there a way to know which type of inlay I´m getting? Such as: inside, front, back, etc?
As a general rule, if the filename contains "_Front" or "_Back" then it's front or back, otherwise it's a full inlay (front and back together).

This rule should work most of the time, but it's not infallible. I'm planning to implement a better classification in the future, but there are over 10,000 tape inlays in ZXDB so don't expect a better solution any time soon...

Re: ZX App - ZXDB for Android

Posted: Wed Sep 18, 2019 10:13 am
by Turrican
Einar Saukas wrote:
Tue Sep 17, 2019 10:07 pm
Turrican wrote:
Mon Sep 16, 2019 2:55 pm
Thank you for suggestions!
You are welcome!

Turrican wrote:
Mon Sep 16, 2019 2:55 pm
PS: is there a way to know which type of inlay I´m getting? Such as: inside, front, back, etc?
As a general rule, if the filename contains "_Front" or "_Back" then it's front or back, otherwise it's a full inlay (front and back together).

This rule should work most of the time, but it's not infallible. I'm planning to implement a better classification in the future, but there are over 10,000 tape inlays in ZXDB so don't expect a better solution any time soon...
Ok. Thanks!

Re: ZX App - ZXDB for Android

Posted: Wed Sep 18, 2019 8:50 pm
by Stefan
Einar Saukas wrote:
Tue Sep 17, 2019 10:07 pm
Turrican wrote:
Mon Sep 16, 2019 2:55 pm
Thank you for suggestions!
You are welcome!

Turrican wrote:
Mon Sep 16, 2019 2:55 pm
PS: is there a way to know which type of inlay I´m getting? Such as: inside, front, back, etc?
As a general rule, if the filename contains "_Front" or "_Back" then it's front or back, otherwise it's a full inlay (front and back together).

This rule should work most of the time, but it's not infallible. I'm planning to implement a better classification in the future, but there are over 10,000 tape inlays in ZXDB so don't expect a better solution any time soon...
How about making it easy for the consumers - add a type and populate type based on _front / _back / full - any errors / exotic cases can be corrected manually afterwards with no pain for the consumers who can start using the normal interface directly.

Re: ZX App - ZXDB for Android

Posted: Wed Sep 18, 2019 9:59 pm
by Einar Saukas
Stefan wrote:
Wed Sep 18, 2019 8:50 pm
Einar Saukas wrote:
Tue Sep 17, 2019 10:07 pm
Turrican wrote:
Mon Sep 16, 2019 2:55 pm
PS: is there a way to know which type of inlay I´m getting? Such as: inside, front, back, etc?
As a general rule, if the filename contains "_Front" or "_Back" then it's front or back, otherwise it's a full inlay (front and back together).

This rule should work most of the time, but it's not infallible. I'm planning to implement a better classification in the future, but there are over 10,000 tape inlays in ZXDB so don't expect a better solution any time soon...
How about making it easy for the consumers - add a type and populate type based on _front / _back / full - any errors / exotic cases can be corrected manually afterwards with no pain for the consumers who can start using the normal interface directly.
That's exactly what I'm planning to do.

It seems like a very simple change, so why didn't I do it already? Well, I should probably explain this point...

Each file already has a "filetype" field, that indicates if a certain file is a "Tape image" or a "Cassette inlay", for instance. Instead of a generic "cassette inlay", it will be more useful to have "Front cassette inlay", "Back cassette inlay" and "Full cassette inlay". This way we can avoid creating one more type field that would be only useful in this specific case anyway.

However we currently have 4 filetypes for inlays: "Cassette inlay", "Compilation cassette inlay", "Covertape cassette inlay", "Re-release cassette inlay". Therefore we would to break it down into 12 new filetypes such as "Front covertape cassette inlay", "Front re-release cassette inlay", etc.

However we don't really need these current 4 filetypes. For instance, each file already has a release number, that can be used to distinguish if it's the inlay for an original release or re-release. There's no need to have different filetypes for "Cassette inlay" and "Re-release cassette inlay", this information is redundant.

However the information originally imported from WoS contained some inconsistencies. There are a few cassette inlays from the original publisher classified as "Re-release cassette inlay" and vice-versa. I'm currently working with Pavero to validate and fix these cases. Afterwards I will make the other changes I mentioned.

This case is a good example that we have been working on a lot of ZXDB improvements without any publicity about it! :)

Re: ZX App - ZXDB for Android

Posted: Thu Sep 19, 2019 12:42 pm
by StooB
Einar Saukas wrote:
Wed Sep 18, 2019 9:59 pm
For instance, each file already has a release number, that can be used to distinguish if it's the inlay for an original release or re-release.
It doesn't make sense to be associating files with release numbers when the release order is incorrect - eg. Thanatos has the Encore inlay as "Re-release cassette inlay (#1)" because the Encore re-release has the wrong year. Correcting the year to 1989 would make it into Re-release #3, but "Re-release cassette inlay (#3)" has already been given to the IBSA inlay.