??? 04/13/11 07:56 Read: times |
#181837 - added cost of the connectivity Responding to: ???'s previous message |
Taking this as a bit of a side-track:
Andy Neil said:
this is probably not suitable to most 8051-level systems (due to the added cost of the connectivity) ie, the cost (hardware & software) of the "connectivity" could seriously exceed the cost (hardware & software) of the rest of the system. The attraction of the "smart phone" is that lots of people already have them, are used to using "apps" on them, and they provide a very "nice" user interface - colour graphics, touch screens, etc.. Providing all that in a custom unit can soon make it very expensive - especially as it's only likely to be in low volumes. An alternative might just be to provide a comms "dongle" which just does the comms - and leaves all the fancy (G)UI stuff to the phone. Then all that needs to be provided on the embedded unit is a connector for the dongle. Which brings us back to the question of doing the app for the phone... |
Topic | Author | Date |
Creating iPhone apps? | 01/01/70 00:00 | |
added cost of the connectivity | 01/01/70 00:00 | |
Web server dongle | 01/01/70 00:00 | |
Code space | 01/01/70 00:00 | |
HTML isn't big | 01/01/70 00:00 | |
"only" (sic) 8919 bytes | 01/01/70 00:00 | |
All depends on target etc | 01/01/70 00:00 | |
You could do a lot in 1kByte | 01/01/70 00:00 | |
It isn't the page itself that consumes code space | 01/01/70 00:00 | |
Apps | 01/01/70 00:00 | |
Evil incarnate | 01/01/70 00:00 | |
hurdles | 01/01/70 00:00 | |
Apple "openness" | 01/01/70 00:00 | |
Free | 01/01/70 00:00 | |
Agree to disagree | 01/01/70 00:00 | |
No, quite a lot is missing | 01/01/70 00:00 | |
But still sufficient to be useful | 01/01/70 00:00 | |
No, definitely usable even if crippled | 01/01/70 00:00 | |
you misunderstood me | 01/01/70 00:00 | |
One More thing | 01/01/70 00:00 |