r.tenorio671 wrote:exx1976 wrote:r.tenorio671 wrote:... A useful feature in your app would be the ability to export it to your laptop/desktop with the formulae intact so that you can use it in MS Excel
I can do that. What do you mean when you say formulae, and what would the spreadsheet look like?
...for what little I know, it sounds like your app uses multiple linked tables that have embedded calculations that will update the appropriate fields as a data element changes. The few phone apps I've used are limited in that they can accept imported files in one of the delimited, txt or csv formats or export in the same flat file format. Unfortunately, a flat file doesn't always include the calculations. Your app sounds on the surface to be more of a database that uses a form (or forms) for the user interface, but most SS applications have some sort of "form" capability as well, but not always easy for the majority of users to create on their own. FWIW, if your app could be interchangable between the desktop and the mobile device where export/import of the data could be done for synching you would probably reach a larger target audience. Data file interchange can be via USB, NFC, BT, e-mail attachment, basically any media format that doesn't rely on the cloud. If the cloud is compromised, unreachable or gone.... Just my depreciated $0.02....
You're correct, it's a multi-table SQLiteDatabase. All calculation and data manipulation is done on the front-end and then posted to the database.
I originally wrote this Android app for personal use, and one of my previous "solutions" (among many) actually was a desktop-based application. But what I found during my initial research (prior to deciding to make the Android app available to the masses) was that a lot of guys don't have a computer near their bench, nor do they have room to put a laptop on their bench. The reason I switched from the desktop app to the mobile app for personal use was that without the mobile component, I still found myself in the situation of not having my inventory at my fingertips, and coming home having bought something that I already had, but had forgotten about.
It wouldn't be difficult to dump the tables to a CSV, as you mention, and I can code .NET, so that's not an issue either. Longer term, the issue that I see with that is that I cannot code for Mac, and the iPhone (when that version is released) guys will want feature parity with the Android version. Then there's the non-trivial matter of the distribution of the x86 code (and the Mac code if I go that route), and then multiple branches to support, and.. The list goes on. All for what I'm not entirely certain would be a feature that would be utilized by all but the outliers of the userbase. I'm not a software development house, not do I work for one. That is to say: this was all written in my spare time. I guess my biggest concern would be eventually ending up with 4 code branches to debug and support and add features to. Since there is a finite amount of spare time that I have between shooting competition and working my regular job, this would extend my release timetable significantly. Since I'm very committed to incorporating as many user-requested features as possible, in as timely a manner as possible, I don't know that would be in line with those goals.
Lastly, since this is the first publicly-released version, I've already received numerous feature requests. My next release will be out by the end of January, and the plan is to follow that up with a release by the end of February. That fast of a development cycle (again, taking the amount of available coding time into account) doesn't lend itself to supporting multiple codebases, for multiple platforms, simultaneously. Perhaps once I get most/all of the most commonly requested features added, and the codebase is more stable, I could look at adding something like that in. I'm just trying to be realistic about it. Underpromise & overdeliver is always better than the reverse.
HOWEVER - having said all that, I am keeping a file of all user-requested features, and marking how many requests I've had for said features. If enough requests come in that it would seem to be a popular feature, I will certainly do my best at adding it.
Hopefully you understand.