In basic of course.
I don't know any other languages. I've always wanted to be able to make a small application for android, but unfortunately I only know basic. I found B4A. (basic for android).
https://www.b4x.com/
At first it was difficult, but later I realized that it's a very good editor, a well-transparent system, object-oriented, uses multiple 'timers', runs on multiple threads, is fast, and syntactically it's the same as QB64. When I got the hang of things, let's do something 3D! But unfortunately there's no such convenient, easy instruction as _maptriangle here. I was never interested in opengl, but I had to learn it. And then the ideas came:
2d opengl
https://www.youtube.com/watch?v=2PIgOF07BvE
3dopengl
https://www.youtube.com/watch?v=V81sO6SqKmw
3d opengl, also with VR glasses (two opengl windows with angle deviation)!
https://www.youtube.com/watch?v=xy3gdXoIOcs&t=22s
https://www.youtube.com/watch?v=9zD7TynEigc
raytracing
https://www.youtube.com/watch?v=qPOHzZcuBLA
After that I tried out what I learned about opengl on QB64.
https://qb64phoenix.com/forum/showthread.php?tid=3774
I wrote this so you can see that every program I showed you is BAD!
You showed me the revolutionary breakthrough, the professional approach with GLLIST. Because I didn't use vbo in openglSE. It doesn't know gllist either. I didn't know gllist either, because I didn't encounter it in opengl SE. In fact, all Android programs should be rewritten to use VBO. Because the performance is noticeably poor. They run at 60fps on a modern phone, but they are not well optimized and just eat up resources.
I don't know any other languages. I've always wanted to be able to make a small application for android, but unfortunately I only know basic. I found B4A. (basic for android).https://www.b4x.com/
At first it was difficult, but later I realized that it's a very good editor, a well-transparent system, object-oriented, uses multiple 'timers', runs on multiple threads, is fast, and syntactically it's the same as QB64. When I got the hang of things, let's do something 3D! But unfortunately there's no such convenient, easy instruction as _maptriangle here. I was never interested in opengl, but I had to learn it. And then the ideas came:
2d opengl
https://www.youtube.com/watch?v=2PIgOF07BvE
3dopengl
https://www.youtube.com/watch?v=V81sO6SqKmw
3d opengl, also with VR glasses (two opengl windows with angle deviation)!
https://www.youtube.com/watch?v=xy3gdXoIOcs&t=22s
https://www.youtube.com/watch?v=9zD7TynEigc
raytracing
https://www.youtube.com/watch?v=qPOHzZcuBLA
After that I tried out what I learned about opengl on QB64.
https://qb64phoenix.com/forum/showthread.php?tid=3774
I wrote this so you can see that every program I showed you is BAD!
You showed me the revolutionary breakthrough, the professional approach with GLLIST. Because I didn't use vbo in openglSE. It doesn't know gllist either. I didn't know gllist either, because I didn't encounter it in opengl SE. In fact, all Android programs should be rewritten to use VBO. Because the performance is noticeably poor. They run at 60fps on a modern phone, but they are not well optimized and just eat up resources.