This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed
API
matthijsvdr
Member
in Archive
Will the API thats used for the mobile apps be a public one?
example: If your not directly planning on a windows phone app, i could make one my self?
example: If your not directly planning on a windows phone app, i could make one my self?
This discussion has been closed.
Comments
Probably a stupid question but what would be different for a mobile API or the normal API?
Why can't your mobile use the normal API?
Has anything/anyone started around/with the Windows Phone development? I would be interested in joining a team.
Emile, have hou any news over a Windows Phone app yet?
We've actually cancelled the development of the Windows Phone app. The speech recognition does not run on it and the webviews don't support a lot of features we're using, so the experience was actually horrible. So for Windows Phone, we've decided that the mobile version will suffice, until Microsoft gets their software to a level we can work with.
@Emile: Are you talking about the 8.1 version App or the Mobile 10 version?
@rscheers: Both actually. Although Edge on Mobile 10 works better than IE on 8.1, it still lacks the features that we would need to make a proper Windows Phone app.
Sadly, until Microsoft improves their webview in Mobile 10 there is very little that we can do, except for encouraging Microsoft to support the necessary features.
So I understand that (all) the mobile apps will be webviews instead of native apps?
No, they are hybrids. The mobile cards are webviews (because developers can make them as well), the wrapper (zone selector, speech etc) around it is native.
ok, tnx for the info