JusSumguy
Chipmonger
Silver Level
I have Android and iPhone. Iphone is much more conductive to downloading. Android DL's are cumbersome to find, keep updated and manage. After a while you just stop.
Iphones have a much cleaner line between use and DL.
In my opinion you're wasting time AND MUCH MONEY developing an App for anything other than Apple.
Android should be the also ran.
Case in point. I have an android and I still haven't DL'd your app.
-
Iphones have a much cleaner line between use and DL.
In my opinion you're wasting time AND MUCH MONEY developing an App for anything other than Apple.
Android should be the also ran.
Case in point. I have an android and I still haven't DL'd your app.
-
Roller
Legend
Platinum Level
Time will tell if Apple has created their own App downfall since the implementation of the required "sanbox" for an app represented at the MAC App Store.
Overall Mac OS X development process has made SANDBOXING and acquiring
App Sandbox Entitlements from Apple, a Fantastic new and eye opening outlook on app design.
Apple: Developers now have until June to sandbox Apps for the privilege of being offered from Mac App Store.
to MAC or not to Mac ...
Downloaded the App on my Droid
Deco
Legend
Silver Level
When I started my project back in September I did not know objective C or have access to Xcode from home so I don't have any regrets even though I would rather have my app on the iPhone. I'll likely get this up and running for the iPhone in June.
My time isn't wasted as I find this fun, can apply my code and layouts to an iphone version and have this marked towards my degree (Best Final year project ever!).
I haven't spent any money other than a $25 registration fee for android marketplace and even that I didn't need to pay as I could have made a mailing list with apks attatched but thought it more convinient for my testers to download the app via the marketplace.
btw you haven't had any issues attempting to download have you? I had a weird thing happen on a friends phone were it wanted him to sign in to his non-existant gmail account.
Deco
Legend
Silver Level
No need, I didn't take it offensively. If I was developing this with the sole purpose to sell it, you wouldn't be far wrong.
As mentioned previously DonkeyTracker sold 1700 iPhone apps yet less than 1 % of that for android
Deco
Legend
Silver Level
V1.3 Released
We now have saving and loading. Save a player once and they should remain tracked for good until you choose to untrack them.
This has easily been the hardest thing to implement and I've had to debug it for weeks. There are still likely bugs. Please let me know off any bugs you come across.
In fact let me know of any small improvements to the interface you would like to see. My University demonstration is Wednesday next week so between writing my report and making a slideshow for the demonstration I can make a few minor tweeks if necessary and add them in with the new buttons along with the next update which will be the final one.
Thanks all. If I do ever make some money from this I will put it back into a CC freeroll.
We now have saving and loading. Save a player once and they should remain tracked for good until you choose to untrack them.
This has easily been the hardest thing to implement and I've had to debug it for weeks. There are still likely bugs. Please let me know off any bugs you come across.
In fact let me know of any small improvements to the interface you would like to see. My University demonstration is Wednesday next week so between writing my report and making a slideshow for the demonstration I can make a few minor tweeks if necessary and add them in with the new buttons along with the next update which will be the final one.
Thanks all. If I do ever make some money from this I will put it back into a CC freeroll.
Deco
Legend
Silver Level
Should have another update for this very soon. I discovered a bug with the steal stat when HU.
BB checks or calls are counting towards missed steal oppurtunites so the % HU is always much lower than it should be.
Also going to polish up my screenshots on the googleplay page and this OP, extend the beta end date and maybe release on that forum which equals 4 get myself a second cohort of testers and keep the app free until I have an IPhone version good to go.
Haven't paid this much attention lately as I've been busy writing my report. Speaking of which some feedback on what you like or dislike would be great so I can throw it in or even a comparison to another product. You may comment based on any version of the app (A little over half the downloader have not upgraded).
BB checks or calls are counting towards missed steal oppurtunites so the % HU is always much lower than it should be.
Also going to polish up my screenshots on the googleplay page and this OP, extend the beta end date and maybe release on that forum which equals 4 get myself a second cohort of testers and keep the app free until I have an IPhone version good to go.
Haven't paid this much attention lately as I've been busy writing my report. Speaking of which some feedback on what you like or dislike would be great so I can throw it in or even a comparison to another product. You may comment based on any version of the app (A little over half the downloader have not upgraded).
M
mineriva
Rising Star
Bronze Level
Hi,
I registered to cardschat because of this App.
I am the mineriva known on other forums (pokerstrategy, 2+2 ect). I am also the guy that emailed you as far as working with you.
Just a few pointers:
STATS:
I have played a lot live and dont waste time with stats that have no meaning on live tables. IMHO these are the most important stats:
vpip,
pfr,
limp_fold,
fold_to_3bet,
3bet,
fold_to__flop_c_bet_headsup_in_position,
fold_to_flop_c_bet_out_of_position,
fold_to_flop_c_bet_multi_way,
fold_to_turn_c_bet.,
flop_agression_in_unraised_pot.
Because there are so many multi way unraised flops IMHO we will need no other stats. Specifically stats relating to steal is useless. Playing live you will see AA more often then it being folded to CO or BTN. Also 4bets is only KK+ so no stats needed.
regards
I registered to cardschat because of this App.
I am the mineriva known on other forums (pokerstrategy, 2+2 ect). I am also the guy that emailed you as far as working with you.
Just a few pointers:
STATS:
I have played a lot live and dont waste time with stats that have no meaning on live tables. IMHO these are the most important stats:
vpip,
pfr,
limp_fold,
fold_to_3bet,
3bet,
fold_to__flop_c_bet_headsup_in_position,
fold_to_flop_c_bet_out_of_position,
fold_to_flop_c_bet_multi_way,
fold_to_turn_c_bet.,
flop_agression_in_unraised_pot.
Because there are so many multi way unraised flops IMHO we will need no other stats. Specifically stats relating to steal is useless. Playing live you will see AA more often then it being folded to CO or BTN. Also 4bets is only KK+ so no stats needed.
regards
M
mineriva
Rising Star
Bronze Level
Tried it live last night:
Problem 1:
The interface and layout is very nice but the seats on the table and on your table is not the same so I found myself constantly checking who was on what seat. I guess with practice it gets easy but we need to consentrate on the table not on our phone. This problem can be overcome by simply displaying the player names on our UI.
Problem 2:
The is no option to save the data. (Or did I miss this). It is of very little use only tracking one session.
Problem 3:
Live poker = Lose poker. Many hands there will be like 3 or more limpers then a raise and some callers. On your app there is no distiction between limp-call and limp-fold. In Live Poker this is an extremely important stat.
Problem 1:
The interface and layout is very nice but the seats on the table and on your table is not the same so I found myself constantly checking who was on what seat. I guess with practice it gets easy but we need to consentrate on the table not on our phone. This problem can be overcome by simply displaying the player names on our UI.
Problem 2:
The is no option to save the data. (Or did I miss this). It is of very little use only tracking one session.
Problem 3:
Live poker = Lose poker. Many hands there will be like 3 or more limpers then a raise and some callers. On your app there is no distiction between limp-call and limp-fold. In Live Poker this is an extremely important stat.
Suited Frenzy
CardsChat Elite
Silver Level
As some have said before, if it were legal to have your cell phone out while playing...this would be an awesome thing.
Every time my phone goes off while I'm sitting @ a table, they make me turn it off. And you can't even look @ it while you're @ the table.
It sucks but I understand why this is a rule.
GL w/ your endeavor :top:
Every time my phone goes off while I'm sitting @ a table, they make me turn it off. And you can't even look @ it while you're @ the table.
It sucks but I understand why this is a rule.
GL w/ your endeavor :top:
Suited Frenzy
CardsChat Elite
Silver Level
Whoop got given a grade of 90% for this and the subsequent dissertation on it
Congrats :top:
Deco
Legend
Silver Level
Thanks I'm flattered someone would sign up to try my app out.
I likely haven't read your email, the address on my android marketplace account isn't my regular email address, I made a seperate google account for betas so 1star reviews for my buggy beta wouldn't be linked with actual releases I make.
I'll be sure to check my email next chance I get.
Whilst I agree that within the little experience I have with live play it's rare we get the oppurtunity to steal at a FR table I am designing this for all levels of play and home games. There will be high staked games or home games with able friends we do get the oppurtunity to steal as often as we do online.
Limp/fold and Fold to 3bet are definitly stats I will consider implementing, however the demand for postflop stats and the opinions of all those I have asked have been against implementing them even though it would have been great to code some complicated stats and was previously very high on my agenda.
The input required of the user has been critisized as too much hassle by some even for the two or three clicks we usually need for preflop play. Adding four streets to the app would almost quadruple the input required of users and would make the app something that requires the users attention for the duration of the hand rather than a few seconds imbetween the preflop action closing and the flop being dealt. It's very convinient as it means it never interupts the users thought process and even if it did for users new to the app it would interupt preflop which is by far the easiest street requring the least thought. That said it may be something I design in the future as personally I would use it but the feedback I have been given has made this a low priority for me.
One other thing is it would require an upheaval of my interface I'll describe in more details for your last point.
The graphical table in itself is an attempt at remedying this problem. DonkeyTracker and Poker incomes list of numbers was impossible to keep track of whilst I tested their programs out.
Having said that I agree it takes getting used to even with the table positioned. Nor should I use deficiencies common to all live HUDs in general as an excuse for not making improvements to my own app.
Consider the underlined my next update (will take a while as I'm currently working on porting this to IPhone).
Hold down on a player then select Track/Untrack. Hold down on a non-empty seat, choose load then select your player. I fear many players may miss the features within the player menu (hold down on a player) or the table menu (press the menu button). Any ideas on how to remedy this will be much appreciated. I am under the constraint with androids that smaller screens must be accommadated for so an onscreen menu/action bar which is always visible is only a partial solution I can only apply to medium to large screens.
Again this is a univeral problem. I would like to update this but it will be a hardeous update which will likely recieve little appreciation. People do not seem to want any more input demands off them than the already is. F3B and limp/calling will require a new interface, more input from the user and more phone resources.
To do this I would need to allow users to take a second action within the same street and we must clearly display the difference between a call and a call/call. I'd need actions to be done in realtime were the second we start a hand and make the HJ open limps all players previous to him must be visibly folded, if the BB reraises we then must fold the BTN/SB/CO and change the HJs seat graphics to show that they previously called yet another action may now be input and the default is currently to fold (not call like their previous graphic would say).
It's something I personally would want and is a prerequisite to me doing anything postflop but I'd need greater demand for it considering it may well be detrimental to my app despite being a very taxing update. I've had more feedback complaining off too much input being required than people requesting postflop play or F3B stats. I'm not ruling it out as I would personally like both postflop and limp-call/F3B stats.
Thank you for your feedback, I wish you'd posted this sooner your post is both helpful and would have looked great in my dissertation.
Anyone reading this I would love more constructive critisim like this. As much as I appreciate people liking the app or disapprove of your local casino or even your entire state banning phones at the table it's not something I can change by coding so receiving posts like the above are the primary objective of this thread.
Deco
Legend
Silver Level
Sorry to hear this, unfortuntaly this seems common in a fair few American casinos. I hope it's still useful for your home games. I will research into whether it's specific states or a casinos preference to do this. I've yet to ever encounter a uk casino that didn't allow phones at the table. For the entire Newcastle UKIPT main event last year I made notes on my phone (not using my app) using draft messages for every player I encountered completly unhindered. The only time some of the players had a go at me was when I answered a call at the table (It was my first big live tournament
).
M
mineriva
Rising Star
Bronze Level
Hi there,
I have been thinking a bit about this. In fact I have started building my own android/java version.
I am happy to share my design ideas here as I have no interest in taking my app to the market.
LAYOUT:
1) In stead of having one button for each player which needs to be pressed x amount of times IMHO it is much better to have 6 smaller buttons. ie {limp_fold}{limp_call}{limp_raise} and below them {bet_fold}{bet_call}{bet_raise}. The user will therefore only need to imput each action once.
2) These buttons can also display the stats and therefore function as the HUD.
3) The playername can be displayed above the buttons and can also function as the "menu" ie {start_tracking}{stop_tracking} ect.
4) You can also put a new button, similar to the "new hand", to go to each street of betting. The info on the above buttons can then change to display the stats for each particular betting street.
FUNCTIONALITY:
With the layout above the user only needs to press once for each player per betting round. The user is also at liberty to use the post flop stats. On the other hand the user is not obliged to use the post flop stats. So no-one can complain that it takes to long because the user decides how much stats he wants.
I have been thinking a bit about this. In fact I have started building my own android/java version.
I am happy to share my design ideas here as I have no interest in taking my app to the market.
LAYOUT:
1) In stead of having one button for each player which needs to be pressed x amount of times IMHO it is much better to have 6 smaller buttons. ie {limp_fold}{limp_call}{limp_raise} and below them {bet_fold}{bet_call}{bet_raise}. The user will therefore only need to imput each action once.
2) These buttons can also display the stats and therefore function as the HUD.
3) The playername can be displayed above the buttons and can also function as the "menu" ie {start_tracking}{stop_tracking} ect.
4) You can also put a new button, similar to the "new hand", to go to each street of betting. The info on the above buttons can then change to display the stats for each particular betting street.
FUNCTIONALITY:
With the layout above the user only needs to press once for each player per betting round. The user is also at liberty to use the post flop stats. On the other hand the user is not obliged to use the post flop stats. So no-one can complain that it takes to long because the user decides how much stats he wants.
Deco
Legend
Silver Level
2) is something I was considering on doing myself to save screen space. I didn't end up doing it as I was considering the possibility of clicking a stat for positional stats (click Vpip get vpip from EP, MP, HJ, CO etc). Had far too small of a screen to implent the above though so was a tight decision, I decided against based on it not being aethsticly pleasing when applied to my layout.
1) Is an intresting idea that circumvates the problems I described. My only concern would be the screen space required for 60+ buttons. Androids such as my ~2inch T-Mobile mini wouldn't have a hope in hell whilst even bigger phones may suffer from a cluttered layout, user typos and will likely not have room for a graphical table.
Were always in a constant battle between screen space and minimizing user input. I'd advise sketching your layout in real size for small/medium and large phone screen sizes see how individually pressable your buttons are.
4) Is a good idea I think is essential for postflop play when were constrained for space.
3) is another great idea but again needs the space for the user to be able to press easily without also pressing the action buttons.
1) Is an intresting idea that circumvates the problems I described. My only concern would be the screen space required for 60+ buttons. Androids such as my ~2inch T-Mobile mini wouldn't have a hope in hell whilst even bigger phones may suffer from a cluttered layout, user typos and will likely not have room for a graphical table.
Were always in a constant battle between screen space and minimizing user input. I'd advise sketching your layout in real size for small/medium and large phone screen sizes see how individually pressable your buttons are.
4) Is a good idea I think is essential for postflop play when were constrained for space.
3) is another great idea but again needs the space for the user to be able to press easily without also pressing the action buttons.
