Feature Requests
Welcome! Use this forum to make feature requests for Mobile Services. Please try to be as detailed as possible in your description so we, and others, can fully understand your request.
-
Add support for F#
Let me author my scripts in F#
295 votes -
Support C# for Server Side "Scripts".
Add support for Server Side "scripts" to be coded in C#.
29 votes -
Add an independant authentication system
Right now, we can only use Microsoft Account/Twitter/Google/Facebook with Windows Azure Mobile Services.
However, if we use the Microsoft Account, it will ask to the user for the following rights: name, gender, display picture, contacts and friends.
I don't need any of those information and asking for this don't not add confidence to the user especially if the app is not related with those information.
The Buddy platform implemented their custom authentication system.
Thank you
ArchieCoder75 votes -
More comprehensive documentation
More real world code examples, better documentation on server side scripting as it pertains to Mobile Services specific classes and methods, lol the elusive "Better" across the board.
13 votes -
16 votes
-
Push Notifications support for multiple App Ids
Actually each mobile services can only serve one application, but in real escenarios a mobile services should serve more than one application.
9 votes -
Support GUID Primary Keys
This would make porting existing databases easier and give us more freedom with design.
41 votes -
The full "Azure" Development Experience
Code and Test Locally in Visual Studio, Deploy Package to Test Instance, Promote/Swap Tested Instance to Production Instance, etc.
9 votes -
Abstracted Notification Services
A complete abstraction for both client and server side scripts making the sending of push notifications with having to special case by device type. This is particularly important if you will be sharing the same mobile services across multiple device types.
9 votes -
push
Remove the need to use the Data Service to send Push Messages.
1 vote -
Use Azure Table Storage Option instead of Azure SQL Database
Let's face it, compared to the Table Storage service, the SQL Database service is EXPENSIVE! Mobile app developers need the low cost option as well. This will surely impact query performance for complex queries but we're big boys and girls, we can weigh the pros and cons.
6 votes -
Bulk Insert
Allow me to send in arrays of objects to insert, without further scripting on the back end.
10 votes -
Automatic generation of api documentation
This would ideally only generate documentation on the publicly accessible endpoints. Maybe even allow some sort of commenting standard on methods to extend the default auto generated documentation.
3 votes -
Add mulitple app support for mobile services
Add mulitple app support for a mobile service. Ex. 2 Windows 8 apps connectng to the same mobile service
8 votes -
Give me more control over the HTTP interactions, including visibility of the request and control of the response
It would be great if I could have more control over the HTTP API in scripts. For example, I would like the ability to read all incoming headers and set outgoing headers.
27 votes -
Add Blob Storage APIs for iOS Devices
APIs/SDKs exist for working with blob storage (for images, raw binary data, etc.), but only for Windows devices. Add a similar API/SDK for use on iOS.
3 votes -
Passing Parameters IOS aplication to Windows Azure
Hello, Can you halp me in this situation ? I search for two days, but I cant't find a way to do this ...
How can I pass parameters to read function in Windows Azure mobile service ?
In code bellow I call the read function , but I want pass Parm1 to manipulate in Windos Azure.
[itemTable readWhere:predicate completion:^(NSArray *items, NSInteger totalCount, NSError *error) {
I want in Windows Azure make something like this...function read(query, user, request) {
var parm1 = query.parameters.Parm1;request.execute();
}
Tks for help me.Paulo
4 votes -
Add an out-of-the-box Logging Service
As mobile app developers, we need an efficient way of capturing critical errors that our end users face. This should just be a standard feature offered by Mobile Services. Something we don't have to write ourselves.
The client API needs to batch offline log events and be smart enough to post them when connectivity is back.
The dashboard should allow us to sort by platform (W8, WP7, WP8, iOS, Android, etc.) and even identify specific users log activity (if security is enabled).
3 votes -
Mobile Services + Just Released LightSwitch HTML Mobile = A Perfect Match!
So, HTML5 based Lightswitch came out on April 6. It allows one to throw up a sleek looking app on top of RESTful service with very little effort, and have it look awesome on a mobile phone. I would love to take advantage of that! Since Mobile Services are already RESTful, I think it should be possible. The snags that I see: Mobile Services need to expose their $metadata in OData compliant way, so that LightSwitch can generate its proxy classes, and authentication mechanisms need to get worked out.
6 votes -
winjs
Native support for html5 apps
5 votes
- Don't see your idea?