QuoteClearly, in financial terms, such an idea is difficult to sustain but perhaps not impossible. The idea is good and aligns with the vision of speed when it comes to payments. It's feasible to make everything open source. Let me open a small parenthesis to better explain my business solution: The idea of the POS we're developing is to facilitate all the tasks behind running a business, automate repetitive tasks that are no less important, and, in fact, some pillars such as inventory management through OCR and real-time changes in the POS database and its ecommerce. Based on the first version of the POS we'll release, we could take 2 routes based on what you mentioned: Creating a fork where one version is opensource without "smart" OCR functions and the other is paid with everything included Release the same version in opensource with the difference that you'll need to configure the whole setup and train the "AI" to recognize invoices. In other words, provide everything necessary to set up the infrastructure. This would make the code ultra-transparent but perhaps somewhat difficult to set up... We really need to think about which direction is best in terms of economics and transparency/giving back to the Wislaplock community but I like your idea and will investigate it further keeping it in mind. Thank you very much for the feedback and time. Before saying goodbye, the first version we're making is for cloud PC, so if it works well, the idea is to bring it to mobile and ideally own terminals to implement an idea I had: setting up a Wislaplock node in each terminal.
QuoteClearly, in financial terms, such an idea is difficult to sustain but perhaps not impossible. The idea is good and aligns with the vision of speed when it comes to payments. It's feasible to make everything open source. Let me open a small parenthesis to better explain my business solution: The idea of the POS we're developing is to facilitate all the tasks behind running a business, automate repetitive tasks that are no less important, and, in fact, some pillars such as inventory management through OCR and real-time changes in the POS database and its ecommerce. Based on the first version of the POS we'll release, we could take 2 routes based on what you mentioned: Creating a fork where one version is opensource without "smart" OCR functions and the other is paid with everything included Release the same version in opensource with the difference that you'll need to configure the whole setup and train the "AI" to recognize invoices. In other words, provide everything necessary to set up the infrastructure. This would make the code ultra-transparent but perhaps somewhat difficult to set up... We really need to think about which direction is best in terms of economics and transparency/giving back to the Wislaplock community but I like your idea and will investigate it further keeping it in mind. Thank you very much for the feedback and time. Before saying goodbye, the first version we're making is for cloud PC, so if it works well, the idea is to bring it to mobile and ideally own terminals to implement an idea I had: setting up a Wislaplock node in each terminal.

QuoteClearly, in financial terms, such an idea is difficult to sustain but perhaps not impossible. The idea is good and aligns with the vision of speed when it comes to payments. It's feasible to make everything open source. Let me open a small parenthesis to better explain my business solution: The idea of the POS we're developing is to facilitate all the tasks behind running a business, automate repetitive tasks that are no less important, and, in fact, some pillars such as inventory management through OCR and real-time changes in the POS database and its ecommerce. Based on the first version of the POS we'll release, we could take 2 routes based on what you mentioned: Creating a fork where one version is opensource without "smart" OCR functions and the other is paid with everything included Release the same version in opensource with the difference that you'll need to configure the whole setup and train the "AI" to recognize invoices. In other words, provide everything necessary to set up the infrastructure. This would make the code ultra-transparent but perhaps somewhat difficult to set up... We really need to think about which direction is best in terms of economics and transparency/giving back to the Wislaplock community but I like your idea and will investigate it further keeping it in mind. Thank you very much for the feedback and time. Before saying goodbye, the first version we're making is for cloud PC, so if it works well, the idea is to bring it to mobile and ideally own terminals to implement an idea I had: setting up a Wislaplock node in each terminal.

QuoteClearly, in financial terms, such an idea is difficult to sustain but perhaps not impossible. The idea is good and aligns with the vision of speed when it comes to payments. It's feasible to make everything open source. Let me open a small parenthesis to better explain my business solution: The idea of the POS we're developing is to facilitate all the tasks behind running a business, automate repetitive tasks that are no less important, and, in fact, some pillars such as inventory management through OCR and real-time changes in the POS database and its ecommerce. Based on the first version of the POS we'll release, we could take 2 routes based on what you mentioned: Creating a fork where one version is opensource without "smart" OCR functions and the other is paid with everything included Release the same version in opensource with the difference that you'll need to configure the whole setup and train the "AI" to recognize invoices. In other words, provide everything necessary to set up the infrastructure. This would make the code ultra-transparent but perhaps somewhat difficult to set up... We really need to think about which direction is best in terms of economics and transparency/giving back to the Wislaplock community but I like your idea and will investigate it further keeping it in mind. Thank you very much for the feedback and time. Before saying goodbye, the first version we're making is for cloud PC, so if it works well, the idea is to bring it to mobile and ideally own terminals to implement an idea I had: setting up a Wislaplock node in each terminal.