diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index 3e725087..10748f35 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -1,13 +1,37 @@
 # now
 
-TEST FILE OPEN ON iPad device as the file input accept type may not work with apple
+TEST IMPORT FILE OPEN ON iPad device as the file input accept type may not work with apple
 
 get back to docs completion
 
-check this in chrome: https://search.google.com/search-console?resource_id=sc-domain%3Aayanova.com
-	looking for security issues
-
 start in on QBI
+	minimum viable product, just something that works
+	How to make it work in desktop / winlan / linuxlan / online all together??
+		desktop is still same server so really all boil down to accessing ay server on one side and local file system qb api on the other side
+		so decision is to make it a web app or not.  In the perfect world it would integrate right into ayanova web app but can't make qbi api calls unless there is a javascript interface now for qb api??
+
+	Need to know what platforms, i.e. windows and online?
+	can it work as a web app only etc
+	a standalone windows desktop app for qbi replacement
+	integrated into web app qboi replacement?
+		should have it's own router package code so it only loads that chunk if a user goes to it
+	general accounting integration plan
+		maybe look at a few things we might integrate with and come up with some ideas of the form of UI required
+	Issue: can't build winform app in vscode due to missing winform designer
+		I could build it on v7 dev laptop and see if it can compile in vscode	
+			or, make it entirely on v7 dev laptop
+			or download a trial version of full vstudio (ugg.will fuck up my dev computer)
+	qb is a windows desktop app so it makes perfect sense to have a windows desktop qbi app for this particular case
+	//-----------
+	todo: read the latest quickbooks windows api docs and gettnig started guides to see what is now possible / involved
+		This is important *first* step as it might point to current recommendations for windows app solutions like winform or wpf or whatever the fuck is current
+		also critical to know if .net core (now just .net apparently) can call into the qb api, that will force my hand completely on the approach taken
+	todo: will need qb for testing, maybe in a vm to be on the safe side?
+	todo: (only if winforms is the route to go and .net core supports qb api) figure out how can design forms in vscode for a winform interface, possible build them on v7 laptop, commit and open in vscode just the form design part
+		does .net core support winforms?  Has the form design code format changed from .net?
+
+
+
 rockfish front end improvements, revocation, license link that does nothing??
 	product codes or feature options to include??
 	what exactly is rental in the license doing?