all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-It won’t be long and we will be able to say – “Adilas is an eCommerce ready point of sale system.” It does a lot more than that but those might be good words to use together. I liked the eCommerce ready part of that saying. -I’m seeing more and more need to build out the eCommerce pieces. That is what people want and think that they need. -Steve and I used to joke… “You can do that???” Or, “You can do that!!!” -We are good at creating and using dynamic templates or dynamic engines. We build once (the engine or template) and then use it over and over again with different or dynamic content. Build once, use many! We used these same concepts on a number of fun projects like the BATC Interactive app., Learn to Freeride (LTF) app., and adilas. It is a great model and very flexible. Build the engine and then allow it to play on multi levels. -What if the actual API calls could have custom stuff added to them? This could be on both passing data in and getting data out. Our current thinking is to expose the API “as is now.” But I can see in the future where some custom options could be beneficial. -This is a side note… but often we have to dream things up in a static mindset. Once we make sure that works; we tend to want more dynamic and custom options. It is a built-in progression of sorts. If you jump straight to dynamic, you tend to get lost sometimes…. Too many options and you no longer can tell what is the most important. I’ve see this many times. -My brother had the idea about creating custom adilas interface options. He would then sell them for $10 a piece over eCommerce. This would be like clothes or different skins. I’m not sure where this would go but I wanted to record the idea. I can see him doing this and then contacting us and having us put the custom interface in place. It would be cool if it was already wired up, had its own help file, documentation, and then it could be added either manually or automatically to the users options under their chooser. Maybe this would require the artist to submit the interfaces for review and wiring. Then we could hold them and let people purchase the interfaces as needed. Anyway, just some options. -Another idea is to have the artist create the custom interface, pay for it to be wired up, and then be able to sell it. Basically, the artist pays for the storage and wire job and is then able to sell it as an add-on to the basic adilas package. We, adilas, would then have to track that and give a kickback to the artist. -Another idea from my brother, we could play a small intro video for a subject during a training to get the ideas flowing. Then we could talk about it and see where the questions are after watching the intro video. Great idea! My brother, said that he loves to see what is possible and then he is more willing to learn it if he wants that as an outcome. I thought that is was a great comment. |