Please use our links: LEGO.com • Amazon
Recent discussions • Categories • Privacy Policy • Brickset.com
Brickset.com is a participant in the Amazon Services LLC Associates Program, the Amazon.com.ca, Inc. Associates Program and the Amazon EU Associates Programme, which are affiliate advertising programs designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.
As an Amazon Associate we earn from qualifying purchases.
Comments
So then I was wondering, maybe other tags were being used to store this.... would be cool! Although if API calls are needed first then someone has some work to do before you do... ;-)
Also very good to know in case I wipe and reflash my device (was planning to at some point). Can the data be backed up somehow?
Otherwise, if you're familiar with the Android SDK (unlikely I know!) you can use the backup command to backup the app + data, or just pull a copy of the db (and obviously you can restore data this way too).
What may be a better option is to take a look at Helium (https://play.google.com/store/apps/details?id=com.koushikdutta.backup&hl=en) and you can do other apps on your device at the same time.
I imagine I'll be using your app most when I'm at a store shopping and need to look up RRP. Is there a way that you can add a "calculate" button on the set description page? That way, we can see the RRP, click a calculate discount button, input sales price, and calculate the discount without leaving the app? It would be greater if you can write the set names and discounts to a temporary in-app log. That would allow a user to calculate the discounts on a bunch of sets and then decide which ones they want to actually buy.
Thank you!
I assume you're trying to determine what % of discount a set has? All phones include a calculator, but I also like to encourage everyone to do percentages in their head! It's quite easy to figure out rough percentages - 10% is the price without the last digit (10% of $10 if $1, 20% is twice that or 5% is half) with a little bit of practice anyone can get a "good enough" answer much faster in their head than typing something in.
Correct. Just trying to compute the discount off RRP.
I agree that everyone should do it in their head, but in reality, we all lean on calculators these days. :) That said, seeing a set for $100 when the pre-sales tag said $128 and the RRP says $160, means you say $60 off great!. But if I want to figure out the discount, I take 160/10 = 16. 16 + 16 = 32. Oh, "60" is close to 32 x 2 = 64, so that's not quite 40%. Turns out that sales price is a 20% discount off a 20% discount. Allowing a user to just tap a button, input $100 and have the app compute 1 - ( salesprice / RRP ) and display 37.5% would be very convenient (especially during the holidays).
Thanks in advance for considering this request! The app is extremely useful with or without the discount calculator.
@deusxanime
This request isn't unrelated or a bloatware feature request. RRP lookup is probably very high on the use cases for this app as it is way faster than using a browser to access Brickset or [email protected] This request enhances the usefulness and convenience of this app as the main time people do RRP lookups is when they are standing in a shopping aisle thinking if it's worth buying something. Determining discounts is what most people will try to do after seeing the RRP. So the core of this request is to add a button, temporary field and a math formula, "1 - (salesprice/RRP)." Not build a full-fledged calculator or invoke a call to the installed calculator and take the user out of the app. We can do that manually already. :)
sorry for being quiet lately, not had much free time. Are you still looking for import/export functionality? If so, I have a prototype version that seems to be working and I can try to do some more testing & hardening at the w/e so I can get it out.
Do you see Belgium prices on any set listings at brickset.com? (I don't but it may depend upon profile settings?) The API doesn't support these yet, but if Brickset has the data then I'm sure Huw would be up to making it available.
Re import/export, yeah, I still need to reflash my phone, haven't dared yet ;) So that would be great!
These images have grown over time and now account for about 250MB of data (luckily this is a one-time download). Are they still useful to people? I like to think of space as cheap but appreciate not everyone has a large internal drive or can add an SD card to their device.
If the images are removed, the app will shrink to < 5MB but thumbnails will not show until they've been seen and cached (the last 30MB are cached IIRC, which is approx 2000 images) but this can lead to a negative user experience when browsing for sets offline when images haven't been cached. However it's over 5 years since I first wrote the app and free Wi-Fi is now available in most shopping malls, removing some of the need for a full offline experience.
Obviously only the images would be removed, the rest of myBrickset's offline functionality would remain unchanged.
If people like the images, I can maybe try to find a way to reduce them. There's no easy way to only "recent" images in the app, but I'm sure I could write something to do this (hmm, have I just talked myself into more work again?!).
Even so, I don't think it would be a big problem to deal with no images in the unlikely situation there is absolutely no way to get cellular OR WiFi data. Usually I'm just looking up MSRP or adding something to my owned or wanted lists, none of which really require seeing a picture.
Anyway, just my $0.02.
For me I'd still prefer an all encompassing app with complete data instead of a "pull data as and when needed" approach regardless of whether there's free wifi around me.
On the brickset website this is available under the link https://brickset.com/minifigs/mycollection-wanted
It seems most websites and apps only support views of "collectable" minifigures, I get the distinction, but all minifigures can be collected right :)
Hope this is as easy as an extra menu item with an underlying sql statement.
(sorry if this was asked before and for valid/obvious reasons turned down)
As for the image data: I don't think you should put effort in changing it, if no one "complained" about it. Nowadays both 250MB permanent storage or always downloading on demand shouldn't be an issue for the target audience. (people with enough money to buy lots of Lego)
i know of my fire table, that i have is almost out of space. and the fire table dont use the memory card right. i have over 27gb free on the card and yet the table tell me over and over again i am low on space.
Unfortunately I can't make the downloading of images an option without a lot of work and also hosting (and paying for the hosting of) images myself (if Google host the data they automatically send it as part of the app installation / update - I don't know a way to stop this from happening). Another option would be to make two apps - one with and one without images, but I don't want to go down that route. Shipping without images and then adding an option to download them all from Brickset would be a poor user experience (they have to do something and then wait for the downloads to finish) and may cause a lot of load and expense on Brickset's cloudflare account!
@Recce I'll have to check about the cache, but if I remove images then I could make a separate cache setting for thumbnails. And it'll still be possible to only download large images on wifi rather than data.
@Cyc I would like to include "regular" minifigs in the app but it's not possible due to licencing issues over legacy data and especially images (Brickset is allowed to use the data but is not allowed to share it). Everyone I have approached about using their data in the app either flat-out refuses or wants payment (which I cannot afford as myBrickset does not generate income).
It includes Import/Export functionality as requested by @sid3windr (he's already got a beta version) but not the support for additional currencies (as El Hefe needs to do non-trivial things with the api to make them work).
Other than that it's mostly a minor point release - improved translations (especially Italian), improved performance (UI should be more responsive whilst large tasks are running), all the latest images, and minor tweaks & bugfixes.
Please LMK if you experience any issues but I expect everyone should be able to upgrade smoothly.
Something that I've noticed that would be a useful shortcut is to have a link to Brickwatch.net on the sets view (where Brickset/Bricklink/Brickowl are). I switched between myBrickset and Chrome quite a bit earlier today in the store.
You can simply link http://brickwat.ch/<setnumber> and it should work.
That site isn't useful to the entire world though (seems it covers Belgium, The Netherlands, France, Germany and UK right now) so I'm not sure if it's an ideal addition...
After downloading the APK I now get "Download failed because you may not have purchased this app". Got this last time when I installed it from APK, but that was on a device where it wasn't installed before...
Trying to fix that meant I had to uninstall the app, which made me lose my "built" "gift" etc. Luckily I exported last week! ;)
Unfortunately, I'm still stuck there - can't start the new APK.
I opened the app, it went to the download screen, and was like it was "topping up" a download - started at maybe 85% , maybe 260MB / 290MB? (VERY rough numbers, from memory)
I didn't cancel it, it finished, but closed (DIDN'T crash).
Then reopening it goes do download 0MB, and is stuck.
Oh and there is a system notification saying "Download finished".
Sounds like it's downloading the latest update (there was a 25MB patch file, plus 5MB app = 30MB download). Hopefully it's just something daft like I've referenced the external data wrongly in the validation code (this is a PITA and very hard to test in advance of shipping to Play, as the app needs to be in the store before I can access the expansion files).
Still stuck at work unfortunately.. I'll try to take a look tonight.
Somehow (don't know how) Google was configured to use an expansion file I had no idea about - probably a late night error. The code was looking for version 88 whilst Google pushing down 90 - so the app would never start as it would never see the file it was looking for.
Should be fixed now (I hope..!)
Thanks again for the app, and the quick turnaround!
Thoughts/suggestions?
Also, due to phone issues I totally forgot to check the brickwatch addition version mentioned above... Still need to do that!
If you have the latest version but still having trouble syncing, please send me your log files (main screen | menu | send log files) - hopefully they'll show what's going wrong.
It makes the screen flash a bit until the last one is displayed, but it also means I have to press the back arrow 3 to 8 times before I get back to the search form.
And yes, I only tap once.... :-)
PS: that brickwatch link would be nice.. I assume I shouldn't use the apk you created long ago as this will downgrade the app..
Not sure why the brickwatch link isn't in the latest version of the app, I'll have a go at adding it again tonight (when I'm home from work) and send you a link.
@MattDawson - I couldn't find anything wrong with the Manual Sync functionality, but it doesn't always happen immediately - it asks Android to perform a sync ASAP but it's eventually up to the system to decide when to do so. I'll take another look at this over the w/e just in case there's something I've missed, and feel free to LMK (and maybe send log files) if you still think there's an issue.
First time I searched for a set (assembly square) the set image flickered for a good 10 seconds...
And I think my sync is broken, too. I have 30356 marked as owned 1 on brickset, but the app is saying 0, even after forced sync. Mailing you the logfile.
After talking with sid3winder the sync was happening but the change wasn't showing up, this could be related to recent changes I made trying to fix the set flickering issue (the data's there, it just hasn't been published to the internal "content" db that drives the display).
And I don't know what's going on with that flickering, my fix should have worked. Back to the drawing board!
Have had a few users saying they're unable to launch the app (which was a pain to diagnose as it works fine whenever and wherever I test it), but I've been able to develop a fix so will be pushing that out this w/e along with a few other minor changes (mostly fixes to accommodate my using newer versions of 3rd party libraries). Sorry for all the churn lately, I change one thing (updated my IDE from 2.x to 3.x) and there's a whole bunch of knock-on changes required which come with a whole set of issues!