Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

javascript native feature parity #58

Open
konsumer opened this issue Dec 31, 2013 · 2 comments
Open

javascript native feature parity #58

konsumer opened this issue Dec 31, 2013 · 2 comments

Comments

@konsumer
Copy link

There are a few core features that would really make the javascript shine, and make it so I don't have to maintain separate native apps, which would be awesome.

Here are the big ones, as I see it:

  • Data-logging (javascript datalogging #57) - this is better than appmessages, right? I like the idea of disconnection-tolerance. If so, I would love to have it available in javascript
  • start/closeAppOnPebble to trigger other apps
  • Sports APIS - it would be neat to be able to trigger these from non-apps
  • misc utilities from pebblekit

Otherwise, appmessage seems to handle just about everything else I would need for everything.

If these things are not in the works, I should probably get started on a Phonegap wrapper for future watchface projects.

@konsumer
Copy link
Author

To help with stubbing out a possible Phonegap plugin, I made a little example wrapper, thought it might be helpful:

https://gist.github.com/konsumer/8197037

@konsumer
Copy link
Author

konsumer commented Jan 3, 2014

I started working on this it doesn't really do anything yet, but I am stubbing the basics, and it might be helpful to integrate into this project, at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant