- Jul 25, 2006
- 1,202
- 2
- 81
SWIM may/may not be involved with a project in which a vehicular asset's location (either current, in-motion, or intended upcoming stop/location) is provided to a web resource.
Focusing on a user web app (to avoid costs of getting into platform app stores, while providing cross-platform availability)... How would one go about using that location info, grabbing the device/browser location info, and map the two along with possible directions on a map (google maps or similar); with the following requirements:
- The site providing the webapp will likely show it in a frame, and no redirects or link-outs can be used; the mapping/location information must be generated/displayed within the webapp and it's frame.
- Any APIs, design tools, etc. must be no-cost.
- Everything past being sent the vehicular location information should be done on the client device via the web app (no separate web-hosted storage or DBs).
- Focus is on design of the web app and not infrastructural setup, server/hosting resources, or hardware.
- Solution is attainable for a small group of folks; some app-dev bg (java, little bit of c++, tiny tiny bit of c# experience), others with mild web use-testing, and the remaining likely using prototyping/mockup/wireframe/design tools to rapidly generate the interface (non-technical project team members).
Focusing on a user web app (to avoid costs of getting into platform app stores, while providing cross-platform availability)... How would one go about using that location info, grabbing the device/browser location info, and map the two along with possible directions on a map (google maps or similar); with the following requirements:
- The site providing the webapp will likely show it in a frame, and no redirects or link-outs can be used; the mapping/location information must be generated/displayed within the webapp and it's frame.
- Any APIs, design tools, etc. must be no-cost.
- Everything past being sent the vehicular location information should be done on the client device via the web app (no separate web-hosted storage or DBs).
- Focus is on design of the web app and not infrastructural setup, server/hosting resources, or hardware.
- Solution is attainable for a small group of folks; some app-dev bg (java, little bit of c++, tiny tiny bit of c# experience), others with mild web use-testing, and the remaining likely using prototyping/mockup/wireframe/design tools to rapidly generate the interface (non-technical project team members).
A current proposal is the following:
Using wordpress (or maybe appery.io), the the web app interface will be made. A prototype is being sought, initially; so, the vehicular GPS info will be hard-coded in the web-app design as static, dummy data. Browser/device location info is requested, and (somehow) using google maps API (if free for this usage) will show the vehicle as a point or destination on a map... The user's location will indicate their position on this map, and options for routes (by car or by foot) to the vehicle are options below the map graphic.
Using wordpress (or maybe appery.io), the the web app interface will be made. A prototype is being sought, initially; so, the vehicular GPS info will be hard-coded in the web-app design as static, dummy data. Browser/device location info is requested, and (somehow) using google maps API (if free for this usage) will show the vehicle as a point or destination on a map... The user's location will indicate their position on this map, and options for routes (by car or by foot) to the vehicle are options below the map graphic.