Can not work in iOS 18.1
Response from developer
Fixed in 1.10.
Menus broken, needs an update
Response from developer
This should be corrected in 1.9.
Doesn't work on iOS 17
Response from developer
This should be corrected in 1.9.
1.10
November 17, 2024
Bug fixes.
1.9
June 22, 2024
Bug fixes
1.8
September 11, 2022
Added metal and plastic 3D materials. Bug fixes and performance improvements.
1.7
June 1, 2022
Support for Dark Mode. Bug fixes.
1.6
October 21, 2020
Symbolically evaluate indefinite and definite integrals, summations, products, and limits. Simplify and Expand trig identities. Solve equations, systems of equations, inequalities, and differential equations symbolically. Factor polynomials.
More1.5
January 29, 2020
Added animation, sliders, axes, coordinate box, and camera snapshots in augmented reality.
1.4
December 4, 2019
View 3D mathematical surfaces in augmented reality.
1.3
February 3, 2019
Bug fixes.
1.2
January 3, 2019
Improved zooming. Added controls for radius, line width, and graph resolution. Bug fixes.
1.1
April 9, 2018
Bug fixes.
Yes, Graphing Calculator AR can support iPad devices.
Ron Avitzur is the developer of the app.
Graphing Calculator AR minimum iOS requirement is iOS 17.6.
Users are raving about Graphing Calculator AR, which has an exceptional rating of 4.0 out of 5.
Graphing Calculator Ar Relates To The Education App Genre.
The current version of the Graphing Calculator AR app is 1.10.
Graphing Calculator AR updated its app on November 30, 2024.
The release date of the app was February 5, 2023.
This app is rated for ages 4 and up, and contains only family-friendly content.
The following list of languages is supported by the Graphing Calculator AR app: English.
No, Graphing Calculator AR is not featured on Apple Arcade.
Unfortunately, users cannot make in-app purchases within Graphing Calculator AR.
No, Graphing Calculator AR does not provide support for Apple Vision Pro.
No, users are not exposed to ads in Graphing Calculator AR.
Fixed in 1.10.
This should be corrected in 1.9.
This should be corrected in 1.9.