0

Users of my app have a wristband which has an NFC tag. NFC tags can be encoded with a URL, but then I have to use the same URL for all aspects of the app.

The user presents the wristband at various devices, each of which has a different functionality.

I have to combine all of those functionalities into a single app. Much as I would like to have one app per functionality, I am forbidden to.

So, normally, I would have URLs along the lines of http://<app URL>/functionality_X, where the user visits http://<app URL>/ and the logic would $state.go("functionality_X").

Now, the wristbands need to be uniquely identified, so the each have a URL encoded along the lines of http://<app URL>?tag_id=1234.

Which results, after state change, in the browser displaying http://<app URL>?tag_id=1234#/<functionality_X>.

Is there some way that I can make the displayed URL less ugly?

Improve this question
2
  • 1
    could use a resove to capture the url values and store in a service then redirect to a more generic looking url that only resolves if the prior data exists. Not really clear how they arrive at this url in the first place Commented Nov 20, 2016 at 21:24
  • Well, I already get the tag_id from the URL before changing state. I also don't understand how that parameter remains part of the new URL after stae change :-( Commented Nov 21, 2016 at 9:22
Related questions
30
Query string parameter in ui-router urls?
0
AngularJS ui-router with different URL parameters
1
simple url with ui-router in angular.js
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.