Jokes aside, if you wanted to develop native applications within that framework (BASIC as implemented by Frederic Laboureur) you would use PureBasic (for Window

Jokes aside, if you wanted to develop native applications within that framework (BASIC as implemented by Frederic Laboureur) you would use PureBasic (for Windows, Linux, Mac, Raspberry PI and, in a discontinued version I believe, Amiga). PureBasic compiled to FASM (then standard executable) up to recently - after Apple switched to ARM, a decision was made to compile to C. (It goes without saying that coding in PureBasic can be much faster than coding in C - that is the purpose.) Use of native libraries is direct. SpiderBasic was born, I guess, to use that framework on mobile devices - which can use Web based applications, if one does not want to invest the time to go native and can bear with the limitations web security imposes. I.e., rephrasing: Fred and his team had this product which worked on all main desktop platform, and at some point mobile environment became prominent: they must have thought, either we invent a way to compile to native Android and iOS, main application code and libraries, or we exploit the consolidated way of compiling into web apps. So PureBasic got flanked by SpiderBasic.