devdocs/todo.txt

@@ -5,17 +5,37 @@
 - Pricing and plans
 - website / purchase / shareit products
 
+todo: legal@ayanova.com is mentioned in license agreements but forwards to webmaster at ayanova.com where it could easily be missed, it should go to support instead so change that at the mail server
 
 
 
 todo: BIG PICTURE
 
+Overview:
+	Focus on migrating existing users first before anything else
+	Critical path items for onboarding existing v7 people:	
+		New pricing determined		
+		New purchase product codes in shareit
+		Rockfish is already ready for them
+		Live eval system, probably manual for now spin up server keep several in rotation.
+		Announcement and messaging
+			Message to users
+			"Released officially, over the coming weeks will transition website, forum etc but you can migrate now"
+			Need careful plan about supporting v7 but no guarantees message
+				We don't want them to bail out prematurely so assurance they can keep going but we aren't updating and may come a time when we can't make it work anymore
+					'we understand you may not be able to upgrade now, we will continue to support v7 for the time being as long as it's possible to do so but no new feature will be added to it and v8 is here for you when you're ready'
+	New website / rockfish (integrated together)
+	New forum pages	
+	Deprecate v7
+		OLD WEBSITE
+			Keep as is, only change the home page for v8 and put all v8 under a fresh path	
+			because there are so many old links in v7 and docs that would need to be changed which would be endless fuckery instead just guide new people to new location
+
+
+
+		
 	
 
-Outlook integration extension??
-	This can wait until after official release when / if people ask for it
-		wtf to do with that, are there any other extensions actively being sold that I need to worry about?
-		this should probably be more like office365 integration at this point, need stats on desktop outlook but it must be vanishingly small aty this point?
 
 
 YES SOONEST - Pricing policy and plan
@@ -39,7 +59,6 @@ todo: QBOI deprecation
 		Email him and say we will be discontinuing support for it on XX date and that we will be supporting desktop quickbooks only
 		If he wishes to switch we will give him a free desktop QBI initial subscription for one year and then regular renewal price afterwards
 
-todo: legal@ayanova.com is mentioned in license agreements but forwards to webmaster at ayanova.com where it could easily be missed, it should go to support instead so change that at the mail server
 
 
 todo: licensing and pricing
@@ -116,60 +135,20 @@ todo: LIVE EVAL NOTES
 
 
 
+Outlook integration extension
+	PLAN: This can wait until after official release when / if people ask for it
+		this should probably be more like office365 integration at this point, need stats on desktop outlook but it must be vanishingly small aty this point?
 
 
 ADD TO DOCS:
 
 
-
-TEST IMPORT FILE OPEN ON iPad device as the file input accept type may not work with apple
-
-
-
-
 Image all the prior docs: Docs could use images on every page of each item, people like images and they may read the docs rather than look at the app so it's nice to show them
 Add where items are selected to all prior docs just as it's been done at the top of the vendors doc which goes a long way to have users understand the purpose of each type of object and why they might want to use it
 	Use the "references avendor" search pattern substituting vendor for whatever to find all the links in the schema which is the most reliable way to find them
 	this process also finds missing things in the docs like the vendor for User subscontractor I found which was not documented as it only appears when you select subcontractor type
 
 
-start in on QBI
-	Fastest easiest thing is to make it on the v7 laptop as a regular .net app but try to compile on .net core on main dev laptop
-	qb developer network change names and phone number from Joyce to me, it has 2fa set to go to Joyce's phone
-	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?
-	
-
-QBOI?  Fuck QBOI, all my homies hate qboi
-	How many actual? one PITI
-	Put last?
-	Focus on qbi
-	that developer survey for qboi api users turned me right off of using it, if they are going to be dicks about it then I'm not sure what the point is if we don't have many users 
-	just dilutes my time unnecessarily.
-	Pivot to other accounting api's instead that are free like the one Joyce uses?
-
 
 
 rockfish front end improvements, revocation, license link that does nothing??
@@ -201,8 +180,6 @@ todo: test with licensed key to ensure evaluate is gone and everything works log
 todo: test key revocation
 
 critical path items:
-	- docs completed
-	- QBI
 	- QBOI FUCK THIS DROP IT>>?? (or server to login and path for them to do it on their server however that works so we can exit that biz)
 	- import inventory and parts for future new sales will be critical
 		ultimately being able to import directly from other apps export formats or online api keys would be ideal