App Update

[nebulis]

When are you going up update this app? The current version almost two years old and crashes frequently.

You've said its in the works before but two years is a long time and I've gotten to the point where I rarely use this because it rarely works correctly.

Updating the offline cache crashes the app. Editing a deck crashes the app.
Prices updated by looking at a card don't hold upon relaunch.
Can't link devices for life tracking.

Other users complain of the same things but because your version doesn't do that you do nothing. I understand that if you can't reproduce the issue its hard to troubleshoot but you can't just brush of your users. The issues exist and need to be dealt with.

[Piotr]

I beg your pardon? I owe you nothing, as far as I know. You had perfectly good app sold to you and destroyed by Apple [updates], so take your needs elsewhere.

To everyone else: good things come to those who wait

[nebulis]

I never said you owed me anything. What I said was the app has bugs and that's because it hasn't been updated in a year and a half.
That's all on you. You can't blame Apple for updating the host operating system. They have a well established upgrade cycle that predates this app. Blaming Apple like that is a cop out.

You use to update the app when a new major iOS version was released and then you stopped. You can't say it's your users fault for upgrading an older device with a newer iOS version or buying the latest device.

My intention was not to offend you but to express my frustration that the app is broken and you've been saying for a while that a big update is coming but as of yet there is no update and no news about it other than its coming.

[Piotr]

My intention was not to offend you but

you did.

You can't say it's your users fault for upgrading an older device with a newer iOS version or buying the latest device.

I never said this. Don't put words in my mouth, this is something I do not want to be done to me. I'm going to ignore your Boss status* from now on.

You can't blame Apple for updating the host operating system.

Of course I can blame Apple for screwing it up


* this means you can't boss me around like other Bosses can.

[nebulis]

It was your choice to not update for, at the very least compatibility, the last 18 months. If you don't change with the times you will be left behind and alienate users that have been there since your first release.

User reassurance like
I'm aware that there are some bugs. They will be addressed in the next release that I'd like to have out ...
Is all that would have been needed. Not these defensive responses that don't really help your paying users by alienating them instead.

[Kaylesh]

Let me start with this: I do not agree with the tone of voice used by Nebuliss, I don't mind waiting, and try to find fixes or workarounds whenever something doesn't work as expected, or crashes. (Example: deck builder crashed, I add cards through the database instead.) I found out, through trial and error, that some things can influence an apps behavior negatively. Older hardware, multiple apps in the background, storage room. Unfortunately Apple doesn't bother giving any error messages or logs as to why an app crashes, which would benefit efforts to prevent such behavior from either user or developer.

However: I too would appreciate an insight in the steps needed to be taken for an update to become available, and if remotely possible a timeframe in which this could be expected.
I realize the nature of programming prohibits an exact timeframe to be established, as one semi-colon in a string of text that could be printed inside the covers of the Encyclopedia Brittanica could cause undesired function, however, I do think that knowing the amount of work required would ease the effort of waiting, and reduce feelings as expressed by OP.
So, Piotr, long story short:
Is it possible to give an estimate as to the amount of work needed for a functioning update to be released, or even alpha-tested?

[Piotr]

Let me start with this: I do not agree with the tone of voice used

Personally I don't mind the tone at all, I'm used to drama queens What I find offensive here is the suggestion that somehow by releasing the product I owe this person lifetime support and updates to it, regardless of changes in environment and 3rd party action. Well, no, this is not the case. I find it offensive because I don't like stupidity: http://imtgapp.com/forum/index.php?topic=20308.0

If they want my continuous support and Database Updates, as well as hosting of this forum, they should make sure they support the project by subscribing to $0.99 Patron monthly PayPal plan. PayPal is a bank based in Europe, which we have tested over many years and consider as safe as HSBC.

Is it possible to give an estimate as to the amount of work needed for a functioning update to be released, or even alpha-tested?

2 months of programming.

Unfortunately Apple doesn't bother giving any error messages or logs as to why an app crashes, which would benefit efforts to prevent such behavior from either user or developer.

So the idea is, add System Log to Shake Menu in Main Menu -> Settings?

[Kaylesh]

That last one is a great idea, if possible it could help determine if the crash is caused by an error in the apps coding or an outside influence.

Also, thank you for giving a broad timeframe on the pending update.

And, last but not least, thank you again for devoting time and server space to keep this community and the app alive.

[Piotr]

That last one is a great idea, if possible it could help determine if the crash is caused by an error in the apps coding or an outside influence.

Thank you for it.

Also, thank you for giving a broad timeframe on the pending update.

The problem is, 2 months of programming could be delivered over 2 years, so my timescale is not very helpful from your point of view. Sorry about that.

And, last but not least, thank you again for devoting time and server space to keep this community and the app alive.

Glad to be of service

[Piotr]

try to find fixes or workarounds whenever something doesn't work as expected, or crashes. (Example: deck builder crashed, I add cards through the database instead.)

You would be a good SAP consultant

[Kaylesh]

try to find fixes or workarounds whenever something doesn't work as expected, or crashes. (Example: deck builder crashed, I add cards through the database instead.)

You would be a good SAP consultant

Tx. I never considered it, but your post made me read into it. It seems like I could well have the mindset needed for such a job.

[Piotr]

I could well have the mindset needed for such a job.

I think it is all you really need, the attitude. When there is a will, there is a way
SAP consultants are required to make things happen with the limited resources they have, the limits of software itself included. Ability to think out of the box and to provide workarounds when forced to work with obsolete tools helps a lot in this trade...