I am looking for advice on the best way to design a solution that will work on both an [url removed, login to view] webpage and in a client side executable (.NET App).
Let me give a simple example and you can help me figure out the best way to do this.
Lets pretend i have a simple webpage that has a logo at the top and 2 fields. One is called Name, the second is called Phone Number.
I can put data in either field and i can hit a save button to save the data to a SQL database.
Now I have users that go to a web url and enter in names and save data, but I also have some users who do not have web access 50% of the time and they need to store the data on their local machine.
The data entry screens look identical in both apps.
Now the problem i have is that in real life I have many pages, and they are constantly being updated and added onto.
I need a solution that will allow me to develop an interface one time and easily use it in both the [url removed, login to view] page as well as the .NET App.
The only thing I could think of was to store the field data in a database that would store information about the components like:
then the [url removed, login to view] page and the .NET App would build the user interfaces using that meta data but I wasn't sure how to make sure it would look right in both APPs.
What do you think is the best way to do this?
By the way this is the beginning of a very large project, and I will need the project winners help to make these updates.