Next update will have 3D Graphs !

Version 1.0 is released, but I plan to add some more features in the forthcoming weeks: 3D Graphs are currently developed , for functions with 2 parameters , and even 3: I will use something like raytracing to display f(x,y,z) functions with “implicit surfaces”.

Note the Math Engine already knew how to give the normal vectors at the surface, which is used for lighting:  it’s just the cross product of the derivatives.

This is rendered using Shaders and GPU, which means your device will be used smartly !

I also plan to add Function Compositions, that will allow to use a fonction as a parameter of another one. I have to manage a special keyboard mode for this. Both with 3D Graphs, it will open a lot more capabilities for the whole app !

Link For Android Smartphones and tablets !
Link For iPhone and iPad !


Math Touch Book officially released

The Application for Apple and Android Smartphones and tablets is here, after 14 months of development !

The main goal of this App is to practice Mathematics, using the screen like a living rough draft assisted by Artificial Intelligence, and automatic layout.

Math Touch Book allows to manipulate equations and functions in a vectorial space, which suits very fine to haptic screens. You can resolve equations and look their transformations in real time, find derivatives and integrals, organize a notebook with your work, experiment in many ways and share your work with social networks, amongst many other features.

Physicist and Nobel Prize Richard Feynman, considered one of the brightest mind in the world, once said:

When I see equations, I see the letters in colors – I don’t know why. [..] And I wonder what the hell it must look like to the students.

Making these kinds of visions available for anyone was a guiding line during the development: Maths should be something tangible and clear to work with, both for students and confirmed Mathematicians.This is why a lot of research about interfaces has been done for this project.

If you have Math brain friends, developers or handymen friends, bring the good news and share this We need  your help, because this original product was created independently with no advertisement budget !
Take One minute to download this app, that weight less than 3 mb, do a little share and tell what you think about it !
Link For Android Smartphones and tablets !
Link For iPhone and iPad !

Capture d’écran 2016-02-12 à 12.46.06

Available both on Apple Store and Google Play


Flyers for french Universities

It arrived today ! I developed the App, but I also do a bit of marketing about it, it’s part of the job when you are independent. I will give out these little papers at the Paul Sabatier Science University in Toulouse next week ! I will not translate or explain the jokes written on the flyer. nudge nudge. wink wink. My private secretary at the right is here to oversee the execution of the process. She indeed validated, but expressed doubts about the absence of kibbles.


1 049 352 …. Bytes !!!

1 049 352 bytes !!  Ironically just 776 bytes after 1 MegaByte !!

(which is 1024*1024= 1048576 bytes)

To my surprise, this will be more or less the final size of #MathTouchBook for Android, that is to be released within the coming week (for sure, I promise, btw it’s a scoop !).

Capture d’écran 2016-02-05 à 22.50.35

The Apple iPhone/iPad version is more likely to weight 3 or 4 Mb, due to some external program libraries that iOS needs.

I wasn’t expecting less than One Mega for this App, this is great news to discover that thin number ! As light as powerful !

What happened ? I planned to include the Facebook SDK at first (3Mb), but I realised the “Share with Intent” system from Android was better. So I cleaned all the useless stuffs and logs from the App…

The tool is primarily using only my own C++ libraries, but I was a bit afraid because of the use of templates at some points in the code: C++ templates can really be useful for coding Maths because they allow to “Overload” simple operators (Addition,Substraction,Multiplication, whatever else.) by making abstraction of the actual type of your data. (Well, more or less.)


But C++ is an old language and C++ templates have a big disadvantage: Every template’s functions operators and methods you use is recompiled each time you use it. I mean: when you read a data in a map (C++’s hash table) , the whole read code is compiled for each call. ( for the record, only allocators are external with templates, and C++ libs like boost stands in includes and not .cpp for these reasons.)

But even if it has a funky side, MathTouchBook is an App with 95% Code and 5% data, so it’s really a “Algorithms and nothing else” approach. Beside that, I only have some little mp3 and PNG out there ! – Just what you need ! Capture d’écran 2016-02-04 à 13.11.58


A Simple yet Powerful Artificial Intelligence Algorithm.

One of the Key Word about Interfaces today is Responsive Design: For a Mobile App, interfaces not only have to be the simplest possible, they have to be clear, and they have to propose only awaited functionalities that users will understand: they had to be adaptative.

So not surprisingly, Math Touch Book displays nothing else than what you wrote on the screen. Then touching a Math expression unfolds a Menu that proposes a short list of features according to that expression.

Capture d’écran 2016-02-02 à 11.35.32.png

Adaptative Menus are not new, but here, the program must “think” to guess the list of functionalities, operations, modifiers: Expressions can be developed or not, Simplified or not, resolved or not. And notice, some of those features can take multiple passes, like Equation resolutions.
It might surprise you, but a bit of Artificial Intelligence (AI) intervenes at this level: The same basic AI algorithm is used, both to select the menu entries and to resolve equations.

With the advent of multi-threaded mobile CPU and GPUs this last decade, Robotics and Artificial intelligence are subject to permanent breakthrough. On the software side the AI subject becomes bigger every day. But large industrial AI programs for robots, that have to compute an impressive sum of data, and more little algorithms managing equations (like  MathTouch Book does) have things in common: they both manage their objects using Graph Theory, and they both create and test algorithms before applying them for real.


Let’s have a look at what Math Touch Book does when it resolves an equation:
First, Equations are defined by Graph Trees, where the root element is an equal sign.
Elements in a tree are all attached to another. That’s what Graph Theory is about and we, computer scientists, usually think it’s a nice way to manage data.

A good Graph theory framework should also have methods for cloning graphs, detaching branches of the tree, re-attach them elsewhere, and the ability to use one or another element allocators, amongst other things.


Then we have some bricks here, that represents schematically classes available in the program, it’s a “Object Oriented” concept. This scheme tells us each of these classes are “GraphActions”, and each is able to modify a graph in their own way. They are available to be used by the Artificial Intelligence.

So now that we know the shape of the data, the tools to modify it, we want the program to find itself a way to resolve the equation. How ?

An equation resolution algorithm can be expressed as a list of “GraphActions”. But what GraphActions to use, in what order ?
And what happens if the program find a wrong algorithm ? the graph would be destroyed !
No, because we can clone the graph and test modifications on the clone.
we can also simply look at the shape of a graph, and decide to modify it in a way or another according to its shape. (You now understand the usefulness of having clone functions and special allocators in your graph framework.)
Written in pseudo-code, you can find a resolution algorithm like this:

Capture d’écran 2016-02-01 à 23.33.06

Acting innocently, with just one accumulator list, a loop and an object oriented set of classes, we have here an algorithm that … creates an algorithm. and it works !
The human brain actually does more or less this “imagine what is the most interesting thing to do, and then do it” game. The temporary allocated memory can be seen as a short-lived “imagination”.  Obviously the real code is a little bigger, but the main idea is here.


To me, the greatest of all things is that, at this level, the algorithm is found, it is available for use, but you can or cannot use it inside the application; it’s up to the user, he may use another modifier, and in some way this “search what to do” Artificial Intelligence algorithm can also be seen as a recursive extension of the Natural Intelligence of the user, that decides, the same way, to use or not a feature. So it may demonstrates that Artificial intelligence and Natural Intelligence can cooperate.
In this perspective, one already can speak of Human Enhacement.