I've been pleasantly surprised with the built in calculator that ships with OSX; it's got a decent RPN mode, good keyboard support, and a nice stack display. Not brilliant, but better than what I've found for Windows or Android. :-/
On my iPhone, I use HP-12C emulator from RLM Tools (I found most other emulators to be inferior). When I really need it, I use HP50G.
On the iPad, I use either m48+ or HP50G (it seems to be another fork of the emu48 code). Both work really well given the size of the iPad — very comfortable to use.
I went thru the same annoyance on my phone/tablet and although I have droid48, free42, and hc-16C on my android devices I mostly just ssh into a real machine.
I have toyed with the idea of graphical environments like mathematica/maple on a real machine via rdesktop/vnc on my tablet, but I don't do CAS so much as stats where I stick with R anyway. And those apps cost lots of money for something I don't do much of anyway.
Eventually with any problem, either you solve it or reach an event horizon where the UI is too horrific to use anymore. So when I can no longer handle the touch screen keyboard I just disconnect from the screen session (yeah, yeah, I know kids these days use tmux) and reconnect on a real computer complete with keyboard and big display.
For medium sized arithmetic problems (as opposed to math problems), just use google drive's spreadsheet and then I can access it anywhere in the world on any kind of machine I have access to. So that's where "total of this column vs total of that column" level of problems live.
An add on android keyboard built specifically for math, or more specifically for R or octave, would be interesting.
It's surprising: when smartphones came out I said calculators would be first against the wall.
Ie: https://sensortower.com/ios/us/incpt-dot-mobis/app/calculato... https://sensortower.com/ios/us/vicinno-soft-llc/app/12e-fina... https://sensortower.com/ios/us/tla-systems-ltd/app/pcalc-the...
I am glad to see this effort because we really need some innovation in the world of calculators. The science of making them has stagnated in the late 1990s. HP50G isn't really different from HP48, first introduced in 1990.
I think there is a widespread perception that calculators are no longer needed, because we have all those computers around us. But that simply isn't true. Many people still need to calculate things quickly, and that requires a good tool: a calculator with a well designed user interface. This is where most devices and programs fail. HP worked on this for more than 20 years and got really good at it, until the unfortunate reorganizations that got rid of the calculator division.
I can't think of any other tool that will let me equally easily multiply numbers, convert hex to decimal, work with complex numbers, and compute a Laplace transform.
And even if you are in front of a computer and have a powerful mathematical package available, there remains the problem of the user interface. For example: I use Mathematica for lots of things. But just try entering numbers using engineering/scientific notation: 4.7*^-6 and you'll see this isn't good at all for rapid calculations.
I hope that someone will start where HP left off and design a better calculator using the huge computational power that we now have at our disposal. Without throwing away all the experience we already have.
http://www8.hp.com/us/en/products/calculators/product-detail...
I've used the emulator, but it's less productive than the 50g. Also TI's nSpire offering is just horrid.
I don't use my calculator in education which means I'm completely forgotten.
TI calcs
https://play.google.com/store/apps/details?id=net.supware.ti...
https://play.google.com/store/apps/details?id=com.Bisha.TI89...
https://play.google.com/store/apps/details?id=org.natygames....
HP calcs
https://play.google.com/store/apps/details?id=org.ab.x48
Casio
https://play.google.com/store/apps/details?id=com.developstu...
https://play.google.com/store/apps/details?id=o2s.emul.hp49g
HP RPN can't be beaten for serious number crunching. It's not pretty, but by god, it is EFFECTIVE!
It does return the correct value for sin(π) though (you gotta call __sinpi(x / M_PI) if you don't want to return -8.74e-8 or some ridiculous value).
This is ridiculous. Your calculator (most calculators) cannot apply sin to π, because π is not representable is their system (typically base-2 or base-10 floating-point).
What you have done here is make sine worse for all values, including the representable value closest to π, in order to obtain what you think is a cosmetically satisfying result for the latter. Note that seeing the closest representable value to π does not mean that the user intended π. Perhaps the user obtained this value as the result of a computation and it's a coincidence. Or perhaps the user really wants to know what the sine of 0x1.921fb54442d18p+1 (the double closest to π) is. Hint: it is not zero.
Casio scientific calculators do have an internal representation of π (it's treated differently from the closest possible typed value) and very nuanced representations of numbers in general.
As you say, this is where calculator apps almost inevitably fail - representing numbers properly is really crucial to the UX, and floating point numbers are not sufficient.
Casios are a mess. They are actually made my Kinpo which do a shitty job of pretty much everything. The notable exceptions being the FX991MS and Fx5800P which are very very close to my 50g (which was laboriously tested on paper before I trusted it)
50g is basically a 48GX emulator with 400MHz ARM core that emulates Saturn, MetaKernel and a CAS. Goes like lightning. Oh and a bigger screen so you get 7-9 stack lines. Also you can use SD cards as ports. Mine has 256Mb of Flash. Eats a set of batteries once a month but it's worth it for the power.
I can create a symbolic list with 50,000 entries in quite happily on the device then do all standard two-variable stats on it in 1-2 seconds.
I should clarify for other readers: __sinpi() is an Apple-created addition to Math.h, what it does is multiply the argument by M_PI before calculating. When you consider that my calculator has a key which inputs the constant pi (which is, of course, not actually pi, but M_PI), it all comes out in the wash (cosmetically speaking).
However, what would you do instead? Test before each trig function whether the argument is a multiple of M_PI and then choose which function to use? I would imagine this would fall apart at higher values...
Also consider that 'cosmetically satisfying' is not an unreasonable goal (in my mind) when the calculator really only has horizontal space for 12 digits in 36-point Helvetica, but you're right, as the user could arrive at arbitrary values by other means.
http://futureboy.us/frinkdocs/
(but not RPN and trig functions are floating point)
Calculators are still an unsolved problem for me on glass devices to the point I still religiously carry around an HP50G even though its 6x the size of my phone. Also from some bad experiences, it appears that some "app" calculators are also seriously badly implemented. Even basic trig ops can return stupid values at extremes which makes them untrustworthy. Plus none are reasonably programmable.
My use cases are base conversions, simple CAS stuff, basic engineering calculations, unit conversions, financial (TVM etc) and generic math. I also canned a lot of knowledge in RPL programs over the years from fuel calculations to diagnostic tools and dice rollers etc.
Please can someone solve all these problems (without doing half arsed HP calc emulation).